Marklin schreef: ↑23 apr 2025, 12:01
[..}
Ps. over het laatste gesproken, kwam er wel achter dat lang niet alle verwijzingen in dat bestand nodig zijn voor een goede werking en bijv. een scenery object niet zichtbaar zou zijn.
Als voorbeeld van oa. GM die men maar 1 keer gebruikt zoals een spoorwoning, maar omdat het hiermee uit de selectie lijst verdwijnt maakt dat dan niet uit en blijft dus zichtbaar in game.
Hello marklin!
Please - don't draw the wrong conclusions. Each asset pack you're using something from
must be preloaded and "checked" in the editor. Even if it seems to be ok, it can lead to errors like strange shadows appearing, polygons connecting to the horizon, instability and increased loading times.
It can also lead to objects suddenly disappearing when working on the route, you can get milk bottles, the flyout still showing the assets name, you have it but still there's a milk bottle. Opening the tiles or tracks.xml then shows the asset is defined but <Provider> and <Product> field are empty, in which case the resource cannot be loaded. I have found a lot of those "ghost" milk bottles on a number of dutch routes.
So even if you're only using one asset from a pack, TS needs to load its blueprints.pak into memory which it only does when the Provider/Product is active. Save yourself from future troubles and correctly check the asset box. I have repaired some czech RouteProperties.xmls, the effect was reduced loading times and strange crashes when switching from playing to editor back and forth were not happening any more.
Another thing:
packing files into an .ap
This needs a check, as files must not contain umlauts or special characters, and the default is zero compression to not slow down loading for unpacking.
I have ran the Frison\Materiaal assets through my powershell script which reports files that won't load if packed in an .ap file - be aware of that!
These assets will fail to load from an .ap archive, because they have a
comma in their filename which is interpreted as a separator by zlib.dll, which handles .ap I/O.
Also be aware that scripts using #include, calling other scripts, won't work from an .ap. See how DTG shipped the KarlsruheStrasbourgSignals as loose files?
Thanks for your work, THVN was my first dutch route and has a place in my heart. Looking forward to V3
Greetings,
Piet
