I noticed that since the new flight model update with the faster throttle response, the aircraft has no momentum anymore when you move the throttle quickly up and down, leading to some very toy-like behavior. For example when I’m hovering and move the throttle quickly up and down, the V-22 can dart instantly upward and downward like it weighs nothing:
I really preferred the old model where this wasn’t possible, the hover behavior felt a lot more immersive and challenging. Maybe it’s possible to keep the throttle response but give it some dampening so that it feels like it has some mass?
I personally find the new flight model more realistic, because IMHO it does what you are asking for. It gives a slower response to the throttle, because turbines need some time to spin up after a new throttle (target power) has been set.
However, in 1.2 I also noticed some strange “extreme” reactions during landing and hover.
I did so far not have time to try the 1.2.1 version (which has a bugfix for the “antigravity bug”)
Interesting, I’ve never noticed this issue. Perhaps I havent tried to move the throttle fast enough (my throttle quadrant has quite a bit of friction so this wouldn’t be possible)
I use a Thrustmaster TWCS with very low friction and able to move it up and down very quickly to try this. I also recently tweaked my MSFS joystick settings to remove some small delays I had configured previously, so I can’t guarantee if the throttle delay I enjoyed before was partly due to that or something new with the flight model. However, I don’t think the aircraft should be able to instantly change directions this fast in any case, it just feels weightless. I would be great if others could try hovering and yank the throttle back and forth quickly by ~30% or so.
Previous thottle model (before v1.2.0) was based on engine RPM. This resulted in the throttle not being “perfectly linear” as the engines must reach some RPM threshold where lift begins to act. This was particularly challenging for some, especially at landings, since control wasn’t fine enough.
The new throttle model bypasses the RPMs and instead uses a linear increment of the aircraft altitude on VTOL. Essentially, there is a linear relationship between throttle and vertical speed. This allows for easier handling of the aircraft on VTOL, but with no friction and aggressive changes in throttle, results in the video above. There is essentially no ramp-up of the engines.
There are a few ways of addressing this. Changing the linearity of the relationship and going for something that inherently adds a “ramp up” could be an option (eg. going for an exponential increase instead of linear). There is also the option of adding a dampening function. Regardless, both are quite complex options and will require some time to R&D.
Ultimately it seems a matter of personal choice. For me and most people, it seems that the current flight model works fine - as long as your throttle has some friction, power is not added aggressively and perhaps you tweak the power curve slightly to your liking, the aircraft will handle just fine. We can also make available the old throttle flight model, so if a customer prefers the RPM-Based model, it can be used instead.
We will be trying out a few things to improve the power curve on VTOL. Also important to mention, this issue only occurs when airspeed is nearly zero, as soon as the aircraft gains some lift from the wings, the issue disappears.
I would love the option of having the old flight model as a “hard” mode. If you’re going for realism, wouldn’t the aircraft’s response be more based on actual RPM than throttle?
I realize that if no one else likes it then it won’t be a sellable product, but maybe it’s good to challenge people once they get used to flying it. It just seems so toy-like now, to me the fun is greatly diminished, I loved how you had to “tame” this thing before.
Also, is the smoother VTOL/plane transition dependent on this throttle/RPM change? Honestly I’ll take jerkier transition vs. being able to do this hopping behavior at hover.
What if you investigate a third option … 1) rpm vs 2) throttle (desired power) vs 3) actual power (a force)
The throttle (in reality) is more about defining the “target power” … but due to physical limits it can never be reached instantaneously. (a turbine needs to speed up gradually).
However in a heli rotor system the engine RPM is limited to a certain (optimum) range during flight … and the rest is done by adding fuel and increasing the blade angle … so the power (= displaced air volume) does increase … but the RPM does not.
But then … “airflow power” can not convert instantaneously to speed … because it is more about an acceleration force … which then is countered by deceleration forces (drag, gravity … and other stuff)
But perhaps we should take this discussion to the Osprey forum … due to the forum guidelines over here at MSFS.
No changes made to external cameras, perhaps you have your camera zoomed out.
CV and CMV variants are included and matched to the corresponding included liveries. Eg. if the included Air Force livery is selected, the CV variant will show up.
An update to the livery pack will be released shortly to match these to the corresponding variants since now everyone is on V1.2.1
Just an update on the Throttle changes. The new throttle mode works very well and its a lot more realistic, with engines spooling up and taking time to react, as they should.
However, this fix does affect VRS as well, and therefore requires more work before it’s released. As a consequence of the fix, now the aircraft cannot recover from VRS, due to the way VRS recovery is programmed. We continue working on it.
This kind of honesty and openness about the development challenges is very, very much appreciated. Cheers to you continuing to make his already super fun aircraft even better. You certainly have my support going forward!
Testing final release version. If everything goes smoothly, we are expecting the update to be out in a few hours at ORBX. Marketplace, as usual, will take a couple of weeks.
Thank you for keeping us up to date. Will this update help to cure the behavior during transition from regular flight to hovering for XBOX users aswell?
