Can someone remove this road with the lightpole? Or patch it out? Its kind of immersion breaking
- Here you can see it
- 20221222194516_1.jpg (1.2 MiB) Viewed 1948 times
(Solved) Mesh error or lazy work?
- WayTooManyDamnSquids
- Posts: 8
(Solved) Mesh error or lazy work?
RWY 18R (Polderbaan)
Can someone remove this road with the lightpole? Or patch it out? Its kind of immersion breaking
Can someone remove this road with the lightpole? Or patch it out? Its kind of immersion breaking
Last edited by WayTooManyDamnSquids on Sun Dec 25, 2022 1:41 pm, edited 1 time in total.
- emilios[flytampa]
- Site Admin
- Posts: 1626
Re: (X-Plane 11) Mesh error or lazy work?
Can you check your scenery_packs.ini and describe the entries please?
something must be off place
something must be off place
Re: (X-Plane 11) Mesh error or lazy work?
X Plane 11, EHAM V1.1, 18R:
This is how it looks for me, road but no light pole.
This is how it looks for me, road but no light pole.
- 767-400ER_xp11 - 2022-12-23 12.08.15.jpeg (38.89 KiB) Viewed 1920 times
- WayTooManyDamnSquids
- Posts: 8
Re: (X-Plane 11) Mesh error or lazy work?
I cannot find anything to be honest, removing the most likely culprit like X-Europe did nothing. I also got no other sceneries for EHAM installed. The four entries for FlyTampa EHAM are at the very top going from 0-3emilios[flytampa] wrote: ↑Thu Dec 22, 2022 4:45 pm Can you check your scenery_packs.ini and describe the entries please?
something must be off place
- WayTooManyDamnSquids
- Posts: 8
Re: (X-Plane 11) Mesh error or lazy work?
Alright, I got it working by editing FlyTampa_Amsterdam_3_mesh UNDER the X-Europe entries in the .ini
Is it supposed to go there? Or right below FlyTampa_Amsterdam_1_overlays?
Is it supposed to go there? Or right below FlyTampa_Amsterdam_1_overlays?
Re: (X-Plane 11) Mesh error or lazy work?
That's were it also resides in my scenery_packs.ini.
Question: Do you still also have the small road and only the light pole is gone?
XP adds new sceneries always at the top. If you delete scenery_packs.ini, XP recreates it with an alphabetical order according to the directory names in directory Custom Scenery.
Sometimes this leads to disturbances, because the order of of the different layers of sceneries is crucial.
What I do is to generally modify the directory names of the sceneries to ensure the correct order in scenery_packs.ini. I always delete scenery_packs.ini when adding a new scenery so enforce creation of a new version.
My naming logic is as follows:
Sceneries start with "a_"
Simheaven with "y_"
Mesh start with "zzz_"
Terrain with "zzzz_"
The only directories which can not be renamed are libraries, because otherwise the sceneries wouldn't find them.
Question: Do you still also have the small road and only the light pole is gone?
XP adds new sceneries always at the top. If you delete scenery_packs.ini, XP recreates it with an alphabetical order according to the directory names in directory Custom Scenery.
Sometimes this leads to disturbances, because the order of of the different layers of sceneries is crucial.
What I do is to generally modify the directory names of the sceneries to ensure the correct order in scenery_packs.ini. I always delete scenery_packs.ini when adding a new scenery so enforce creation of a new version.
My naming logic is as follows:
Sceneries start with "a_"
Simheaven with "y_"
Mesh start with "zzz_"
Terrain with "zzzz_"
The only directories which can not be renamed are libraries, because otherwise the sceneries wouldn't find them.
- Tim/Rodeo314
- Posts: 7
Re: (Solved) Mesh error or lazy work?
Libraries can be renamed.
If you rename a library folder and another scenery stops working, that’s because the other scenery is broken and references objects by path directly instead of using the X-Plane library system (whose purpose is precisely to allow developers to reference objects in other packages without having to hardcode the path to the object).
If you rename a library folder and another scenery stops working, that’s because the other scenery is broken and references objects by path directly instead of using the X-Plane library system (whose purpose is precisely to allow developers to reference objects in other packages without having to hardcode the path to the object).
Re: (Solved) Mesh error or lazy work?
To avoid this kind of hazzle they shouldn't be renamed. There is also no reason to do so.