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

P3Dv6 stock scenery objects GUID

hervesors

hervesors

Messages
92
Country
france
Hi all,

Following a preliminary analysis, it seems many stock scenery objects GUID have changed in P3Dv6 as compared to previous P3D versions and FSX. It is notably the case for ILS associated objects and probably some others.
I couldn't find any precise information in the P3DV6 SDK regarding that. Are you aware of some published information that lists stock objects GUID in P3Dv6?
I also identified some BGL record structure changes that I could partly decode, in particular
- Runway approach lights
- Airport taxiway sign records
to name a few
Thanks for the information you could provide. I will be glad to share the information I already have by email if you wish

Regards

Hervé
 
Hi,

I don't think any SDK lists the GUIDs of the stock objects. All you can probably find are some community generated lists for older releases.
 
hervesors said:
Hi all,

Following a preliminary analysis, it seems many stock scenery objects GUID have changed in P3Dv6 as compared to previous P3D versions and FSX. It is notably the case for ILS associated objects and probably some others.
I couldn't find any precise information in the P3DV6 SDK regarding that. Are you aware of some published information that lists stock objects GUID in P3Dv6?
I also identified some BGL record structure changes that I could partly decode, in particular
- Runway approach lights
- Airport taxiway sign records
to name a few
Thanks for the information you could provide. I will be glad to share the information I already have by email if you wish

Regards

Hervé
Click to expand...
Hervé, may I ask where you found BGL records for Airport taxiway signs? I have been searching for same for several airports with no luck. Any pointers are GREATLY appreciated.
Click to expand...
Thank you in advance.
 
Hi Lemon,

Airport taxiway signs are still stored in the SCENERYOBJECT section of the BGL file (Id 0x25). However, inside it, taxiway sign records have a different Id (0x14) instead of 0x13 for P3DV5 version
Structure is also a bit different, as follows (identified changes are in bold caracters)
Fixed header length is 32 bytes greater than P3DV5 header that is 0x50 instead of 0x30
Offset Number of Bytes Format Description
0x00 2 WORD Id (0x14)
0x02 2 WORD Size
0x04 4 DWORD Longitude
0x08 4 DWORD Latitude
0x0C 4 DWORD Altitude (0, cannot be coded with the compiler)
0x10 2 WORD (Flags, not checked but appear to be similar to P3DV5, except may be bit 0 that is IsAboveAGL?)
0x12 2 WORD Pitch
0x14 2 WORD Bank
0x16 2 WORD Heading
0x18 2 WORD Image Complexity
0x1A 2 WORD Unknown
0x1C 16 - Instance Id
0x2C 4 DWORD Number of signs
0x30 32 Unknow (all are 0xFF)

and then for each sign, structure is the same as for P3Dv5
0x00 4 FLOAT Longitude offset
0x04 4 FLOAT Latitude offset
0x08 4 FLOAT Altitude
0x0C 2 WORD Pitch
0x0E 2 WORD Bank
0x10 2 WORD Heading
0x12 2 WORD Flags
0x14 1 BYTE Sign size
0x15 1 BYTE Justification
0x16 - STRINGZ Label (zero filled)

Hervé
 
Hervé
WOW!...sorry, but I am impressed....I have dealt with FS and P3D for years, lots of work with ADE but never at this level and I THANK YOU. I got here, my question to you, as I moved a custom airport from P3Dv5.3 to P3Dv6 and then recompiled it with the P3Dv6 compiler. With ADE, I then Imported the "stock" taxiway signs, but after doing such and listing them with ADE, there were none, yet they certainly appeared in the runtime of P3Dv6, after adding the new BGL to the scenery library for that particular airport. If I were to "decompile" the BGL using Bgl2Xml, should I be able to see the detail you provided within the SCENERYOBJECT section?
I am guessing that the probable reason the stock signs do not appear in the "list" of taxi signs in ADE is due to the above mentioned differences (taxiway sign records have a different Id (0x14) instead of 0x13 for P3DV5 version)?
Thanks again, sorry for the ?'s.
Best regards
 
Hi Lemon,

I don't think Jon adds P3DV6 compatibility in its latest Bgl2Xml version. Indeed, running it on P3DV6 APX files does not extract existing taxiway sign records
Considering Jon retired, I don't think he will continue updating ADE and/or Bgl2Xml
Current P3DV5 compatible ADE version successfully opens and decompiles P3DV6 bgl files but I don't think taxiway sign list that is displayed is that coded in the BGL file but rather "stock" P3DV5 data
Now, it may well be that things did not change a lot and that P3DV5 taxiway sign lists can be used without modification for some (many?) P3DV6 airports. To be tested

Best regards

Hervé
 
hervesors said:
Hi Lemon,

I don't think Jon adds P3DV6 compatibility in its latest Bgl2Xml version. Indeed, running it on P3DV6 APX files does not extract existing taxiway sign records
Considering Jon retired, I don't think he will continue updating ADE and/or Bgl2Xml
Current P3DV5 compatible ADE version successfully opens and decompiles P3DV6 bgl files but I don't think taxiway sign list that is displayed is that coded in the BGL file but rather "stock" P3DV5 data
Now, it may well be that things did not change a lot and that P3DV5 taxiway sign lists can be used without modification for some (many?) P3DV6 airports. To be tested

Best regards

Hervé
Click to expand...
Hervé, again, thank you for your insight, knowledge and reply. I have been aware of Jon retiring and I totally wish him good fortune,, he has been a God send to us with his expertise.
You are correct on all accounts, the P3Dv5 bgl files do in fact compile in P3Dv6 and the taxiway signs created in v5 move over to v6 without any problems (that I currently see). The issue that started me
down this discussion path was the fact that after moving a P3Dv5 developed airport to v6, the v6 "stock" taxiway signs are included in the final compiled bgl. I have tried to use an exclude (all) but the stock taxiway signs
still show thru on the v5 built and recompiled on v6 airport.
I tend to be a stickler for accuracy when I craft an airport and the v6 airports that I have looked at contain a number of errors as it relates to the "real thing", taxiway signs are just one of the more noticeable.
I feel sure all of us will hear more and learn more about the v6 implementation as time marches on.
Again, many thanks for your indepth reply, its GREATLY appreciated!
Best Regards
 
You must log in or register to reply here.
Back
Top