Since the last update of FS2024, the Navigation instruments are not working:
When tuning the frequency of a VOR either on NAV1 or NAV2 (GNS530 or GNS430), the station name and distance to the station (if there is a DME) are not displayed. The OBS are not working (dont capture any signal from the station. No TO or FROM).
Same problem with the ADF. When tuning the frequency of a NDB, the needle of the ADF doesn’t move toward the station..
Those bugs are observed in the C172 default.
I don’t have those bugs with my radio hardware in FS2020.
Additional bug. Since sim update 1, the trim wheel is inverted!
When using a home cockpit, the output in the sim moves inverted compared to the physical input (wheel movement)..the wheel used to work perfectly in FS2020 through air manager and it stopped working in the good direction in both sims since January, when the update came out in fs2020 and fs2024.
Assigning switches to my joystick, tim moves in the correct direction. In the case of your configuration I could not say. Maybe a binding issue ?, you can invert in the configuration profile the way you want an action to act.
Maybe some users can make recommendations on what exactly to check.
Unfortunately, no. The trim wheel is a potentiometer with a code from air manager that always worked in the good direction.
It is like 1 instead of -1.
The values can’t be edited in their code. To have it working, it would be to resolder the wires in the other way around.. which doesn’t make sense since it worked until January in both FS2020 and FS2024. (It stopped working after the first updates post Christmas time).
Regarding the OBS and ADF, checking now in your airport
I can’t quite see what you are doing, but for OBS to work you would need to have a flight plan, even if it’s only a single destination way point. You then enable OBS, and it makes that waypoint behave like a VOR. You would still be in GPS mode, not VLOC. If you were actually tuned to a VOR, and in VLOC mode, you don’t need OBS.
Interestingly I don’t seem to be getting a signal from NDB PI either on 360, and I’m only ~2nm from it.
Regarding OBS, if I do a direct to KCLW, OBS works as expected.
Sure, and I just checked that although my Navigraph data is a cycle back, it does include PI, as I can see it on the nearest screen of the 530. I’m also on the SU3 beta.
I ran another test after this, to do with partial panel failures, and I did it over the ocean. When I wanted to test some avionics failures I teleported the plane back to KCLW, and was surprised to find the ADF worked this time. No idea why. Same place, same-ish location, but the only difference was I spawned in the air over water, rather than on the ground powered off.
I was in air as well. I took off to try to capture it,but didn’t work.
Regarding OBS,I never had to use a flight plan for it to work, as IRL..I have the same issue by the way with the OBS2.
P.s: it worked fine when I was with the beta 2( I reverted back to official stable release to be able to see friends in multiplayer.. other bug)
I think you might have misunderstood the recommendation to reverse the input. No one is suggesting you change the physical aspects of your equipment. Just use the “set inverted axis” in the controls setup of the sim. (see the screenshot. I used my rudder axis, but it’s the same if you’re using an axis for the trim).
If it’s only this one plane with the issue, just save it to that plane’s control profile. If it’s affecting all your planes, then set it as the default for everything.
Hope that clarifies it for you.
Regards
and report back.
