• 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.

the EQU operator...

12bPilot

12bPilot

Messages
611
Country
switzerland
Hi,

I'm building a SafeDock System right now and ran into a problem yesterday.
As in Arno's Docking System, I used a STOPDISTANCE constant.
I set "STOPDISTANCE EQU 20".
Now, some lines later in the code, after the particular Aircraft Recognition checks, I want to change the value of the Stopdistance, example:
Code: 
IFIN1 b777, usrvr4, ....
   STOPDISTANCE EQU 30
   ....
The compiler doesn't take it and returns "redefine of symbol blablabla". Hmm, constant must have to stay constant ;)

So, is there a way to assign a new value to a variable? Or should I make it with local variables? Any hints?

Jeff
 
Hi Jeff,

I have never tried to use the variable like that, I only used it because it gave me an easy way to change a value all over the file without having to edit a lot of lines.

One thing you should remember is that this variable only exists at compile time, so in the generated BGL/MDL code there is no variable, only the value.

So if you want to change the value a lot, why not just type the number you want?
 
Thanks for the reply Arno.

So we can't change values "dynamically" at runtime? Because the Stopdistance for a 737 is nearer towards the terminal than for let's say an A340. I'm speaking of distance in respect to the aircraft's reference point (as this is used for the separation plane, or am I wrong?). That's why I need individual Stopdistances.
I hope you can understand my thoughts :)

Jeff
 
Hi Jeff,

We can have dynamic stop distances, but not with BGLC variables, as these only exist at compile time.

For my docking systems I am using one stoppoint at the moment, but it would indeed be nice if that could be made depending on the aircraft type. I guess to do that, you will have to make a new SEPERATION_PLANE command for each type, as the distance is given in that command. So that would make the source code a bit more complex :).
 
Oh no, that's what I've tried to avoid ;)
Maybe I'll make 2 stop-points, for small and big planes, that's reasonable enough I think...

Thanks anyways, and when I'm finished with my Docking system, maybe it's good enough to add to your VDGS-Tweaker!

some screens:
SafeDock_IdFail.gif

SafeDock_Active.gif

SafeDock_Distance.gif

SafeDock_TurnRight.gif

SafeDock_Stop.gif

SafeDock_Ok.gif

SafeDock_TooFar.gif


-Jeff
 
You must log in or register to reply here.
Back
Top