Trevor Bagnell in Canada recently reported that when NAV1 radio is controlled by the GPS signal under a filed flight plan, the Standalone C172 VOR1 gauge (Integrated as well) doesn’t respond accordingly.
With no flight plan, he said, the localizer needle on the VOR1 of course remains centered when the NAV/GPS Switch is toggled to GPS.
But when a flight plan is active, the NAV1 radio will be controlled by the GPS signal. The localizer needle on the VOR1 should deflect accordingly.
The virtual panel gauge localizer needle reacts to being off the centreline of the flight plan. The FIP gauge does not, he added.
Trevor submitted a video explaining the case as follows: Continue reading

indication of wind direction so as to render a more realistic appearance.
Indeed, the recent drivers from Saitek have brought improvements over older versions. That’s no doubt about it. But they are still lack of flexibility and configurability. Especially, the company’s FIP driver still only support a subset of the simulation variables. This has caused incompatibility issue among those 3rd-party aircrafts which use the simulation variables extensively in their designs.
Lately, half of my minimal flightsim time were spent on creating new FIP gauges for Baron B58 (both default & Carenado versions) and Bonanza A36 simultaneously as they share many similarities.
Compass is a bit wide. Well, it very much depends on personal preferences.