it seems that RPN scripts are not properly evaluated in script triggers in v4. they worked great in v3.
some scripts cause validation errors, others simply don't evaluate correctly.
one example is an RPN script that begins (A:INDICATED AIRSPEED, knots) will cause an immediate object error of "missing parenthese". simple constants seem to work <script>0</script> works but with variables or comparisons like <, >, >=, etc. fail. in v3 I used < and > for the comparisons since it's embedded in XML, worked fine. will this be supported in v4 or do we need to re-write our scenarios?
thanks
[RESOLVED] RPN scripts within script triggers fail in v4?
- Rob McCarthy
- Lockheed Martin
- Posts: 3703
- Joined: Wed Aug 24, 2011 1:37 pm
Re: RPN scripts within script triggers fail in v4?
Thanks for letting us know. We'll investigate the issue.
Regards,
Rob McCarthy
Regards,
Rob McCarthy
Rob McCarthy
Prepar3D® Core Lead
Prepar3D® Core Lead
-
- Lockheed Martin
- Posts: 1207
- Joined: Tue Sep 25, 2012 2:34 pm
Re: RPN scripts within script triggers fail in v4?
Hello,
Thanks for the report! The issue will be fixed in the next release.
Thanks for the report! The issue will be fixed in the next release.
Clifton Crane
Prepar3D® Software Engineer Sr.
Prepar3D® Software Engineer Sr.
Re: RPN scripts within script triggers fail in v4?
Thanks! I think we confirmed it's working now in 4.1.