December 2, 20205 yr Hi all, When departing KPSP using VoxATC, both Palm Springs departure and SoCal center are using 126.70. It leads to some issues with crossed comms where it seems even AI gets confused. Is this a frequency resolution issue in P3d, a VoxATC issue, a P3D issue or possibly Orbx KPSP? I'm using FSAeroData with latest AIRAC. Thanks! sg [email protected] | 32gb RAM | EVGA GTX1080 8gb | Mostly P3Dv5 (also IL2:BoX, DCS, XP11)
December 2, 20205 yr not a local ...... but my understanding of charts etc. is that approach / departure is with Socal Tracon (& as per fsad), hence no frequency named Palm Springs departure. sounds like a tweak is needed to the afcad to eliminate the confusion (& what vox reads) others may know better in this local. for now, cheers john martin
December 2, 20205 yr Author That makes sense to me. Looking at KPSP in ADE, it lists Palm Springs approach and departure at 126.70, and Los Angeles center at a different frequency. SOCAL center must be coming from the sim or FSAD, not the afcad? I'll try deleting the approach and departure in ADE and see if SOCAL takes over... [email protected] | 32gb RAM | EVGA GTX1080 8gb | Mostly P3Dv5 (also IL2:BoX, DCS, XP11)
December 3, 20205 yr 2 hours ago, Gridley said: I'll try ...... if FSAD has the higher priority (ie above KPSP). for now, cheers john martin
December 3, 20205 yr Here's a bit more detail regarding SOCAL Approach, in addition to what @vadriver wrote above: https://www.wingsbywerntz.com/private-pilot/expanding-the-envelope/cross-country-training/socal-communication#:~:text=For example%2C “Squawk 1234%2C,or below 2%2C500 until advised”. You could also try adding revised KPSP comms to a file, KPSP.XML which will override anything in the P3d5 scenery library. The file should be located in: C:\Users\<USERNAME>\AppData\Roaming\Internal Workings\VoxATC P3D 5\apdata Use one of the other files in that folder as a template. There's a thread here somewhere else in this subforum, which explains all the "apdata" xml file options. I assume that this method still works in 7.43. I can't locate that thread, but here's a post that explains some of it: Multiple frequencies exist in RL to allow for more precise ATC with geographic sectors. VOXATC does not store this directional information as best I can tell, so it uses the first frequency it discovers. Also, VOXATC does not recognize FIR/TRSA/Center vertical sectors and the same logic applies.
Archived
This topic is now archived and is closed to further replies.