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

Possible SDE bug in approach legs

M

MillKa

Messages
16
Country
germany
Hi ScruffyDuck,

i just fixed a bug in my own decompiling code and it looks like you have the same bug in SDE.

According to Orthmanns doc, a leg subrecord has a DWord at offset 0x10 named "recommendedRegion". I used to convert the lower 16 bits to a region ident and skipped the upper 16 bits. That gave the same values SDE shows.

However, sometimes the upper 16 bits are not zero. Converting the two 16 bit halfs into two idents gives bogus strings. If the DWord is split into the lower 11 and upper 21 bit (like elsewhere for region and airport), the resulting ident strings look correct.

P.S. i'm on vacation from May 6th to 17th
 
Hi Millka

Thanks I will take a look at that.
 
OK Thanks - I was assuming 16 bits for the recommended region ID and have changed that now so that I am reading bits 0->10 for that attribute.

Update will be in the next release of the engine.

Thanks again for spotting it and letting us know :)
 
Oops - don't know how I missed that one - have replied to it now
 
You must log in or register to reply here.
Back
Top