Jump to content

Evan Reiter

Members
  • Content Count

    221
  • Joined

  • Last visited

  • Days Won

    2

Evan Reiter last won the day on September 2

Evan Reiter had the most liked content!

Community Reputation

37 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks for the response Matt. I will say that I did receive the draft policy back on October 15 and provided the same feedback as on this thread. I didn't hear whether it went anywhere, which is why I suggested it here again. Ultimately, it's great to see the network looking for more input. I guess my comment is that publishing the policy as you did, but just with an effective date about 2 weeks after it's published publicly, might have been helpful. Your points around top-down ATC are well taken too. I can see the logic in the way you've done it. There is definitely value in being i
  2. I too am happy we have a policy now. I also agree that a few days' notice for implementation would have been helpful. Like you, ZBW had several questions come up on a Sunday evening. Fortunately, it not being 1am for us, we were able to put out a statement quickly. However, all it says is that we haven't had the chance to review the policy yet and that no changes will happen until we have. Some of our pilot members were asking what this means and they got "I don't know, we got the same info you did, at the same time you did", which makes us look a little under-coordinated. That said, giv
  3. Hi Dustin - not sure (and can't speak to) what the future of AFV will allow, but I've worked around this by using a program called VoiceMeeter. You set the audio output from AFV to VoiceMeeter and then you can choose (in real time) which output device you want. I'm not sure if the same is possible with input devices. https://vb-audio.com/Voicemeeter/index.htm More detailed instructions in this document, starting on Page 6: https://atchub.bvartcc.com/atcfiles/BVA_AdditionalSoftwareGuide.pdf.
  4. From a domestic U.S. ATC perspective, this was the first CTP I can remember that we were not absolutely hammered. And when we're hammered, Moncton, Gander, and Oceanic have it way worse than the rest of us. Having spoken to several of our controllers from Boston Tower through to the enroute controllers, the feedback is that this year's event was so much more manageable in the past. Having fewer pilots on frequencies (the result of both adding more airports and reducing the number of non-event aircraft) really improved the system for everyone. It meant no delays for slot aircraft, reasona
  5. We've talked quite a bit in this thread about the availability of pilot slots and the vast interest in flying the event. It's nice to see there is so much excitement and for the 50% of people who weren't lucky enough to get a slot: sorry. Hope you can join in the fun next time. It's good to see the team acknowledging that and giving those who entered this year an improve chance of a slot next time. As Morten says, there is a significant capacity limitation on this event. It's not just on the number of controllers: it's also about the availability of runways and airspace. In real life, Bos
  6. We've seen this error reported 2-3 times on Facebook with no clear solution. We have never been able to duplicate. Some things that might help based on what people have told me: Do not install into your simulator's folder but instead into a directory in Documents or similar. "I think it's a matter of different security settings for .net in the first place (I think my version is "too new") and afterwards I followed the suggestion to install it to a separate folder which made it work. I googled for the error message and found out what to edit in the registry. It's about .net s
  7. I posted about this issue here: I have seen this happening very regularly of late. It's been several airports and so it isn't just affecting KSEA. I have been told from a non-BOG that it's a VATSIM-wide issue and have not heard anything further on a resolution.
  8. Thanks Justin! @Dhruv Kalra 1182570tells me "ATIS voice dropouts are a known issue with AFV servers - that issue isn’t isolated to vATIS. Euroscope has the same issue. That’s high up their fix list, but afaik the AFV dev team hasn’t been able to nail down the issue as yet." Perhaps you are already aware but I thought I'd pass on his note. I think that would help tremendously. For what it's worth, it isn't immediately obvious that the voice drops. You would have to be monitoring it and/or have a pilot report that the voice isn't working. In my case, when I'm on position for 2
  9. Hi everyone, just following up on this thread. Have other facilities experienced this issue or is it just us in ZBW? Is vATIS' developer aware of any of this? Is VATSIM aware of any of this?
  10. Over the past several months, we have seen several examples of inconsistent behavior from vATIS. This seems to affect controllers at all levels and at multiple facilities within ZBW. We routinely get reports from pilots and need to restart vATIS on a fairly regular basis over the course of a long session. The issues are as follows: After an hour or so, it seems vATIS will stop broadcasting the "voice" portion of a non-recorded ATIS. The "TX ATIS" button remains selected and the "TX" light is on, but nobody can hear the audio (myself included). A restart of vATIS is required to re-
  11. It's difficult to troubleshoot this stuff when it's not real-time. Guessing here, it's possible you might have been outside the visibility/audio range of the controller(s) when you were attempting to fly. But there could be several other possibilities. Firstly, I'd strongly recommend making your goal to have voice working; the experience is much more engaging when you're speaking on the radio. Perhaps once you receive the new mic, things will get easier. If you are switched to the radio of the controller and using text radio messages, there is no reason the controller shouldn't reply
  12. Since the VATSIM audio is now range-based, it's possible that you were too far from the controller for them to hear you. Have you tried moving to another location and/or to an airport serviced by Ground/Tower? Of course, if you were at the controller's airport, this wouldn't be the issue.
  13. I haven't looked into this in the FAA AIM but in my experience, the altimeter setting or wind is almost never read back in a landing/takeoff clearance. I have never heard a controller query a pilot and request a readback of an altimeter setting in Canada or the United States. Interesting to know that is a requirement in Europe. If anyone is worried about this, let me know and I'll have a look through the AIM.
  14. Hi Travis, welcome to VATSIM! One piece of advice I'd offer is that, although events do offer guaranteed ATC coverage, they usually attract a lot of traffic. It might not be best to plan your first flight into an airport that is hosting an event because the radio traffic and workload would be much higher than an average evening. Do you fly in the U.S. often? If so, I don't think many VATUSA facilities are using VATBOOK at this stage. However, you can sometimes find "expected" ATC coverage available on websites. For example, if you visit www.bvartcc.com, you'll see we have an idea o
×
×
  • Create New...