One thing that is really frustrating is the lack of acceleration for the heading bug and altitude selector for lack of a better term. Like we had in FSX and even P3D. This is also present in real airplanes too. Right now when selecting a heading that is say 180 degrees off your present heading, it takes forever to set (mouse or hardware doesn’t matter). Same with altitude when you’re going from let’s say 3000ft to 40.000 ft.
Frustrated me too, especially since I fly in VR only, but now I use VoiceAttack and HCS and can just simply say “set heading to 163”.
It used to be a thing in the base avionics and even in the WT mods. The G1000NXi and new AAU I avionics removed the acceleration completely. And it also blocks external hardware and software that has built in acceleration from using it too.
It was reported during the AAU I beta both here and on the WT Discord, but the topic was never addressed or acknowledged. So no one knows if they’re aware or there’s any intent to fix / restore this.
That’s too bad. In my case it’s been an issue since the release of the sim. I’m using Honeycomb Bravo, but it doesn’t make any difference if I’m using my mouse. Takes forever to set 40.000 ft on the autopilot.
On the Vision Jet which currently still uses the old G3000, I use the Bravo knob for altitude. After a few turns, it accelerates and start incrementing by steps of 1000 instead of 100. The heading knob, which I use Air Manager and my Knobster for, also has acceleration in that plane.
The TBM used to that as well, as did the HJet. I noticed this stopped working with AAU I. So now the TBM, Longitude, and now the new HJet as well. There’s no longer acceleration on their control.
Even Air Manager, which has a built-in acceleration function that can be enabled or disabled at the instrument level, ignores knob acceleration for any of the avionics tied to AAU I. I discovered this was also a thing in the G1000NXi, so I’m guessing it’s something in the core codebase for all these new instruments causing this.
2 Likes
Well, in the NXi, you left click and hold on the heading bug and then move your mouse left or right. It moves as fast as you want. Not sure about altitude bug selectors – I fly the C172.
The NXi wasn’t really noticed in terms of altitude, because it has concentric knobs to adjust 100 and 1000 foot increments.
When using the APs in planes like the TBM, Longitude, CJ4, SR-22, or other planes who have a single knob for altitude, this is a step backwards. Having to make a large altitude changes with limited speed 100 foot increments is difficult.
Also, many folks use external controls like their Logitech AP panel, Honeycomb Bravo or other external controls for that. We’re the folks really noticing this regression. People using a mouse, probably not as much, particularly if youre using modern interaction.
If you click the knob in on the G3000/G5000 related MCPs it switches from 100’ increments to 1000’ increments.
Yes, in the virtual cockpit that works. That’s of no help to people using their external Logitech AP, Honeycomb Bravo, or other 3rd party hardware. That’s not an insignificant number of folks. People buy these things specifically because they don’t want to have to control this stuff with a mouse. Knob acceleration was in the sim specifically for these people. Now it’s been removed. Likely unintentionally. But it’s been removed nonetheless.
I don’t currently have a knob mapped, but doesn’t that toggle then allow the regular call to cause it to go by 1000’ steps? That’s how it was with the WT G3000 IIRC.
These AP units are a single knob without a press function. What you’re suggesting still requires the awkward steps of first clicking the knob in the VC, then using the physical knob. If you ahve to use a mouse in order to use your external hardware, you’ve defeated the purpose of the external hardware in the first place.
Acceleration used to be in the old avionics specifically to counter this. It needs to be brought back to the new ones.
ah, and mine had a pushbutton that was mapped I think to an LVar through fsuipc.
I think I’m now better understanding what’s going on.
Yes. Using 3rd party software, you can do this. Most regular users out there affected by this regression aren’t using Spad, AAO, Mobiflight, Air Manager, etc nor care to. They just want their shiny Honeycomb Bravo or Logitech panel to work out like it did prior to AAU I.
1 Like
Wait the Nxi. ……runs off to try ………..
I tried the Nxi in the Bonanza and my acceleration is working just fine for the heading bug. I’ll check the G3000 and report back.
EDIT: I tried the TBM also and that works just as well. Are you sure this isn’t a community folder conflict or something else.
Strange. I don’t have the acceleration any more off my Honeycomb for AAU I avionics. I’ll try emptying the community folder in case and test again this evening.
That may well be the case for the HV if something in the sim has changed. I was responding to what you said about AM acceleration not working with the WT units since AAU1.
1 Like
I have altitude and heading set to buttons on the flight stick and they move plenty fast (especially altitude which wizzes up and down with great speed), it even moves the altitude knob on the Flight Director (the heading knob does not move). I use Spad Next for a lot of controls but not this, it’s just the basic FS key binds, I’m not doing anything special.
Acceleration isn’t working on my ALT knob with the TBM. Or it wasn’t last I tried it. I’ll try again this evening to confirm. It’s been a bit since I’ve used it.
Didn’t try the ALT only AM HDG bug. I can try ALT but that’s much less of an issue because I use the knobster inner/outer knobs for 100/1000 ft changes even for the non concentric ALT knobs.
Yeah, I’ve retrofitted my AP panels. Even the ones with a single knob, I’ve added a user prop to optionally enable dual knobs.
1 Like