Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.
Yes
Brief description of the issue:
When saving a flight if any of the radios are tuned to an 8.33 kHz spaced frequency it is not saved correctly. For example if the radio is tuned to 121.805 when the flight is saved it will be saved as 121.800 when the flight is reloaded.
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
Tune radio to an 8.33 kHz spaced frequency (e.g. 121.805), 2. save flight, 3. reload saved flight and check radio frequency.
PC specs and/or peripheral set up if relevant:
Build Version # when you first started experiencing this issue:
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
It happens with all aircraft, when you save a flight the radio frequencies (along with all other switch positions etc) are saved in the ****.flt file, you can open the ****.flt files with a text editor to see this.
25kHz spaced frequencies seem to be saved and restored correctly but 8.33kHz spaced frequencies are not.
Possibly, but I think this is more likely to be related to left over code from FSX being used. FSX only had 25kHz spacing so frequencies would be 118.000, 118.025, 118.050, 118.075… and so on. With 8.33kHz spacing there are additional frequencies 8.33kHz above and below each of those steps and it is these that are not being saved correctly.
The INC & DEC of 8.33khz spaced frequencies is not reliable (to put it nicely)-- rather than just adding/subtracting 9.33333kHz (and roundingoff) it should set the frequency to EXACTLTY the correct 8.33 spacing Frequencies.
I believe the pms50 GTN750, check the 8.33kHz frequencies, and programmatically does not allow an Incorrect (inaccurate) 8.33 Khz to exist, without correcting it
I’ve not noticed any issues with the INC / DEC function, that seems to work as I would expect it to. The steps I get are:-
000
005
010
015 025
030
035
040 050
and so on…
When the frequencies in bold are selected the radio would be operating in 25kHz bandwidth mode and when any other frequencies are selected it would be in 8.33kHz mode.
Ah OK, I don’t really use the GPS much so wasn’t aware of that, I’m more of an airliner man I have a self built hardware radio panel and that always works as expected for me.
The panel is connected via Mobiflight and uses the relevant INC and DEC events so it’s not possible to enter an invalid frequency (which of course would be the case with a real world radio!). The “bug” I am reporting is that even when a valid frequency is set on the radio it is not saved correctly in the FLT file when you save a flight.
It’s not particularly a big issue for me, just a minor irritation and there are many other things that really DO need fixing and are far more important (the c***py ATC springs to mind!). I just thought as I had noticed it I would report it and let Asobo / MS decide if they want to fix it or not (I won’t hold my breath )
Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
For anyone who wants to contribute on this issue, Click on the button below to use this template:
I have a self built hardware radio panel and that always works as expected for me.