Version: All versions
Context: Mounted in community folder, devmode or marketplace
When we put custom code in RPN that is incredible important and necessary to override certain base sim vars due to MSFS limitations or due to the requirement to implement custom solutions such as, custom ITT, NG, and other simulations behaviours. The code stops to work as soon as the camera drone is active and moves away from the airplane.
I understand this is for performance purposes, and makes sense for multiplayer objects. But for the user airplane is just causes incredible bad bugs and behaviours, even sounds can go wrong.
Below is an example, when the FSR500 is on full reverse due to TurboProp limitations we have currently in the MSFS Turbos simulations the engine spins out of control even beyond to what we have set in .cfg files (I reported this issues 6+ months ago), to overcome the limitation I wrote custom simulations that overrides, fuel flow, NG, Prop RPMs, etc. to keep it as per the real aircraft behaviours.
Now when the user switches to drone camera and moves away from it, some code that I placed in .XML to save performance from WASM → SimConnect due to how heavy I have to overwrite MSFS SimVars fails to work… making the PROP RPM:1 spins 4433,7753 even when the governor should keep it at a max of 2000 RPMs, however during reverse FSR500 can only get to a max of 1800RPMs and my custom code takes care of that, but with drone camera away from the airplane this is the result:
This breaks the sounds since now the RPMs are too high:
Ideally we need a tag on the GT_UPDATE code that says execute this always, and it gets executed despite of the distance at least for the user aircraft.
Load FSR500, put the engine in full reverse, move the drone camera like in the video above
Thanks to the team for investigating this, and let me know if there is anything I can implement to mitigate the behaviour or implement in the future to avoid the issue. I have advised customers in the meantime to avoid drone cameras with engine on full reverse, lucky enough I have the rest of my custom simulation inside WASM so normal engine operations are not affected, however MANY OTHER products out there are suffering from this problem and they don’t use WASM to be able to prevent the issue.
All the best,