Atomic Systems

I have had more than a couple of enquiries about how to make route selection pictures for single player mode etc, I know there is some advice out there but I thought it would be worth putting it in one place.

1. The first thing you need to do is to create a PreLoad folder in your route. This should be located in Assets/DeveloperName/Route ie. Assets/keithmross/Port Road.

2. Open up RW2013 and navigate to an iconic location for your route. Use CTRL-S to snapshot the picture which is usually saved in your My Photographs directory as a .jpg file.

3. You will need a grphics editor such as Paint.Net ( Free ), GIMP ( Free ), Paintshop (not free)

For Good Quality and Usable Pictures do the following:

4. Open your editor and create a blank picture that is 256 x 128 pixels. If you mearly shrink the screenshot from TS2013 it will be a horrible looking, poorly defined and HUGE file.

5. Open your screenshot, copy and paste it into your blank image using whatever option enables you to keep the canvas you are pasting onto as 256x128 pixels. You should then be able to move the image round and shrink it within that 256x128 window.

For quick, simple but poor quality images with distortion

4. open you editor and copy in your screenshot. It is probably square whereas you need it letterbox shape. Use the crop tool to make at least a reasonable crop that looks about twice as wide as it is high. Now use the image resize function to get your image exactly to 256 x 178 pixels.

Making a dds is next

5. In most picture editors it is possible to make a .dds file. If you have this option then save your image into the Preload folder you made earlier as a .dds file slecting for dxt1 format with mipmaps. Some editors may need you to be more specific and select dxt1, ARGB, 6 mipmaps. The key thing is NO ALPHA TRANSPARENCY if the editor asks.

6. If you do not have a graphics editor that can make a dds then the next option is to download DXTBMP from http://www.mwgfx.co.uk It is free and safe - I have been using it for years. Save your picture as a .bmp file. Open up DXTBMP and using this convert your .bmp to a .dds

Turning your .dds into a route picture

7. OK now you are in a position to use RWTools. Read the RWT Help2 file first and make sure you have the latest version 4.0.16. Remeber that you need to point RWTools to your PreLoad folder first using the options menu. Bingo it will work.

8. If you do not want to or can't use RWTools then you can go the long way round. Goto assets/kuju/railsimulator/preload and copy LegacySBMetaData.bin and RouteSeeberg.TgPcDx into your folder.

9. Rename them MyrouteMetaData.bin and MyrouteThumb.TgPcDx

10. Use SERZ to turn the .bin into xml. Edit the lines ( which are obvious ) in the xml which have the name of your new thumnail in them AND the line that has the RouteGUID. The GUID is the huge letter string found in the Scenarios directory that is the directory name for your route.

11. Re-SERZ your xml file.

12. Get hold of a copy of the RSBIN tool - can't remember where from. Use the open SERZ option to point to your route loading thumbnail, this will decompile the .TgPcDx file. Now use the dds tool and select your dds picture. Save and bingo you are in business.

So its possible without RWTools but frankly ..... well go buy a copy !

Hope this helps

Thanks my friend - This does help a lot.

" Remeber that you need to point RWTools to your PreLoad folder first using the options menu."

To which PreLoad folder are you refering? Does one have to make your own PreLoad folder under your name in the ASSET folder eg Assets>George>PreLoad or does one have to point to PreLoad Folder of the Provider of the Route eg Kuju>Railsim>PreLoad
Thanks

The key thing about the PreLoad is that it "ought" to be in the third level down from Assets. But in some of the content it isn't and that works because they ( being KUJU and some DLC makers have done some more complex stuff ) but if you are adding ROUTE pics then put the Preload folder below

Asset\makersname\routename

ie at the same level as folders like Railnetwork or RailVehicles or Scenery etc

If you put in here then this means that you can ( if there is stock associated with the route ) also use it for the stock.

In effect ( conceptually ) a PreLoad directory pre-loads content in directories below it into a big database made up of all the contents of all the preloads - hence Preloads having files in them called metadata.

There are no absolutes in this, just best practise that will keep things simple. The key thing is that you understand what you are doing when you place a preload directory. The Kuju ones are placed far inside the structure but this is to achieve a particular effect relating to the way in which they plan to deliver these routes in the future. For routes we have downloaded most have a very simple directory tree.

What you must NOT do is try to create one single preload directory for your files - preloads are not user specific but either route or stock specific. A single preload directory really will ( and I speak from trying it ) hamper your ability to organise things.

Actully I realised I hadn't answered your question exactly.

You point Railworks at the Preload where you are going to have the route's metadata file which "ought" to be in the route's own preload folder.

I know that Mike RWTools has provided route metadatafiles based in a seperate single file - it works but ... in my opinion after having to unpick things as I got into a dreadful tangle ... this isn;t to be recommended. Look at the existing routes and stock. All have their own metadatfiles.

If you have a single metadata folder that gets the "bluecube ticks" for every route that means that all the metadata you create is being openned and stored ( in memory ??) everytime you open any route. By limiting preloads to specific routes and stock only the relevant preloads are preloaded for any session. I think

Thanks very much for this "HOW TO" explanation. It helps a lot. Boy these things tend to get so complicated.
To do Route pics is one thing but one would also like to add pics to the stock associated with the scenarios when choosing. a "HOW TO" to do this will also be much appreciated my friend.
Thanks again for your patience and help

Maxtedrw
Thanks from me also for the tutorial. I have been trying to create pics & description for my favourite reskins with "limited"success so to echo zigal's request, would also appreciate a stock tutorial.
Thanks

Sent using Tapatalk 2

maxtedrw wrote:Actully I realised I hadn't answered your question exactly.

You point Railworks at the Preload where you are going to have the route's metadata file which "ought" to be in the route's own preload folder.

I know that Mike RWTools has provided route metadatafiles based in a seperate single file - it works but ... in my opinion after having to unpick things as I got into a dreadful tangle ... this isn;t to be recommended. Look at the existing routes and stock. All have their own metadatfiles.

If you have a single metadata folder that gets the "bluecube ticks" for every route that means that all the metadata you create is being openned and stored ( in memory ??) everytime you open any route. By limiting preloads to specific routes and stock only the relevant preloads are preloaded for any session. I think

I have finally succeeded after following all steps featured in your fantastic "HOW TO" explanation. That was after struggling for 2 days on end. This forum is just fantastic . No better place to learn from the MASTERS

Essentially the stock is basically the same BUT you do not need all that stuff about decompiling.

You are going to need to create a locoinformation folder that is where the image of the loco is stored

Find the folder with your loco's .bin in it - its often called Engine but for multiple units especially these are often called DMOS etc. In this Engine folder create a folder called LocoInformation. You do not have to have an HTML file in here - it is just used to display text and the sim works perfectly well without it.

Next grab a picture ( using the CTRL-S technique above ) form the sim or an even easier way is to open the loco's manuals stored in Railworks and grab one of the pictures ( most pdf readers have a copy facilitity or if using Win7 use the fabulous Snipping Tool.

Then create your 256 x 128 image by either the quick and dirty method or the much, much better alternative outlined above.

Save you picture in the loco's LocoInformation Folder as a file called ( and it must be called ) image.png. I have yet to find a graphics package that can't create .png files.

Bingo you now have a loco pic which will display.

BUT you will soon find you have many many loco pics - for instance with the Class 31 and 08 installed I had one picture for each skin type. This is where your xxxMetadata comes in really handy.

Create a Preload folder again in Asset\Loconame. This is where you are going to be able to save both the (loco)Metadata.bin
and any QD consists or fragments you create to provide QuickDrives for that loco.

If you have any RSC stock like the Class 31, 8F or Jubilee then find their preload directories and copy into yours one the xxxxMetadata.bin - if not do a search on the assets directory and find one to copy. Note that KUJU didn't provide them for their stock (sigh)

Rename the metadata file to something like (MyStock)Metadata.bin. You can rename .bins just fine. SERZ the renamed Metadata file to produce a .xml. Open it in your editor - or use RWTOOLS.

change the line <name> to a name that applies to all the stock you are going to gather together i.e "Class 43 HST". Copy this into the line that starts <English> under the localised string ( its obvious when you get there ). Change the line <Key d:type that starts RS_TXT_XX_GRP to make the XX a few characters like for the HST make it HST or for a class 50 use CL50 etc

Ok now begins the fun. Each Section that starts <iBlueprintLibrary-cAbsoluteBlueprintID d:id and finishes </iBlueprintLibrary-cAbsoluteBlueprintID> contains a reference to your loco. The structure is pretty obvious.

You need as many sections as drivable locos, or DMU driving units, you want to include and each cAbsoluteBluprintID d:id needs to be a different number contained in the quotation marks. However, these are only references internal to the blueprint - which is a blessing - so with a bit of care its possible ( and I did for the Patriot Class ) to have 10's of locos held in it provided you take graet care with these numbers.

The slow way is to do this manually. The quick way is to use RWTools to create a QD fragment that contains all the locos you want and then copy the relevent bits.

Save the file. SERZ it.

Bingo - you should find all your stock in the file now show as a single selction in the SingleUser menus and group together under the scenario menus.

Any that don't - and I have found examples - are caused by the way the stock are referenced in the scenario. If this matters to you open the scenario in edit, change the weather and save it- CHANGE NOTHING ELSE. That should sort the problem

maxtedrw wrote:Essentially the stock is basically the same BUT you do not need all that stuff about decompiling.

You are going to need to create a locoinformation folder that is where the image of the loco is stored

Find the folder with your loco's .bin in it - its often called Engine but for multiple units especially these are often called DMOS etc. In this Engine folder create a folder called LocoInformation. You do not have to have an HTML file in here - it is just used to display text and the sim works perfectly well without it.

Next grab a picture ( using the CTRL-S technique above ) form the sim or an even easier way is to open the loco's manuals stored in Railworks and grab one of the pictures ( most pdf readers have a copy facilitity or if using Win7 use the fabulous Snipping Tool.

Then create your 256 x 128 image by either the quick and dirty method or the much, much better alternative outlined above.

Save you picture in the loco's LocoInformation Folder as a file called ( and it must be called ) image.png. I have yet to find a graphics package that can't create .png files.

Bingo you now have a loco pic which will display.

BUT you will soon find you have many many loco pics - for instance with the Class 31 and 08 installed I had one picture for each skin type. This is where your xxxMetadata comes in really handy.

Create a Preload folder again in Asset\Loconame. This is where you are going to be able to save both the (loco)Metadata.bin
and any QD consists or fragments you create to provide QuickDrives for that loco.

If you have any RSC stock like the Class 31, 8F or Jubilee then find their preload directories and copy into yours one the xxxxMetadata.bin - if not do a search on the assets directory and find one to copy. Note that KUJU didn't provide them for their stock (sigh)

Rename the metadata file to something like (MyStock)Metadata.bin. You can rename .bins just fine. SERZ the renamed Metadata file to produce a .xml. Open it in your editor - or use RWTOOLS.

change the line <name> to a name that applies to all the stock you are going to gather together i.e "Class 43 HST". Copy this into the line that starts <English> under the localised string ( its obvious when you get there ). Change the line <Key d:type that starts RS_TXT_XX_GRP to make the XX a few characters like for the HST make it HST or for a class 50 use CL50 etc

Ok now begins the fun. Each Section that starts <iBlueprintLibrary-cAbsoluteBlueprintID d:id and finishes </iBlueprintLibrary-cAbsoluteBlueprintID> contains a reference to your loco. The structure is pretty obvious.

You need as many sections as drivable locos, or DMU driving units, you want to include and each cAbsoluteBluprintID d:id needs to be a different number contained in the quotation marks. However, these are only references internal to the blueprint - which is a blessing - so with a bit of care its possible ( and I did for the Patriot Class ) to have 10's of locos held in it provided you take graet care with these numbers.

The slow way is to do this manually. The quick way is to use RWTools to create a QD fragment that contains all the locos you want and then copy the relevent bits.

Save the file. SERZ it.

Bingo - you should find all your stock in the file now show as a single selction in the SingleUser menus and group together under the scenario menus.

Any that don't - and I have found examples - are caused by the way the stock are referenced in the scenario. If this matters to you open the scenario in edit, change the weather and save it- CHANGE NOTHING ELSE. That should sort the problem

Thanks again for spending your time to educate us. This "HOW TO" will keep me busy for the next few days. Thanks again Friend

I have just uploaded a file which contains my

Locoinformation pictures and metadatafiles for the following stock

DT 4MT, DT Class 40, KUJU default stock, JustTrains Patriots, RSC 4F, 31 and 101 DMU, RSDL IOW electrics and 08 and S9BL's class 158

Some of them may need an edit - for instance the 5MT Black 5 metafile refs the Gorden Highlander version and the HST metafile refs all sorts fo reskins but nontheless at leats these show what the files are and will save a lot of work I hope

enjoy !

Just a few comments.

1. TS2013 does open EVERY PreLoad folder on startup, (You can confirm this by running Perfmon) this is why when you click the 'Train' button on the Quick Drive screen you get every loco which has a PreLoad folder shown (Unless you limit them via the filters), no matter which route is shown in the metadata file for that loco.

2. As all the PreLoad folders are read and the Loco metadata files obviously read or this QD screen would not be loaded, then it stands to reason that the Route metadata files are also read at that time, so I don't think it makes any difference if you have all the data in your own PreLoad folder or it is in one of the other folders.

3. In the case of the London/Brighton line, RSC have the route metadata file and the rolling stock Consist/Fragment files in the route PreLoad folder, so they don't seem to care.

Mike

Good info Mike. Thanks. Its a bit of an evolving picture isn't it ? In which case I wonder why RSC didn't have a single preload directory ? Maybe to make QD stock portable ? Sort of like when you buy some stock or a route it comes with some preloads / QD's but rather than risk them overwriting something in the master directory if they are in their own then they can be added safely ?

Hope the mod removed my last post (all quote & no comment) Just a quick thanks for the comprehensive stock tutorial
Regards


Sent from my GT-N8010 using Tapatalk 2

I assume the PreLoad files being in the same file as the Loco makes sense from a distribution point of view. All RSC routes seem to come in packs these days along with all the stock/scenery etc. This will make it easier to keep the packs up to date.

Mike