With last update Pilatus, with G1000, altitud selector in Saitek AP panel is not working for me…
Perhaps there are other G1000 planes too.
No addons, no modifications, vanilla MSFS.
I will agree feedback about this.
Thks a lot.
Albert.
Other planes with G1000, works properly.
Not all tested, anyway, Pilatus G1000 cant up and down altitud selector.
Cheers my friends.
And you are using the standard Logitech driver I assume? Stock G1000 or with the Working Title NXi mod?
It may be that they have changed the coding in the Asobo Pilatus G1000 so it triggers a different simevent* when you alter the ALT selector and that this new event is not recognised by the Logitech driver. It is is not uncommon for the Logitech driver to give patchy performance, particularly with 3rd party aircraft but also with some of the Asobo.
Also the WT G1000 has some custom events associated with it I believe that the Logitech driver may not recognise.
I’m not sure what changes may have been made, but someone using a specialist driver software like SPAD.next should be able to see what the events are
*this is the code that gets triggered when you click on something in the virtual cockpit or when the SIM receives input from an external controller/device
The default Logitech drivers for those panels are horrible. Really, if you use Logi / Saitek panels, you really need SPAD.next. That’s really the only way to use those panels effectively. Unfortunately, it’s a paid program. It sucks to have to pay more to use hardware you already paid for. But if I still had my Logitech panels, I would be using SPAD without question.
For me the Dec ‘21 Logitech drivers drive my many Saitek/Logitech peripherals like a charm. SPAD not needed at all.
It all depends on what aircraft you fly. The CRJ, WT CJ4, PMDG 737 and SWS Kodaik all use custom events that the Logitech driver will not find
It’s also worth noting that SPAD or Axis and Ohs or similar allows you to get much more out of your devices than the basics. I use the radio panel to set my barons, to set minimums, to control all my G1000 buttons and dials etc. And for me, that’s priceless.
But this is not helping the OP with their problem. I would go look at the PC-6 but my motherboard died yesterday. RIP
For me too, i had some problems in 01-2022 when begin with MSFS202 and autodisconect USB make me crazy, but I could solve it.
Respect this issue with aircraft, seems all other planes works properly.
In fact, for me is not a really problem, is only to share knowlegment.
About SPAD next, I saw a lot of “learning and configuration” videos, and for now, I think, IMHO, I dont need it.
As you talk about, drivers from 21 works in the way they are designed, but, I know, there are people who need go in deep for some kind of config that my little brain can not understand.
No problem with this option, but is not for me.
Cheers to all .
Confirmed, is an issue with Asobo Pilatus.
If you assign in keybord config up or down altitude , works on any other planes than Pilatus.
The only way for work is interact directly with the G1000 altitude knob.
No Logitech drivers related, period.
Cheers to all
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.