Since the beginning, variables ROTATION ACCELERATION BODY , ACCELERATION
BODY and ACCELERATION WORLD were always read only. In 1.15.7.0 release
notes I have seen SimConnect:
Exposed ROTATION_ACCELERATION_BODY_X/Y/Z Simvars
and tested it straight away - I can swear it worked, and much smoother than ROTATION VELOCITY , so I kept in mind several ideas how it can be used. But
now it no longer works, checked the docs - even more vars marked as settable,
but none actually affect game physics. SimConnect does not return the error on
attempt to set such vars, so I believe it is a matter of the unit, or just a
code bug. Please clarify this point as these variables are critical for any
kind of physics manipulations. p.s. more logical unit for ROTATION VELOCITY
is radians per second
Hello. I’ve just tried to write to the ROTATION simvars using SimVarWatcher
and had no issues both on the official retail and preview build. Note that
your value will be overwritten in the next loop so this will not be visible
directly in the SimVarWatcher. But your aircraft rotation should be impacted
when writing those values. Also make sure your aircraft is not on the ground
when testing this. On the other hand, all ACCELERATION BODY and ACCELERATION
WORLD simvars don’t seem to be writable at the moment. I suspect this was
never supported by the new flight model and we will inspect this further…
Finally, as for the unit used for ROTATION VELOCITY, I agree but we kept the
legacy unit from FSX to ensure compatibility with older modules. Regards,
Sylvain
