Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.
actually, MV22 have it own saving system, it more custom, not predefine.
VTOL mode is a real time calculation. saving isn't problem, but how fast aircraft will ready at VTOL: Read the saving file, load into sim, read by dll gauge, sent to VTOL xml, calculated by xml, dll get feedback from xml, sent to sim, receive by the sim and aircraft already fall on the ground ( depend on height though). it not recommended.
by now, still focus on MSFS.
Firstly, thanks for the helicopter!If you need any help with the flight model for MSFS, I am glad to assist! The osprey looks great already!
I should have putThat's why I object to your statement
""
I stumbled on this F-35B project, it has working thrust vectoring;
"
No, it doesn't.
It's just able to more-or-less jump vertically off the ground.
That's all .....
For anyone who wants to experiment, I have managed to effectively merge the two engines by customizing a UCR v0.1.22 plugin. The master throttle axis is multiplied by the thrust vector axis. Individual throttle axis's are the output, the lift engine is the inverse ratio of the main engine.Given time, with a wasm gauge it might be possible, but it will still be clunky.
Yes I know it's impractical, just for experimentation (possibly useful for developers).better you make your own thread @Essex. Osprey will not use that stuff.