Version: 1.4.7.0
Frequency: Consistently
Severity: High
Context: Any package - When editing and mounted from Community
After loading a project in DevMode, the “Order Hint Selection” window forces us to choose a “Package Order Hint”. In DevMode, the package remains correct, e.g. all exclusions work and polygons are also displayed correctly, but when the simulator is restarted in free view mode, the scene is completely buggy, e.g. no exclusions work and many polygons are no longer displayed. The solution is to delete the line CUSTOM_WORLD_SCENERY added previously in the DevMode in the .xml file of the “Package Definition” and drag-and-drop it onto “fspackagetool”.
Hello @FuturKiwi1965
By “restarted in free view mode”, you mean restarted with your package in the Community folder and starting a free flight?
Did you select the CUSTOM_WORLD_SCENERY hint manually?
What kind of scenery is it?
Regards,
Sylvain
Yes, sorry, that’s what I meant, it’s a free flight reload.
In fact, when loading my project(s) into Project Editor, which have not been reloaded since the release of 1.4.7 and now 1.4.9, the Order Hint Selection window systematically appears to allow me to continue, forcing me to choose a custom or other definition, which I do and which is then written, as you know, in the .xml file of the definition package. After compilation on some scenery I have the building exclusions that don’t work, as well as the apron and taxiway exclusions. The solution is to delete the line XXXX recompile, reload and everything works. I should point out that this concerns two airports, one of which is very large (LFJR), another where three hangars are not displayed and aprons, taxiways are not excluded (LFOT) and a custom scenery (Château de Chenonceau). On the other hand, I have another airport where this has no impact whatsoever, but it’s located in the southern hemisphere: FMEE. For LFJR in Debug Scenery Packages mode, the parasitic buildings are a priori from “microsoft-scenery-gliders-worldwide-part1”.
The first three screenshots are with the <PackageOrderHint line and the next three without the line.
Hello @FuturKiwi1965
This should no longer be a problem in the current SU2 beta build.
Regards,
Sylvain
1 Like
Hello
Indeed it’s perfect 
Thank you
