I don't know that I can answer your question as I don't think I have a working installation of MSTS-the-game but I'll look into it. I did describe the issue as "Possible". For the world file replacement example I provided I've put textures into the routes own \snow directory -- that's where the Scalerail snow textures are as well and that works perfectly well so it may be there is not actually a problem. I've reported it out of the concern I expressed -- that track and roads are not necessarily in \global\shapes (and as I now know from your note below, not all \global\shapes are tracks or roads). The problem seems to be that KUJU chose not to use the ESD_Alternative_Texture() parameter when they should have done so. Anyway, it's always been my opinion the route developer should be the one who declares via data values all sorts of things, including what textures to use and so assumptions like you have here get in the way of achieving that. I think it would be better to distribute something akin to a perl script to add ESD_Alternative_Texture( 1 ) to those \global\shapes that lack the line over coding in assumptions that work only 1 way. Last comment: I had a conversation w/ Steven Masters (Tsection.dat Master emeritus) where I said the right design for the tsection file was to NOT specify a shape file but o provide a descriptive name linked with just the dimensional specifications the actual shape should have. With that RE would guide the user to selecting the dimensional spec (via the descriptive name) and then guide the user to select the shape to use from the routes shape directory. That way you could have many identically sized shapes bearing unique textures (e.g., one 100m tangent specification displaying choice of all combinations of rusty rails vs. well used rails, concrete ties vs wood ties, dark ballast here, light ballast there, etc. etc) and so the Tsection file would not be filled with so many entries bearing identical dimensions. His reply was "Wish we understood that 10 years ago, it would have made life much easier". IOW a standard way of "replacing" a global specification with a non-global displayed shape -- exactly what I'm doing w/o the help of RE. Dave Nelson -----Original Message----- From: