Version: 1.8.9.0
Frequency: Consistently
Severity: High
(Low - quality of life, workflow optimization, rare enough to not impact production, etc…
High - critical but workarounds are available, important feature not working as expected, frequent enough to impact production
Blocker - prevents from working on the project, prevents from releasing the product)
Marketplace package name: indiafoxtecho-tornado
Context: packae is monunted in the Community folder
Bug description:
When the Tornado is flying at high speed, pulling the stick causes the reverse thrust plates to deploy.
Happens only on SU6.
Repro steps:
Take off with the Tornado, accelerate to 300 kts and pull the stick: the thrust reverse plates deploy.
This is the animation code:
As you can see this depends on the L:ReverseAnimation, number (although it would also require SIM ON GROUND), but as far as I can tell the L:ReverseAnimation variable is zero during flight (does not change value), making me think it may be an issue in parsing the XML for the animations.
This happens consistently in SU6, but seems OK in SU5. We also assume some user would have noticed this.
Double checked the code for “L:ReverserAnimation” variable it is unlikely to be the cause of the issue. Also we have monitored the variable during a flight and it is always zero unless the plane is on the ground and reversers are engaged, so it seems OK.
Also, retested in SU5 and the animation works fine - so it seems a SU6 problem.
Additional comments:
-
Bug is still present on 1.8.10.0
-
The model actually uses only the third animation (“reverse”). “r_reverse” and “l_reverse” were planned as separate animations but never used.
-
It seems a parser issue (probably due to the extra spaces or new line?).
We have changed the code as indicated below (no extra spaces, no new line) and it now works fine.
…but it should still be addressed as probably affects other products/animations.
Hello @Scimmia1974
We have identified the issue.
The RPN stack is no longer cleared in the case of PartInfo animations, so when the code does not return a value, it would return the result of the previously evaluated animation code instead.
This also explains why explicitly returning 0 in your els scope fixes the issue.
A fix is being worked on but it will likely come with SU7.
Thank you for reporting the issue.
Regards,
Sylvain
1 Like
