The issue we face when trying to map our cockpits is that with the encrypted
files we can not figure out what the buttons / controls are mapped to.
Especially with the addition of parameters on K events (like how the landing
lights and pulse lights need a 1/2/3 added to the K event)… Since the
introduction of the B Var/Events in SU5 we have struggled with sorting out how
to trigger the events. the Interior XML model files was the way to sort
through the mess and get to the heart of what the model controls were doing
under the hood… Since we don’t have access to the BVARs then we need to get
access to the files to read the Events / Vars and Emissive code… If you could
make these files available that would be of help.
This would be extremely helpful and GREATLY appreciated. I really hope this
request will be approved. Thank you for your thoughtful consideration!
If releasing Non-encoded files is a NO-GO for DRM reasons, then please
consider including in the Planes Technical Documentation, the needed
information ? But lets face it, as far as DRM & Encryption are concerned in
MSFS, the stable doors were left insecurely locked, and most of the horses
have already got out of their stables. Catching them all, and putting them
back in re-designed, more secure stables, in probably now not a cost
effective exercise.
Your best bet currently is to use the Behaviors debug. It will provide you
with the starting parameters that ASOBO templates use in most cases. It’s a
bit of work but can be done. I have used it on the Cessna 172 classic. Also
use the Fly by Wire blender gltf importer (msfs2blender2msfs )- you get node
names and animation names there.