Hi Peter - I'm assuming that you're referring to drawdistance and the way that this makes assets invisible at reduced levels of details? Apologies if not. Assuming that you are then: At the Asset level each Asset .bin has a section like this: Code: <DetailLevelGenerationRange> <cSceneryRenderBlueprint-sDetailLevelGenerationRange> <HighestLevel_1isHighest d:type="sInt32">1</HighestLevel_1isHighest> <LowestLevel_10isLowest d:type="sInt32">10</LowestLevel_10isLowest> </cSceneryRenderBlueprint-sDetailLevelGenerationRange> </DetailLevelGenerationRange> SO you can force all instances of that asset to have a minimum drawdistance by increasing the HighestLevel_1isHighest setting upwards from '1' (as shown here). NB this only affects newly added instances - not anything already in place. If you want to see/alter the setting for a previously-drawn instance then: each scenery item is defined on the relevant scenery tile - the first section for each starts like this: Code: <cDynamicEntity d:id="1299599664"> <Component> <cSceneryRender d:id="1058053584"> <DetailLevel d:type="sInt32">4</DetailLevel> <Global d:type="bool">0</Global> </cSceneryRender> Where 'DetailLevel' defines the drawdistance. Cheers Neil
Thanks Neil, The problem I'm having is a signal does not appear in the game even though the HUD shows it is there. I have been underground to see if it got sunk but there is nothing, I asked a friend who has the route and he can see the signal ok. So I might be barking up the wrong tree with the LOD
So, in theory that rules out the drawdistance issue. Also, if it is a signal they are usually defined as 10/10 in the model so they should always appear. Is this the only example of that type of signal - i.e. can you see other instances in game ok?
The signals are Wartezeichen that have a letter W and two lights illuminate to allow you to pass them. https://de.wikipedia.org/wiki/Wartezeichen I checked the same signals on a different route and they all appear so I went tin to TS Tools and the tracks bin I manually edited the defective signals to use the other version by changing of the Product. There were only 9 signals to change and it works. Still don't know why the signals from the same provider work in one route and not another. Either way I have the signals back on the route Thanks for the suggestions Neil.
Good to hear that got it sorted - presumably there is a slight pack difference between the two routes and you were unlucky to get the duff one!