After my post I had time for one more flight, again without using any trim at all. It wasn’t perfect but within the parameters I’ve seen with other aircraft using default autopilot. It didn’t go bananas like it has on other flights.
Will do more testing tomorrow evening but I’m more convinced now that trim has something to do with it.
Interesting idea … I will try the same on my side.
After getting the Osprey up in the air … and up to 100+ ktas APLN … it does feel “tail heavy” and I also typically first trim it manually to get it leveled out … and then I play with the AP settings.
So lets see what happens when I leave out the trim part.
I have also heard that the AV-8B does use an axis for its vector trust. So an (propeller) axis sounds like a good idea.
However, it might be nice to offer multiple options … because not everybody might have an additional axis. On my side the Virpil CM2 would offer a second axis, but I often use it as a “throttle max” marker, so that I can “blindly” push the throttle to a max position, that will still be in the “green” (no overstress) range. So I guess I still would prefer to use buttons.
While I am thinking about the throttle … what I find strange is that the reaction to throttle changes seems to be very sensitive in some conditions … sometimes I need to adjust by tiny millimeter amounts. This feels unnatural … as I doubt that real pilots in real (shaky) Ospreys … can even apply such tiny throttle changes.
What is the throttle in the Osprey actually controlling … engine fuel injection … engine shaft power … torque at the central gearbox … rotor lift force (air flow) ?
Is that even publicly documented? … (or what do real Osprey pilots say)
Now I DEFINITELY will be getting touch monitors larger than my 15.6" 
By the way, haven’t tried getting it off the ground yet. Just practicing taxiing. I notice she’ll tip over rather easily. Turns have to be very wide and gentle.
The osprey is very top and side heavy (with the heavy engines and huge props located on the sides), you must be careful when turning as the aircraft can quite easily impact one of the props into the ground if you tip the aircraft.
Sensitivity has been improved significantly for the upcoming update
I’ve been testing with trim, and I can’t see trim affecting the autopilot in any way. Works as intended.
If you can record a video of the issue and send it to our email, we may be able to more easily see the issue and try to replicate it.
I did more AP tests … and it seems to me like if it is mainly (only?) airspeed related.
I will retry again under different wind (weather) conditions … but that would explain the patterns I have seen … because I usually activated the AP shortly after takeoff … and I clearly was still below 170 ktas
Nevertheless … the Osprey will be my default aircraft for the foreseeable future … this is tiltrotor tech so much fun.
I’m having an issue where if I am in a mountainous area and am moving out of APLN mode, it snaps me to the ground and crashes the aircraft. This is getting expensive in NeoFly. lol.
Details:
I thought I had it relegated to transitioning while banking or transitioning while at a higher rate of speed but I did some testing at level flight and 150 groundspeed and both times it still snapped me to the ground. The only thing I have not tried is getting high enough that the radio altimeter is not reading and then trying to transition.
Any ideas?
This is a known issue when operating the nacelles above 8000ft. It’s currently being fixed. There is a bug in the physics that regardless of your altitude, it resets to 8000ft when you operate nacelles above that altitude.
At that speed (APLN mode), is likely that the aircraft won’t be able to sustain a climb. The aircraft automatically pitches down to avoid stalling. At 170ktas you should be in conversion configuration (nacelles anywhere between 0-30deg - see page 41 of the manual)
Folks - a reminder that this is NOT a Technical Support forum. The Third Party Forums are for GENERAL DISCUSSION ONLY. This is in the Pinned Post atop each Third Party sub-forum.
You can reach Miltech Simulations on Facebook or their E-mail for Technical Support. If this thread continues to show Tech Support trending, it will be shut down. Thanks for your cooperation.
Ah, awesome. I’ll keep that in mind for now. Thanks for letting me know about the bug
I am genuinely confused now. What is allowed and what is not.
So would our discussion be ok if @LikedHare478430 would not react to us? Then it becomes a general self-help discussion. Or are we in general not allowed to talk about bugs in third party products?
After all … we all are investing our time to make MSFS a better place for everybody else. I was always thinking that this is the main purpose of this forum.
We’ve just created a forum on our website for further support and discussion. Please continue the conversation there:
First off - the Pinned Post for the record. Note the Support phrase.
Why? Historically, we’ve had to police, penalize and shut down threads where either/or the manufacturer and or a customer got into a tiff - over the product, the support, or any other potential customer interaction. That’s not efficient or sustainable for a mostly Volunteer Staff which makes up the majority of the Mod Team. Secondly, there are legal and regulatory implications for allowing someone not affiliated by Microsoft to conduct their business (i.e., tech support) on Microsoft property and systems. That’s why we adamantly make it clear - this is not a Technical Support forum.
Do we allow peer-to-peer assistance (i.e., customers or users assisting each other)? Yes. We allow a wide range of activities to occur in these forums. But we reserve the right to manage and moderate those activities at any time, and they are evaluated on a case-by-case basis.
Thank you for the first clear explanation of this policy I’ve seen on these boards. I now understand the “why” of that rule.
They have a lot of rules, but they do run a tight, peaceful, logical forum.
And I cannot wait for the Osprey to drop on Marketplace.
That is great news .. Your Own Forum
(with your own Moderators and your own Rules)
Hey, question.
Is “True-to-Life” a cemented requirement?
I’m m not a super hardcore simmer, so I have things like Damage and Fuel Usage off.
What limitations will there be once it’s released on Xbox?
Please use our forums for these kind of questions: https://miltechsimulations.talkyard.net/latest
“True to life” minus crash detection/damage and fuel usage is fine. But all other assists must be set to REALISM since they may interfere with the VTOL physics.
No limitations on Xbox. It will be the exact same product as PC.
I am loving this module. However, I am struggling with it. I have DCS and always end up finding the ground in interesting ways when trying to fly choppers.
Here, once I transition to level flight, the aircraft is yawed and I have to keep a steady pressure by using the stick to yaw to the left. I also have to hold a bit of left roll and even with this, the nose is never completely pointing in the direction of flight. I approach any waypoint from an angle.
I know that this is not a bug, but my lack of flight experience/controls. Just wondering if anyone else is having a similar situation or knows what is going on. I have not trimmed the aircraft, it is one of the only assists that I use in the sim.
Great module, looking forward to seeing how it grows over time. In the meantime, 3 cheers for always finding the ground.
