Textures: The "Layers-over-Layers-Myth"

[OzBoz]

So let me see if I understand this if I cover a texture with another texture there is nothing under it

I believe you also need to remove the bottom texture(s) from the config file, and then save twice. I'm waiting for confirmation from jost62/geophil.

Cheers

Brian

 

[geophil]

I believe you also need to remove the bottom texture(s) from the config file, and then save twice. I'm waiting for confirmation from jost62/geophil.

config.txt will be updated by Surveyor automatically. The KUID list in config.txt seems to be for info only. Surveyor definitely does not rely on it. It finds the KUID information it needs in the .gnd, .obs and .trk file (with .obs and .trk being irrelevant for ground textures.)

geophil

 

[jost62]

It is quite simple:
1. You have textured a part of your board with texture A.
2. You don't like it any longer, so you cover it with Texture B.
3. Thats it. Trainz will delete the unused kuid's of the covered texture(s) in the map.

You have to do nothing else, nothing in the config and nothing in the gnd-file, no removing - forget all that internal manipulation. Trainz is intelligent enough to do that for you.
Indeed: When you covered a texture with another texture there is nothing under it!
(- ok, from the description above you know that textures only are deleted in the stored map data, when
1. covering a texture totally and
2. after saving it a second time).

 

[Dinorius_Redundicus]

John

If it's so intelligent, why does it take 2 saves to remove a (covered) texture? From your experiments, can we say what its status is after just one save?

- The texture is actually gone but TO is unable to reflect that until the map is saved a second time?

- The texture is still there as reported by TO and to really remove it needs another save?

TO can presumably read the .GND file (this is how it is able to replace objects and textures in a map) so I'm inclined to think the second option is correct, ie. the texture is still a dependency until the second save is done. If that's true, then the programming of Trainz is more cock-eyed than I thought.

 

[leader2302]

It is quite simple:
1. You have textured a part of your board with texture A.
2. You don't like it any longer, so you cover it with Texture B.
3. Thats it. Trainz will delete the unused kuid's of the covered texture(s) in the map.

John,

I have a 400 baseboard route with HOG lines all over that I no longer need. To completely remove the HOG textures from the map do I have to cover all the HOG textures on every baseboard in the entire route?

I would like to remove all the HOG lines in the route without having to cover them with another texture. Is that possible?

 

[rweber95]

Wouldn't the easiest way to get rid of the hog textures is to remove them using CMP then open your route in surveyor and select delete missing assets and save as a new route.

Bob

 

[leader2302]

I forgot to add I am using TRS04.

 

[OzBoz]

John,

I have a 400 baseboard route with HOG lines all over that I no longer need. To completely remove the HOG textures from the map do I have to cover all the HOG textures on every baseboard in the entire route?

I would like to remove all the HOG lines in the route without having to cover them with another texture. Is that possible?

The easiest way to achieve that in 2004 is to use the utility Erazor available at http://http://www.uelasticus.de/erazor/erazor.zip
This removes all textures where it's used, and just leaves blank grid base boards. It only removes textures, and nothing else.

Cheers

Brian

 

[Dermmy]

Easier way - in 04 the HOG textures should be in a folder called C:\programfiles\auran\trs04\world\custom\ground

Navigate to the 'custom' folder using 'My Computer', move the 'ground' folder to the desktop, fire up TRS04, load the route, delete missing content and no more HOG textures in the config or anywhere else. Move the 'Ground' folder back where it should be and life goes on as normal....

Andy