Problem with scenery order - part II in SIMstarter NG Posted March 11, 2019 There have to be some other bugs with the layering too. Not only related to autodiscovery. P3D (nor simstarter) simply did wrong things in the above mentioned state. There was no way anymore to have WSSS (for example), the one with 4 layers, in a working order. It ordered it always in a way that broke not only WSSS (overlapping with standard scenery, despite it being ontop) itself but caused also other problems. I think you see that i tried very very hard to use Simstarter to fix it but it simply did not work because also SS read the order wrong AND placed the order wrong into the sim. No way to fix it with the functions i know in SS. Ordering manually did not help. And you can also see (also in the post from the other guy) that SS even oders it different from P3D itself. I posted 3 pics of that. And doesnt matter how hard i tried to order the layers in SS, on reload of P3d they were simply in another place again. Impossible to order. Im not sure wich part of lorby did the trick, maybe the deletion of scenery indexes. Maybe other things but that was the only way to fix it. Btw, im not ranting here about SS, i like the tool but im pretty sure there is some thing overseen that causes this problem. Like i also mentioned, SS seems to place addons coming from the addons cfg in another place as P3D itself. You seem to place it before the other addon entries and P3D behind. One question i have now: Is it possible to use simstarter only to start P3D, without it touching my scenery order? I want to use the core set functions to free core 1 but im really scared atm to use it to order scenery. This cost me so much time already and i dont want to end up with a broken sim again.