On aircraft with a GPS you can switch the OBS between VNAV and GPS mode. When you have it set to GPS and then switch to an aircraft variant without GPS, the OBS are still set to GPS and because there is no button, you can’t change it and thus the nav-radios are useless.
FREQUENCY OF ISSUE
all the time, tested on C172 and DHC2 beaver but it’s likely a common problem in the nav system.
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
load an aircaft with GPS, set the OBS mode to GPS
load an aircraft without GPS and try to use the nav-radios, it’s stuck to GPS track even though it has no GPS.
YOUR SETTINGS
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 User Support Hub.
Could provide a 1st party aircraft with a GPS and 1st party aircraft without a GPS for which you experienced the issue so that devs/users can try to replicate the same scenario ?
You’ve added the C172 tags but I understand that both versions (G1000 & Classic) have a GPS through the Garmin avionics.
In that case, try with the Vikingair DHC2 beaver. I just flew it a few minutes ago and had the issue. on the previous flight I’d done GPS navigation (in the C172) and on this one I was given, by the mission, a Beaver without GPS, but since the OBS mode is stuck in GPS, the nav-radios can’t be used. It’s most likely not an issue with the aircraft or the radios, but rather with the underlying code, which should prevent even the possibility of an OBS being in GPS mode if no GPS is installed.
Also I added the tags but really the tag I was looking for, of the base game coding itself, wasn’t there So I picked one of the aircraft I just had the issue with, but the DHC2 would have been a better tag.
Did a test and it seems the root cause is not the fact to have loaded at 1st place an aircraft set to GPS mode but it is an issue with the DHC-2 nav avionic as reported here: DHC-2 Radios - VOR navigation not working
Moved to User Support Hub since a report already exist for this issue.