Pam Brooker wrote:My big three challenges right now are:
1. Get the loadup picture to show
Pam
YW...I have asked help myself with many given by folks and in return I try always to give back. Sorry Rich, I did say I would back off a little but I had done these before I posted such and it got the better of me so I thought I may as well use them. Pam, I tried a replication of what you may have done....as I did not know your Route name I substituted one as you will see in my pictures and explanations by using RailWorks which I will note as RW. As you can see I have the Real Route names listed and not the default key type.....I thought this would be easier to comprehend as well......as I was doing other tests at the time also.
Here we go....

cln 1.jpg
I cloned Don's Route (
1 ) using RW and named it as (
2 ) as I don't know your Route name. As you can see by comparison of your file structure first up and Don's you have nothing yet as far as folders, that's why you had flat ground, no mountains, etc....some of these will be automatically created when you start using default material or third party stuff by ticking the provider's name in the right flyout when in edit mode and others that will be generated by the Blueprint option if you use a Source folder with your name with appropriate files. The .xml file (
3 ) is generated when you clone Don's Route and has his default paths in it which I will show in the next pic.
cln 2.jpg
As Don had his own Assets folder the paths for finding his Template for others to use and his load screen are noted in your RoutesProperties.xml file and that's why you were having these issues. (
4 ) is his folder ( Provider ) in the Assets folders, (
5 ) is his ( Product ) which is the King's Arm Route and (
6 ) is the bin file that loads as the Template when used by somebody ( you in this case ) and it also tells RW where to find the load screen.
cln 3.jpg
This a breakdown of Don's Asset folder that the above picture is pointing to. The
4, 5, 6 in this picture are what's mentioned above and there is his load screen that your RouteProperties.xml is always loading.
cln 4.jpg
Okay, how do you get around this.....go through the whole learning process of creating your own Provider / Product names by using the RW Source / Blueprint / file option or an easy fix to get your own load screen to work for the moment. Let's go with the easy option just for now....you can learn all that other stuff later.
Using Windows Explorer or whatever you use, create a folder in your Assets folder of RW called ******** ? I used Pam B (
7 as Provider ) add a sub folder (
8 as Product ) called ****** as you can see I named it as such " not knowing your real route name " and the TemplateRoutes folder. Now copy Don's bin file over from his TemplateRoutes folder and place in your folder (
9 ) and put your very own TgPcDx load screen here that you have made also. Rename and edit the KAHTemplate.bin to suit your Route and Asset name. I renamed it NIK-Template.bin for example.
Edit these parts in the new renamed NIT-Template.bin file shown in bold as my example:
1. <DisplayName>
<Localisation-cUserLocalisedString>
<English d:type="cDeltaString">
NIK-Template</English>
2. <TextureID d:type="cDeltaString">
Pam B\Not in Kansas\TemplateRoutes\[00]
Not in Kansas</TextureID>
The first one will make it the same as the renamed bin file and the most important of all is the second one which is causing you all the grief will tell RW to load your very own load screen.
As you have used RW_Tools before the above is quite easy for you to do.
Is that it.....

....no, sorry just one little bit to go.....

cln 7.jpg
On the home straight....now go to
your Route and open up the RouteProperties.xml and edit the parts I have underlined as my example of the names you have to change. There are two bits, one section at the top and one at the bottom of that file.
All the names I have given / shown are examples and not what you have to do. Name them as you see fit for your Route but make sure they are consistent.
Save and go see if your load screen works.....

You do not have the required permissions to view the files attached to this post.