Jump to content

Nate Johns

  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral
  1. Implementing Continuous Range Readout (CRR) in vERAM would go a long ways in replacing the anchor function in VRC, which is a valuable tool for TMCs and controllers alike for spacing and sequencing purposes.
  2. The primary issue with this, combined with attempting to follow the NBACP (real or VATUSA), is the discontinuous code sets. While each ARTCC theoretically has many hundreds of codes available at any given time thanks to Prim/Second/Terti-ary blocks, not to mention differentiation between Internal and External assignments, it get too chopped up among the potentially dozens of child facilities if we're trying to eliminate potential for dupe codes. Point being, the current client structure (nor POF) simply does not allow for a reasonable number of codes for departure-heavy events without arti
  3. With ADS-B being nearly-ubiquitously in use throughout the USA, we've very nearly come full circle away from the idea of radar coverage swaths. For typical VATSIM traffic, I believe it would be more realistic to implement filters to not display aircraft on the surface of airports (in a manner similar to the current arrival filter volume) and show all other traffic, rather than have holes in radar coverage. I have can expand on the concept in a separate conversation if you'd like.
  4. Ross, One area of concern is beacon code allocation. In the past, I have designed POFs to allocate increased and differentiated beacon code sets for tower controllers signed on separately from TRACONs. However, with vSTARS only allowing a VFR and IFR code set on a per-facility basis (as far as I'm aware anyway), I don't necessarily want to have individual vSTARS files for every tower facility. I was just discussing with ZAU staff last week about philosophy of sector file use based on this, with consensus on our end being we only wanted to support separate vSTARS files for ORD/MDW
  5. A long, long time ago, in a galaxy far away, Naboo was under an attack. Also, I vaguely remember there was an ability to geo-reference a standard FAA airport diagram PDF (vector shapes as it is) and somehow export such in to lat/longs, then convertable to sector file format. What is the modern state of airport diagram creation/updating? Would appreciate process discussion and software needs. Mucho grazie.
  6. 22:00:59.144 Started 22:00:59.919 Client Started with 11 22:00:59.937 Loading airport database json 22:01:00.360 Airport database loaded 22:01:03.712 Client Started with 11 22:01:03.748 Attempting to find API Transceivers for ZAU_NT_OBS 22:01:03.878 No Transceivers from API Received 22:01:04.696 Updated Trans List 22:01:15.475 Updated Trans List 22:01:15.599 Client Started with 67 22:01:17.949 Client Started with 82 22:01:18.103 Updated Trans List 22:02:18.106 Updated Trans List 22:03:18.106 Updated Trans List 22:04:18.115 Updated Trans List 22:05:18.129 Updated T
  7. See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown. at NAudio.Utils.CircularBuffer..ctor(Int32 size) at NAudio.Wave.BufferedWaveProvider.AddSamples(Byte[] buffer, Int32 offset, Int32 count) at GeoVR.Client.CallsignSampleProvider.AddSilentSamples(IAudioDto audioDto) at GeoVR.Client.ReceiverSampleProvider.AddSilentSamples(IAudioDto audioDto, UInt32 frequency, Single distanceRati
  8. Hi there, Just starting out with the audio software. Encountered an OutOfMemoryException. The program crashed after hearing a constant static loop for a while. I saved the error output. Is it something I should post here? Thanks! Love how it sounds!
  9. Gotta state a SID before "then as filed" if that SID is to be flown, departure headings or not. .65 4-3-3.d
  10. First, I think you would benefit greatly from reading through this thread. It's been fairly civil compared to many in the past, as evidenced by it not being locked by this point. Personally, I think I see your point, but I think it's poorly made. The proposed VATUSA high altitude airspace construct is a fabrication with little to no basis in reality. TRACONs (and all airspace sectors) shutting down due to time constraints, however, are consequences of inherent volunteerism for the network at large. I would argue that part time TRACONs and towers are fundamentally more realistic and ben
  11. A founder wants this, so, yes, it is serious.
  12. High altitude controlling in VATUSA (and I am explicitly qualifying this for VATUSA) is fundamentally boring, except for high profile events where alleviating frequency congestion and providing solid in-trail spacing is paramount. Low altitude is where departure clearances, approach clearances, terrain, towers, runways are... all the "meaty" stuff. Where the work really happens. And as for center = enroute "nothing else," I guess the tens of thousands of airports to which ARTCCs alone provide approach control service don't count for anything. The people that have cooked up the me
  13. Just don't take any pictures... trust me.
  • Create New...