1 hour ago, Alvega said:

That is explained in the their thread on the Microsoft forum (see the first post): https://forums.flightsimulator.com/t/working-title-g1000-nxi-discussion-thread/435492

 

 

Well that's handy,  because I've been using slot 1 the entire time anyway.

We are actively soliciting people that use this AP panel to assist us in resolving this bug. If you want to help, stop by our discord and send me a message, or send me a message on here...

Hi,

Unfortunately I do not understand all the technicalities, but I think I understand that with the next update the WT G1000 NXI will work correctly with all peripherals (in fact the only thing that does not work well is the altitude).

I hope that there will be a solution for all MFSF users (whether or not they use software like spad.next or similar).

Regards.

21 minutes ago, cwburnett said:

We are actively soliciting people that use this AP panel to assist us in resolving this bug. If you want to help, stop by our discord and send me a message, or send me a message on here...

Hi, cwburnett,

I've bought Logitech Multi Panel (AP) last week. I'm very satisfied with it! 

But today I've installed the WT G1000 NXI and the Altitude gone crazy (it shows 990000 or something ijke that). The altitude knob of the Panel is not working at all (the altitude is not changing) and the leds of blink continuously!

So, I decided to uninstall the WT G1000 NXI. But I'm a bit worried about the next update and that I won't be able to use my peripheral.

Thank you and regards.

Edited September 3, 20214 yr by John Fields

For users having hardware problems with selected altitude display, please have a quick look at the known issues page for more info - we've got notes in there for the Logitech and SteamDeck.

https://www.workingtitle.aero/packages/nxi/issues

9 minutes ago, cwburnett said:

For users having hardware problems with selected altitude display, please have a quick look at the known issues page for more info - we've got notes in there for the Logitech and SteamDeck.

https://www.workingtitle.aero/packages/nxi/issues

Logitech is to blame for this all the way. Their plugins are the bare minimal to support the hardware. There is no re-mapping functionality. So if you have a logitech panel, you need to buy Spad.next

I had an issue in my one flight since the update with the NAV function failing to engage my flight plan. Could not do it with the AP keys on my Honeycomb Bravo or with the mouse.  I stayed in HDG mode and tried several things.  What finally worked was performing a Direct To function in the MFD to the first waypoint in my flight plan.  NAV function began to work and was fine from there on.  The NAV led indicator on my Bravo never illuminated.  The APR led and or key function also may not be operative.

24 minutes ago, cwburnett said:

For users having hardware problems with selected altitude display, please have a quick look at the known issues page for more info - we've got notes in there for the Logitech and SteamDeck.

https://www.workingtitle.aero/packages/nxi/issues

The Carenado C182T also displays 99000 on the autopilot, although it does level off at the G1000 set altitude.. just looks a bit distracting..

1 minute ago, Bert Pieke said:

The Carenado C182T also displays 99000 on the autopilot, although it does level off at the G1000 set altitude.. just looks a bit distracting..

I didn't realize the C182T had an AP separate from the G1000. Interesting, I guess that one is also looking at SLOT 0 for the selected altitude.

10 minutes ago, fppilot said:

I had an issue in my one flight since the update with the NAV function failing to engage my flight plan. Could not do it with the AP keys on my Honeycomb Bravo or with the mouse.  I stayed in HDG mode and tried several things.  What finally worked was performing a Direct To function in the MFD to the first waypoint in my flight plan.  NAV function began to work and was fine from there on.  The NAV led indicator on my Bravo never illuminated.  The APR led and or key function also may not be operative.

We are hopefully pushing a hotfix to address most hardware AP issues today - not sure if it will make it to the MP today, but we'll try.
When you tried to activate NAV via the mouse, did GPS arm? Did you see GPS in grey letters to the left of HDG in green?

2 minutes ago, cwburnett said:

We are hopefully pushing a hotfix to address most hardware AP issues today - not sure if it will make it to the MP today, but we'll try.
When you tried to activate NAV via the mouse, did GPS arm? Did you see GPS in grey letters to the left of HDG in green?

Was in a surprised and reactive state of mind and did not know to look for those, LOL!  Have another flight tomorrow. What I experienced was that NAV mode did not appear on the PFD and attempts to engage NAV seemed to toggle ROL mode.  So as I reported, with the MFD I executed a Direct To for the first waypoint in my flight plan and was then able to enter NAV.  Noted the hardware issue and will wait for your efforts there.  Thank you for responding/assisting.

2 minutes ago, fppilot said:

Was in a surprised and reactive state of mind and did not know to look for those, LOL!  Have another flight tomorrow. What I experienced was that NAV mode did not appear on the PFD and attempts to engage NAV seemed to toggle ROL mode.  So as I reported, with the MFD I executed a Direct To for the first waypoint in my flight plan and was then able to enter NAV.  Noted the hardware issue and will wait for your efforts there.  Thank you for responding/assisting.

Yea, let me know. For hardware, if that was the issue ... update incoming. However, if you notice that GPS appears in grey, that means that GPS (LNAV) is armed, but not active. It will not activate until you get within activation criteria (less than half scale CDI deflection and an intercept course with the magenta line). Arming is new in this update, so some people have not realized that just like the real unit, you have to manually get the plane into activation criteria before it will go from armed to active. But, if you don't see it armed at all in the FMA on the PFD, then that's definitely a bug. Let me know how the flight tomorrow goes and thanks for the feedback. 👍

 

This is how to fix the 99999.   

I notice that the multipanel's VS button seems to be bugged out.   The VS button on the G1000 still works,  and the multipanel still reflects the proper led state though.    (Disregard that.  It  works,  I'm just stupid.  I forgot to update to todays version of the NXI in the marketplace)

Autopilot Altitude Lock Var:1 (GPS Altitude Lock)

Autopilot Vertical Hold Var:1 (GPS Vertical Speed)

 

Edited September 4, 20214 yr by Waldo Pepper

10 hours ago, Waldo Pepper said:

 

This is how to fix the 99999.   

I notice that the multipanel's VS button seems to be bugged out.   The VS button on the G1000 still works,  and the multipanel still reflects the proper led state though.    (Disregard that.  It  works,  I'm just stupid.  I forgot to update to todays version of the NXI in the marketplace)

Autopilot Altitude Lock Var:1 (GPS Altitude Lock)

Autopilot Vertical Hold Var:1 (GPS Vertical Speed)

 

Hi, Waldo,

I did what you say. I changed LOCK VAR to LOCK VAR 1.

Now I can set the Altitude with the Logitech Multi Panel (AP) knob (it flashes 99.000 every time you set the altitude, not a real issue though).

The problem is that none of the panel buttons (AP, HDG, NAV, IAS, ALT, VS, APR, REV). They are inactive (no light) and they don't react to.

So, for the moment, a can't see a solution for my problem with G1000 NXI and Logitech Multi Panel with or without spad.next. 

I hope Asobo or WT or Logitech will fix this issue soon.

Regards. 

Edited September 4, 20214 yr by John Fields

6 hours ago, John Fields said:

Hi, Waldo,

I did what you say. I changed LOCK VAR to LOCK VAR 1.

Now I can set the Altitude with the Logitech Multi Panel (AP) knob (it flashes 99.000 every time you set the altitude, not a real issue though).

The problem is that none of the panel buttons (AP, HDG, NAV, IAS, ALT, VS, APR, REV). They are inactive (no light) and they don't react to.

So, for the moment, a can't see a solution for my problem with G1000 NXI and Logitech Multi Panel with or without spad.next. 

I hope Asobo or WT or Logitech will fix this issue soon.

Regards. 

That's the craziest thing about this sim,   so many of us have different experiences with it.   I guess that's only logical, with all the myriad hardware and software combinations in the world.

Anyway,   Good to hear from Working Title that SU6 fixes the 9 issue.

Edited September 4, 20214 yr by Waldo Pepper