Control Splits Modeled?
-
@Black-Square This is gonna be totally crazy (in a good way) if you did, but are throttle control splits actually simulated? Currently climbing through FL250 with the torques and ITT's perfectly matched, and in order to do that, my power levers are split about half an inch. Not my hardware, it looks that way in the virtual cockpit too!
If this is really a feature, its awesome. When you fly a non-FADEC twin in real life, the power levers never match up exactly to produce the same power on each engine. Theres always slight differences in the rigging.
-
There has actually been some discussion on this in the past with my aircraft. I program my engines such that they are never exactly the same, since you're absolute correct about this being realistic. Unfortunately, the engine simulations in MSFS are always identical, so it's just some trickery to give you the impression of minute differences, but that's as real as you want to it to be, I suppose!
-
It adds a lot of immersion when the engines are not 100% in sync. Thanks for doing this @Black-Square.
-
Is it a default behavior of MSFS for throttle/prop/mixture axis levers for multiple engines to sync themselves together when the axis positions are close?
I hadn’t noticed all my airplanes doing this until recently when I bought a VIRPIL throttle and control panel with very high resolution axes. The behavior doesn’t bother me most of the time, however it bugs the hell out of me with Starship because the engine split is juuuuuust inside the range where my throttle axes will snap into sync.
Just wondering if anyone else notices this.
-
Is it a default behavior of MSFS for throttle/prop/mixture axis levers for multiple engines to sync themselves together when the axis positions are close?
I hadn’t noticed all my airplanes doing this until recently when I bought a VIRPIL throttle and control panel with very high resolution axes. The behavior doesn’t bother me most of the time, however it bugs the hell out of me with Starship because the engine split is juuuuuust inside the range where my throttle axes will snap into sync.
Just wondering if anyone else notices this.
@C525B I think you will find that it is virpil who sync a throttle pair when they are closely aligned, you can see it happen in the VPC config tool. I also have a Virtual Fly TQ Neo and that doesn't do that fortunately.
-
@C525B I think you will find that it is virpil who sync a throttle pair when they are closely aligned, you can see it happen in the VPC config tool. I also have a Virtual Fly TQ Neo and that doesn't do that fortunately.
-
@C525B I think you will find that it is virpil who sync a throttle pair when they are closely aligned, you can see it happen in the VPC config tool. I also have a Virtual Fly TQ Neo and that doesn't do that fortunately.
@Andydigital Thank you for sharing this with me, as well. I had heard users mention this "feature" of "mine" in the past, and I thought they were crazy! Very good for me to know.
-
Thank you! I was googling this like crazy thinking it was an MSFS feature, but found nothing. Can this feature be disabled in the VPC utility?
@C525B said in Control Splits Modeled?:
Can this feature be disabled in the VPC utility?
Yes look on the Axis page in VPC Config and set Sticky Dead Zone to whatever you prefer. On my VMAX Prime it's set to 4% by default, I just changed it to 2%
-
@C525B said in Control Splits Modeled?:
Can this feature be disabled in the VPC utility?
Yes look on the Axis page in VPC Config and set Sticky Dead Zone to whatever you prefer. On my VMAX Prime it's set to 4% by default, I just changed it to 2%
@Andydigital Thanks very much! I looked in the configuration tool manual and it doesn’t explain anything about the dead zones enabling “sticky” behavior…it’s completely undocumented.
-
Yes that is true @C525B , unfortnately very few companies write excellent manuals like Black Square do.
