Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 28, 2019 21:46:28 GMT
Below are my various Payware airport addons like Mk-Studios etc
LOWS 133.330 Correct - 133.325
EDDN 123.080 Correct - 123.075
EGGP 124.330 Correct - 124.325
EPGD 129.630 Correct - 129.625
LEAL 120.080 Correct - 120.075
LOWI 126.030 Correct - 126.030
LPPT 121.955 Correct - 121.950
The FREQ after the ICAO identifier is the FREQ from the Airport charts and the frequency i want to change to. But somehow after saving the ADE and restarting your Airport Editor they default to the frequencies to the right (after Correct)
I’m using 737 Prosim and my VHF 1 and 2 has 8.33khz spacing.
|
|
|
|
Post by Herve Sors on May 29, 2019 11:33:32 GMT
Hello,
Even if 737 Prosim has 8.33 spacing, simulator (from FSX to latest P3D) does not manage them the reason why I default to 25 khz in such cases. I may change that (as an option) in the future although I'm unsure it will have any consequence. Some online ATC software (VATSIM & IVAO) accept 8.33 but it is only on the dedicated software side not on the simulator
Let me know what are the side effects of not having 8.33 frequencies correctly set on your installation
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 30, 2019 20:01:37 GMT
Hello, Even if 737 Prosim has 8.33 spacing, simulator (from FSX to latest P3D) does not manage them the reason why I default to 25 khz in such cases. I may change that (as an option) in the future although I'm unsure it will have any consequence. Some online ATC software (VATSIM & IVAO) accept 8.33 but it is only on the dedicated software side not on the simulator Let me know what are the side effects of not having 8.33 frequencies correctly set on your installation If you could change that in the future that would be great! |
|
|
|
Post by Herve Sors on Jun 11, 2019 6:20:08 GMT
Hello, I checked the code and there is no discrepancy here just a 8.33 channel display problem According to current assignment rules www.eurocontrol.int/sites/default/files/article/content/documents/communications/2016-03-frequency%20table.pdfsome dial channels may not be correctly displayed in the 8.33 system but are still correct As an example 133.330 is internally stored as 133.325 (real TX/RX frequency) in both the 25kHz and 8.33KHz spacing systems However, when retrieved from the BGL, it should be displayed as 133.330 in the new 8.33kHz radio system or 133.325 in the old 25kHz spacing In both cases, it will still be 133.325 in the BGL The same is true for all 8.33 channels ending by 05-30-55-80 Consequently, I will add a check box so as these frequencies are correctly displayed as 8.33 channels if required by user Now be aware 8.33 spacing is not fully supported by FS/P3D (especially by internal ATC, AI traffic and most aircraft COM equipments) even if the compiler accept it when channel is correctly converted to real TX/RX frequency (see table). Consequently, including 8.33 frequencies inside BGLs may have unpredictable effects |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 15, 2019 10:12:25 GMT
That check box will be great please. Will this be with that nav data update you release? I can only test and see how i get on with the new 8.33khz spacing in the BGL
What do you think?
|
|
