• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

P3D v4 Script error in P3Dv4

I don't agree or disagree, as it's your code and thus your preference... I asked as I didn't see a benefit to your approach and found it somewhat obfuscating.
 
I find that in both cases the condition IS executed... tested in FSX and P3D v4 using the script

You're right, I tested and surprisingly (to me) the if{ } is executed. I recall having done this test many times, but looong ago (FS9 perhaps), and I can assure you it wouldn't work then.
Which was very odd as logical "true"is a non zero number, but wasn't working that way.

Thanks for pointing out.

Tom
 
Thanks for all the reactions.
I dont use P3Dv4 myself, so I will ask the guy who reported this to me to post detail on the error log.

Rob

sorry for the wait to post this...



[error.0]
error=Gauge/Script Error
Type: Gauge
Name: VSTOLControlIPC_Function
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): ")" in: )
}
(L:VSTOLMode,enum) 4 == if{ 1 } els{ 0 } (>L:ChuteVisible,bool)




???
 
Four things that strike me here

1) this isn't the line that you quoted in your OP
2) Running a quick test here on V4.5 again yields NO error in the log. The value assignment works as intended.
3) Your user's error message seems to flag something like "}", or is it ") }", at the beginning. Better take a close look at the surrounding logic structure. Like WarpD I believe we need more context (said that in my first reply).
4) Is the function name really "VSTOLControlIPC " - Two l's?
 
Last edited by a moderator:
OK, I found the reason for the script error; it's not in that code line itself, but in the preceeding code ….

Code:
(L:VSTOLMode,enum) 2 == (L:VSTOLModePrev,enum) 3 == &&
(L:VSTOLMode,enum) 0 == (L:VSTOLModePrev,enum) 4 == && ||
if{
   0 (>K:AILERON_TRIM_SET)
   0 @SetVTOLConfig)
}

(L:VSTOLMode,enum) 4 == if{ 1 } els{ 0 } (>L:ChuteVisible,bool)
It's the ")" character in "0 @SetVTOLConfig)" ....

Rob
 
The log entry referenced it accurately:
Code:
                   )
}

(L:VSTOLMode,enum) 4 == if{ 1 } els{ 0 } (>L:ChuteVisible,bool)
I will mention to L-M that perhaps a CRLF after the colon might help us to track down the location(s) easier.
 
Back
Top