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

SCASM lights KILL my fps

EdGeneer

EdGeneer

Messages
470
Country
unitedstates
thebeloved said:
My findings (but i hope someone can do other tests):

Runway heading must be declared in the range 0 to 179

AND

No integer values allowed!!!
Click to expand...

Your a genius!!!!

Awesome!!!

this thread was pointed out to me by Kumara, I was searching for this and didnt find it on initial search, and didnt think to go to this section of the forum.

Thanks for finding that!!!
 
thebeloved

thebeloved

Messages
22
Country
italy
Hi guys!

I'm happy that you find useful the solution! I have used the same technique on Milano Linate X, and it works fine :)
 
Kumara

Kumara

Messages
119
Country
italy
Gianni, you've found a Golden Rule here!
I've fixed already about ten airports using your technique, and indeed it works faultlessly!

The only trouble is to have to disassemble many BGLs to find the one that contains the runway heading information: this is not always the case as in some instances you will find the file named with the ICAO code (not the AFCAD), or the airport name, or a hint to Runways (usually RW), but I've found that sometime there is no logic in the file names.

Is there any other way to detect this crucial file?
 
thebeloved

thebeloved

Messages
22
Country
italy
Kumara said:
Gianni, you've found a Golden Rule here!
I've fixed already about ten airports using your technique, and indeed it works faultlessly!

The only trouble is to have to disassemble many BGLs to find the one that contains the runway heading information: this is not always the case as in some instances you will find the file named with the ICAO code (not the AFCAD), or the airport name, or a hint to Runways (usually RW), but I've found that sometime there is no logic in the file names.

Is there any other way to detect this crucial file?
Click to expand...

Unfortunately not....the only way is that sometimes the files are really small (less than 1kb) as they contains only the FS8 header and the 0xAA opcode with its sub-opcodes.

You have to try disassembling it with bglanalyze, that is the technique that i've used till now...
 
Kumara

Kumara

Messages
119
Country
italy
Great!
In between I also made clear to myself about the disappearance of the AI aircraft in some places... or their resurrection! We should really BAN SCASM from the FS world...

BTW maybe you should add an actual script example in the FSXA/P3D section, since it may lead to confusion when you declare
Heading 58.01 (we have +2° degrees of magnetic declination)
Click to expand...

As for now I fixed quite a few airport using your discovery, but I only added a +0.1° or +0.2° whenever there was an integer value declared below the 179° and it seems to work without the trouble it may create on the terminal way points to have the rw shifted with one or two degrees...

As you yourself have already made clear, it's plain and simple:

# Heading values should be declared between 0 and 179

# No integer Heading values are allowed: a +0.1° or +0.2° should be added

Am I correct?
 
thebeloved

thebeloved

Messages
22
Country
italy
Kumara said:
Great!
In between I also made clear to myself about the disappearance of the AI aircraft in some places... or their resurrection! We should really BAN SCASM from the FS world...

BTW maybe you should add an actual script example in the FSXA/P3D section, since it may lead to confusion when you declare


As for now I fixed quite a few airport using your discovery, but I only added a +0.1° or +0.2° whenever there was an integer value declared below the 179° and it seems to work without the trouble it may create on the terminal way points to have the rw shifted with one or two degrees...

As you yourself have already made clear, it's plain and simple:

# Heading values should be declared between 0 and 179

# No integer Heading values are allowed: a +0.1° or +0.2° should be added

Am I correct?
Click to expand...

Yes is correct,

if we want to be academic we can tell:

# Heading values should be declared between 0.00 and 179.99

# No integer Heading values are allowed: a +0.1° or +0.2° should be added
 
Kumara

Kumara

Messages
119
Country
italy
thebeloved said:
Yes is correct,

if we want to be academic we can tell:

# Heading values should be declared between 0.00 and 179.99

# No integer Heading values are allowed: a +0.1° or +0.2° should be added
Click to expand...

then

# Heading values should be declared between 0.01 ;)

Cheers!
 
You must log in or register to reply here.
Top