Avionics plugin g3000/g5000 conflicts with FSReborn Phenom 300

As with many planes with a g3000, the phenom’s FMS speed (magenta on the PFD) is supposed to be controlled by the g3000, including the flaps settings, VNAV climb schedule, flight plan constraints, etc.

When the navigraph-avionics-g3000-g5000 folder is present in my MSFS2024 community folder, this FMS SPD setting malfunctions, and just sets itself to whatever the MAN SPD setting last was.

tests I’ve done:

When my community folder is totally empty, the FMS SPD works properly.

When my community folder is totally empty EXCEPT navigraph-avionics-g3000-g5000, I get the bug.

When all of my various mods and planes; about 3 dozen folders EXCEPT the navigraph-avionics-g3000-g5000 are loaded into community, the FMS SPD works properly.

Update: found the cause, and it isn’t specific to the Phenom

Some follow-up after more digging:

1. It affects every G3000 aircraft, not just the Phenom. With the plugin installed, the stock Longitude does the same thing. On the ground the FMS speed defaulted to something low (~85 kt) instead of the Flaps 1 limit, same as the Phenom.

2. The cause looks like the plugin’s settings save slot. In plugin v2.5.0, NavigraphG3000MfdPlugin.js → initGlobalPersistentSettings() creates a G3000UserSettingSaveManager and passes it the host aircraft’s fmsSpeedsSettingManager. It then calls load("navigraph") and startAutoSave("navigraph"). That save key is the same for every aircraft, so the aircraft’s FMS speed settings get saved to one slot shared by all G3000 aircraft. Those settings include the flaps/gear configuration limits (fmsSpeedConfigurationLimit_N), the speed schedule selections, and the pilot-entered speeds.

Because the plugin loads during plugin installation, this happens before the stock G3000 loads the aircraft’s own <aircraftKey>_g3000-default-profile. The SDK’s UserSettingSaveManager.load() only overwrites settings that profile has actually stored, and settings are only stored when their value changes. So any FMS speed setting the aircraft’s own profile never saved keeps whatever value was in the shared navigraph slot. That carries stale values from one G3000 aircraft into every other one, every flight.

3. That explains why only some people see it. The bad data is saved per user (the sim’s DataStore, which on the Store/Game Pass version appears to be synced with your account). Clearing the Community folder, or reinstalling the plugin, never touches it. Users whose navigraph slot never picked up a non-default value won’t see anything wrong.

4. Confirmed fix on my end: I cleared all keys under persistent-setting.navigraph.* from the DataStore, then reinstalled the stock, unmodified plugin. FMS SPD now works correctly in the Phenom, including the Flaps 1 default on the ground and VNAV/schedule speeds. I wiped the whole slot, so I can’t say for certain which key was the bad one. My best guess is one of the configuration-limit settings.

Suggested fix: don’t pass fmsSpeedsSettingManager (or any aircraft-specific settings) to the plugin’s save manager. Pass undefined and persist only Navigraph’s own settings. Alternatively, include the aircraft in the save key. As it stands, the existing bad data in users’ navigraph slots would also need clearing, or ignoring, for anyone already affected.

Happy to provide more detail if useful. Environment: MSFS 2024 (MS Store), navigraph-avionics-g3000-g5000 v2.5.0, FSReborn Phenom 300E (Marketplace).