Jump to content

Brin Brody

  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About Brin Brody

  • Birthday 05/28/2002

Recent Profile Visitors

367 profile views
  1. Opening disclaimer: This is written for FAA-land. You absolutely could do this if your company policies allow it, but that's not always the case. Some real world company OPSPECs prevent crews from cancelling in the air, so they'll take a visual approach (under IFR) to the ground. I'd guess that some of the more "realistic" virtual airlines might have something similar built into their policies. There are also plenty situations in which it makes very little sense to cancel. For example, if I'm arriving into a Class B primary field (not necessarily a satellite, though this could be a
  2. Ross: You are a lifesaver. Thank you for taking care of this so quickly.
  3. Hello, all: vZJX ARTCC (VATUSA) has had a consistent issue with FS2020 pilots using vPilot wherein they are unable to connect to the primary CTR frequency (135.925). vPilot seems to interpret 135.925 as 135.924, making it so that pilots are not reaching us when they need to. As far as we're aware, we're the only U.S. facility to report the problem. We've been made aware that it is due to a SimConnect issue, but are still hoping there is some kind of resolution on VATSIM's side. Short of updating our primary frequency - again (this change was made only about two or three weeks befor
  4. Hi @Adar Polachek! At the present time, vUSAF, much like vUSAA (see Sean's post above) does not actively make use of a CRAF. We do have policies in place for such activities, though, which have been activated in the past. If this is of interest to you, please send me an email ([email protected]) and I can connect you with the appropriate party on our end.
  5. I've used TWRTrainer and vSTARs to run a simulation with virtual tower view... So this is probably a EuroScope-isolated issue. That said, I have no experience with EuroScope, so I have no idea as to a fix, this should at least narrow it down to a client.
  6. Oh it's built for it alright. Looks like it! Appeared to be very TRACON based (as expected) after a first look. Didn’t expect nearly as much TWR support. Thanks.
  7. Hi there... Been using STARs to work a Tower position, and though it's not built for it, it works pretty well. The only issue I'm seeing is the flight strips. It might be an issue I've created on my own, due to lack of knowledge, but I've been unable to use strips that aren't pushed from another controller. When pushed from another controller, either below, or above, they put themselves nicely in the bay. However, when working top down, flight strips need to be automatically generated. This is supposedly possible using the separators, and defining parameters for each... I've config
  8. Personally it happened every time... I had people reporting that it was working for them every once in a while though. Hence "sporadic". They might've just been using the old sector file?
  9. That's my own stupidity. You'd think I would learn something from a few years of programming. Thanks for the help guys.
  10. That was my thought too. However, it happens ONLY with the new sector file, and not with any of the old ones. The rest of our staff couldn't find any good reason, as sector files don't influence connections. There's been no reliable way to reproduce the problem past trying to connect using that sector file. Did you see anything abnormal in the file itself?
  11. Hi, I recently put together and released a new sector file updated to AIRAC 1709 for the Anchorage ARTCC. The creation is fine, and it loads into VRC fine, with all diagrams showing up properly. However, when a user attempts to connect to the network with the new sector file loaded, it connects them, and then instantly disconnects them. If they revert to a previous version of the sector file, it works fine. This problem is sporadic, and VRC will sometimes connect to the network without any issue. Is there something wrong with the sector file that would be causing this problem? Dow
  12. Thank you, Messina! Was able to only copy mswinsck.ocx into syswow64, but register all three successfully. Much appreciated.
  13. Nicely done! That's exactly what I need. Thanks, Christoph.
  14. Thanks for the try... But no. I've come across this before, but the list is not full, in the slightest. Good try.
  • Create New...