pellelil Posted November 2, 2020 Report Posted November 2, 2020 Hi Pete I don't know if it is the data (scanned scenery) or MkRwy, but as far I can tell it detects all runways as "Concrete". E.g. EKKA (vanilla scenery) both have Concrete and Grass runways, but MkRwy5 scanning MSFS scenery detects them all as Concrete. EDIT: Forgot to mention I am reading the content of Runways.xml
Pete Dowson Posted November 2, 2020 Report Posted November 2, 2020 On 11/2/2020 at 1:34 PM, pellelil said: I don't know if it is the data (scanned scenery) or MkRwy, but as far I can tell it detects all runways as "Concrete". E.g. EKKA (vanilla scenery) both have Concrete and Grass runways, but MkRwy5 scanning MSFS scenery detects them all as Concrete. Hmmm. I think the actual surface is given in the BGL as a GUID referencing a texture file somewhere. I didn't think I got a surface type at present. Maybe concrete is default. The XML decode for the surface type is a GUID string like "{0e12195b-4a50-42d1-b8c8-177b270f3aab}" Checking the information I've received from others, the byte for surface type is labelled "for FSX legacy enum". I'll ask what that relly means, exactly. Checking further, the enum value for "concrete" is 0. So the field is simply not populated. I'll let you know. Pete
Pete Dowson Posted November 3, 2020 Report Posted November 3, 2020 Hi Pelle I found out how to convert the runway surface GUIDs into the normal type names. So i'll make an update to MakeRwys with that included. Pete
Pete Dowson Posted November 3, 2020 Report Posted November 3, 2020 Hi Pelle, Okay. Decoded runway surfaces now correct in MakeRwys 5.01, now released. Pete
pellelil Posted November 4, 2020 Author Report Posted November 4, 2020 Thanks Pete that is great. Pelle
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now