IT is a BAD BAD idea to modify the standard texturing.bin files because it will make any route non-standard that uses any of the textures in that terrain paint definition. This could cause trouble in the future if RailSim is updated with a new terrain paint file.
Any route distributed with that modified terrain paint would also mess up the users installation with a non-standard file. Other downloadable routes with different non-standard terrain paint definitions could completely break other routes. This is a BAD BAD method of changing the Terrain Paint.
The best way is to include a custom texturing.bin file in an 'Assets/{Developer}/{Route}' folder that would apply a custom terrain paint only to that route.
Here is another way: Create a 'Common' folder with the modified texturing.bin inside. To use it just reference that asset in the route blueprint instead of the standard US or EU texturing.bin file. This can be done by creating a new route blueprint or directly editing an existing route's 'TerrainBlueprint' in the Content\Routes.xml file.
So I created two texturing.bin files, each contains the complete set of combined US and EU textures. The order of the list for each is different, the Texturing_US.bin has the US textures listed first with the US 'rock' definition, the Texturing_EU.bin has the EU stuff listed first with the EU 'rock' definition. The texture display names are changed for easier use.
This is the contents of the file attached below.
\Rail Simulator\Assets\Kuju\Common
\Rail Simulator\Assets\Kuju\Common\Environment
\Rail Simulator\Assets\Kuju\Common\Environment\Terrain
02/28/2008 12:48 AM 14,844 Texturing_EU.bin
02/29/2008 02:17 AM 15,304 Texturing_US.bin
The file is a RS_Tools package, unzip to a temporary folder, doubleclick AssetSetup.exe to install. Remove the \Common\Environment\Terrain folder to uninstall. If this package is uninstalled, any route that used this terrain paint file will likely fail to draw terrain textures.
To use one of these with an existing route you must edit the Content/Routes.xml file to replace the reference in the 'TerrainBlueprint' for that route. If the route originally used the EU terrain paint the Texturing_EU.bin file should be used as a replacement. The Texturing_US.bin should be used if the existing route was based on the US content.
Because this is an Assets add-on, for a route to use this new terrain paint the add-on has to be enabled in the World Editor. Click the object set filter icon (the blue box in the second left pop-up window), select Kuju->Common and checkmark the box. This must also be done for an existing route before the textures will show up in the lists. This will add a PreLoad block to the route's definition in the routes.xml file, that is normally an irreversible route change so a backup of the Content/Routes.xml file is recommended. The PreLoad block entry for that route can be manually edited out later if the modified terrain paint files need to be removed. You must enable the Common folder for an existing route in the World Editor before changing the TerrainBlueprint as described below.
Below is the TerrainBlueprint entry an existing EU based route. To use the combined textures you need to replace two entries. Replace the Product entry 'railsimulator' with 'common', replace the BlueprintID entry 'Texturing.xml' with 'Texturing_EU.xml', same procedure for a US based route but use 'Texturing_US.xml' instead. Note the use of '.xml', pay no attention to the fact that the actual files have '.bin' extensions, the entry here must use the '.xml' extension.
<TerrainBlueprint>
<iBlueprintLibrary-cAbsoluteBlueprintID>
<BlueprintSetID>
<iBlueprintLibrary-cBlueprintSetID>
<Provider d:type="cDeltaString">kuju</Provider>
<Product d:type="cDeltaString">railsimulator</Product>
</iBlueprintLibrary-cBlueprintSetID>
</BlueprintSetID>
<BlueprintID d:type="cDeltaString">Environment\Terrain\Texturing.xml</BlueprintID>
</iBlueprintLibrary-cAbsoluteBlueprintID>
</TerrainBlueprint>
So after modifying you end up with:
<TerrainBlueprint>
<iBlueprintLibrary-cAbsoluteBlueprintID>
<BlueprintSetID>
<iBlueprintLibrary-cBlueprintSetID>
<Provider d:type="cDeltaString">kuju</Provider>
<Product d:type="cDeltaString">common</Product>
</iBlueprintLibrary-cBlueprintSetID>
</BlueprintSetID>
<BlueprintID d:type="cDeltaString">Environment\Terrain\Texturing_EU.xml</BlueprintID>
</iBlueprintLibrary-cAbsoluteBlueprintID>
</TerrainBlueprint>
Uninstalling the modified terrain paint files will break a route that used one of those files. Any missing texture in a route will not display properly. There is no easy way to remove a terrain paint texture once it has been applied, I suppose you could paint over it with a standard texture. As a last resort you can remove the actual tile entry in the MixMap folder, that would remove ALL the terrain paint for that tile (you would have to entirely repaint the tile).
If you need to remove the reference in an existing route, simply change the TerrainBlueprint entries (in the routes.xml file or in the route blueprint) back to one of the two standard files.
Notes:
1. Neither of the modified texturing files are optimized, they were created by copy and paste with no other (major) modifications. There are duplicate entries where a texture is the same in the EU and US versions, there may be duplicate textures but they do have different display names. The display names are arbitrary.
2. There are NO procedural flora used in any of the US textures - that's how they are in the standard files. Existing procedural flora could easily be added to some of the US textures but it might be a good thing to have a duplicate texture available without procedural flora.
3. The US textures have NO winter textures - that's how they are in the standard files. I am presently adding some winter textures to the US terrain set, I don't know how far I'll get with that or how successful I'll be.