G1000 does not allow editing or leg selection in [FLP] page

ISSUE DESCRIPTION

Description of the issue:
The G1000 does not offer any button navigation to select next leg or direct to or FPL waypoint editing.

If applicable, which aircraft is experiencing this issue:
I have tested it in SR22 but it might be happening in other aircraft which use G1000.

FREQUENCY OF ISSUE

Every time

REPRODUCTION STEPS

1.Get in SR22 and load a flight plan.
2.Go to FLP page and try to edit or change active leg.

[END OF FIRST USER REPORT]


:loudspeaker: 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:
•

Could this be down to the lock controls?

Left click on the right knob of the G1000 and keep holding left click and then press Mouse 4. Does that cause it to push?

This may be related to the Bug I opened where pushing the FMS button does not highlight a waypoint on the Flight Plan. The FMS knob is typically how you navigate the flight plan to make edits.

I have experienced this in the 172 and 208. Best I can do is Direct To and type in the waypoint. And when I reach the end of the leg, Direct To again for the next waypoint. Yeah, I could just preload the flight plan from the planner, but I like to punch it all in manually. If I have to make a change to a preloaded flight plan, cant do that because the FMS knob in the game doesnt function appropriately.

Does this report resolve the issue? I am able to navigate the FLP page just fine, but not the same way I did in 2020. C172 G1000 Knobs Not Clickable in Legacy Interaction Mode - #10 by DerFluch21

Further to this, the knob doesn’t support activating/deactivating the cursor on both PFD and MFD. Basically, the unit doesn’t work as in 2020.

This bug is incredibly annoying. I’m unable to enter the fight plan in the G1000 (make changes, etc.). The only thing you can do is go Direct To a waypoint and it works great. You can’t change/add the origin/enroute/destination/etc (normally you would press in the FMS button to highlight and then scroll to make changes - just like the real plane but it nothing happens when you press it in).

This is how I use flight sims (load into an airport and program the flight plan myself). Until this is fixed, I’ll watch others play :confused:

There is already a bug opened for this.

SR22T FMS Knob (Push) not Functioning - #2 by ondrejfencl.

Confirmed.

Here’s a temporary workaround: double-clicking both mouse buttons simultaneously while hovering over the FMS, HDG, RANGE, COM, NAV, or CRS/BARO buttons works as pushing the knob when in legacy control mode. It’s clumsy, you have to be pretty precise, and it doesn’t always hit it, but it does work.

When in legacy control mode, the mouse cursor does not change to a “fingerpush” when we hover over pushable buttons on the G1000 like we had in 2020.

1 Like

I take back my contribution to this bug. I discovered that simply right-clicking the FMS knob acts as the push function (different than fs2020).

Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes

Provide extra information to complete the original description of the issue:
• In addition to the 172 G1000 FPL being unable to be navigated, I just suffered a total UI freeze. I was doing a ferry flight mission, and was climbing to cruise. I tried to adjust the course to a direct to my destination, and the G1000 MFD froze, after I pressed the lower right knob button. I then found I couldn’t interact with the virtual cockpit at all, not with the mouse, not even pressing the Esc key brought up the menu. My physical throttle didn’t do anything either, but I could raise/lower the flaps with the Logitech panel lever. I ended up ALT+F4’ing the sim as there was no way to quit, and no way to land either. I just remembered that I had also clicked on the little keyboard icon to type in the ICAO of my destination. Maybe that did it?

If relevant, provide additional screenshots/video:
•