Hi,
I just got a Raildriver ... been through (at least some of) the forums ... to find out Steam Engines (generally) don't work ... a little disappointed ... but NEVER GIVE UP!
Well ... I've been playing around a bit and might have found a solution (no Asset changes, no keyboard reprogramming ... just a possible fix). Keep reading if you are interested.
For this example I'm going to use the Norfolk & Western - Appalachian Coal: Westbound Merchandise Train session in TS12 ... but feel free to try another.
1. Plug in Raildriver.
2. Start Trainz
3. Start the session (let it load to the point where it is ready to start driving) ... I am going to assume that at this point when you pull back on the throttle, the Steam Engine just sits there ... fear not ... that's why we're here.
4. Shut down Trainz (important! You must exit all of the way out).
5. Startup Windows explorer and find your Trainz installation directory (mine is C:\Program Files (x86)\N3V Games\Trainz Simulator 12).
6. In that directory find and open the trainzhid.log file in a text editor (notepad will work just fine).
7. Scroll down to the bottom of the file where you should see something simular to this:
Set Str Prp called for current-engine-kuid=<kuid:523:1972916>
Set Str Prp called for current-interior-kuid=<kuid:523:1972918>
Discovering engine type for <kuid:523:1972916>, recursion 0
New Property current-physics-model has value 2.000000
path of filename: \config.txt
opening file: \config.txt failed!
Set Engine Type failed
What's important in the above lines are the two lines in Red
The reason that the Set Engine Type failed for <kuid:523:1972916> is that the file located in the Trainz Installation\Controllers (for me it would be C:\Program Files (x86)\N3V Games\Trainz Simulator 12\Controllers) called EngineKinds.txt DOESN'T have the engine listed, so it can't realize that it's a steam engine. So, let fix that!!!!
8. Go to the Trainz Installation\Controllers and open up that file (EngineKinds.txt) in another copy of notepad and let's add that engine to it. Again going to the bottom of this file, let's add another line... the line in Red is the one I added (there are a whole lot more lines than shown ... just an example of what was towards the end of the file and what was added by me. Please note: I not only added the <kuid:523:1972916> but I also added a space and the word STEAM and I hit the enter (or return) key. Note: The reason I said open ANOTHER copy of notepad is that it's really nice to be able to cut and paste the kuid (avoid mis-typing, etc) ... but you are welcome to type it in manually if you'd like.
<kuid:-1:42004212> MODERN
<kuid:61119:81000> MODERN
<kuid:-1:42004213> MODERN
<kuid:67873:51940> STEAM
<kuid:523:1972916> STEAM
9. Now save the updated EngineKinds.txt file.
10. So .. what are you waiting for! Fire it up ... let's see if it worked!
I have found it does ... in-fact ... I have done this for a number of steam engines and so far they have all worked (even from Add-on Packs, SnC, Murchison 2, etc, etc, etc). And when I pull back on the throttle to give it some power, the steam engine starts moving ... and the throttle can be controlled.
Notes:
a) I have been able to start multiple sessions with unworking Steam Engines and the trainhid.log file had information and failure statements about each of the kuids ... so typically, I think you can try more than one locomotive before shutting down trainz and adding the failed kuid(s) to the EngineKinds.txt file.
b) I would think you could do something similar with non-STEAM engines that don't work ... just add MODERN rather than STEAM after the kuid (and a space) ... although it might be that it just defaults to MODERN when it can't be found in the EngineKuids.txt file ... I've never really had any problems with non-STEAM engines yet.
c) REMEMBER ... you MUST restart Trainz before the changes in the EngineKinds.txt will take place: Alt-Tabbing out of Trainz to the desktop, then making the changes, followed by Re-focusing back to Trainz and trying it, without fully restarting Trainz, well ... just doesn't work!!!
d) Also, keep in mind that if a session doesn't start with the STEAM locomotive selected that you are interested in driving with Raildriver (which isn't working) ... you are going to have to (at least) start 'Driving the train' so that you can see the failed results in the trainzhid.log file, otherwise it probably won't even show up in the log file.
e) Oh ... and I wanted to show you what happened to the trainhid.log file after running the session a second time with the added Engine to the EngineKinds.txt file:
Set Str Prp called for current-vehicle-kuid=<kuid:523:1972911>
Set Str Prp called for current-engine-kuid=<kuid:523:1972916>
Engine type set to: STEAM, index is 2
Set Str Prp called for current-interior-kuid=<kuid:523:1972918>
New Property current-physics-model has value 2.000000
This time ... it found it (<kuid:523:1972916>) ... and set the Engine type to STEAM!
Please ... feel free to share your experiences ... and I hope it works for you too! Good Luck!
I just got a Raildriver ... been through (at least some of) the forums ... to find out Steam Engines (generally) don't work ... a little disappointed ... but NEVER GIVE UP!
Well ... I've been playing around a bit and might have found a solution (no Asset changes, no keyboard reprogramming ... just a possible fix). Keep reading if you are interested.
For this example I'm going to use the Norfolk & Western - Appalachian Coal: Westbound Merchandise Train session in TS12 ... but feel free to try another.
1. Plug in Raildriver.
2. Start Trainz
3. Start the session (let it load to the point where it is ready to start driving) ... I am going to assume that at this point when you pull back on the throttle, the Steam Engine just sits there ... fear not ... that's why we're here.
4. Shut down Trainz (important! You must exit all of the way out).
5. Startup Windows explorer and find your Trainz installation directory (mine is C:\Program Files (x86)\N3V Games\Trainz Simulator 12).
6. In that directory find and open the trainzhid.log file in a text editor (notepad will work just fine).
7. Scroll down to the bottom of the file where you should see something simular to this:
Set Str Prp called for current-engine-kuid=<kuid:523:1972916>
Set Str Prp called for current-interior-kuid=<kuid:523:1972918>
Discovering engine type for <kuid:523:1972916>, recursion 0
New Property current-physics-model has value 2.000000
path of filename: \config.txt
opening file: \config.txt failed!
Set Engine Type failed
What's important in the above lines are the two lines in Red
The reason that the Set Engine Type failed for <kuid:523:1972916> is that the file located in the Trainz Installation\Controllers (for me it would be C:\Program Files (x86)\N3V Games\Trainz Simulator 12\Controllers) called EngineKinds.txt DOESN'T have the engine listed, so it can't realize that it's a steam engine. So, let fix that!!!!
8. Go to the Trainz Installation\Controllers and open up that file (EngineKinds.txt) in another copy of notepad and let's add that engine to it. Again going to the bottom of this file, let's add another line... the line in Red is the one I added (there are a whole lot more lines than shown ... just an example of what was towards the end of the file and what was added by me. Please note: I not only added the <kuid:523:1972916> but I also added a space and the word STEAM and I hit the enter (or return) key. Note: The reason I said open ANOTHER copy of notepad is that it's really nice to be able to cut and paste the kuid (avoid mis-typing, etc) ... but you are welcome to type it in manually if you'd like.
<kuid:-1:42004212> MODERN
<kuid:61119:81000> MODERN
<kuid:-1:42004213> MODERN
<kuid:67873:51940> STEAM
<kuid:523:1972916> STEAM
9. Now save the updated EngineKinds.txt file.
10. So .. what are you waiting for! Fire it up ... let's see if it worked!
I have found it does ... in-fact ... I have done this for a number of steam engines and so far they have all worked (even from Add-on Packs, SnC, Murchison 2, etc, etc, etc). And when I pull back on the throttle to give it some power, the steam engine starts moving ... and the throttle can be controlled.
Notes:
a) I have been able to start multiple sessions with unworking Steam Engines and the trainhid.log file had information and failure statements about each of the kuids ... so typically, I think you can try more than one locomotive before shutting down trainz and adding the failed kuid(s) to the EngineKinds.txt file.
b) I would think you could do something similar with non-STEAM engines that don't work ... just add MODERN rather than STEAM after the kuid (and a space) ... although it might be that it just defaults to MODERN when it can't be found in the EngineKuids.txt file ... I've never really had any problems with non-STEAM engines yet.
c) REMEMBER ... you MUST restart Trainz before the changes in the EngineKinds.txt will take place: Alt-Tabbing out of Trainz to the desktop, then making the changes, followed by Re-focusing back to Trainz and trying it, without fully restarting Trainz, well ... just doesn't work!!!
d) Also, keep in mind that if a session doesn't start with the STEAM locomotive selected that you are interested in driving with Raildriver (which isn't working) ... you are going to have to (at least) start 'Driving the train' so that you can see the failed results in the trainzhid.log file, otherwise it probably won't even show up in the log file.
e) Oh ... and I wanted to show you what happened to the trainhid.log file after running the session a second time with the added Engine to the EngineKinds.txt file:
Set Str Prp called for current-vehicle-kuid=<kuid:523:1972911>
Set Str Prp called for current-engine-kuid=<kuid:523:1972916>
Engine type set to: STEAM, index is 2
Set Str Prp called for current-interior-kuid=<kuid:523:1972918>
New Property current-physics-model has value 2.000000
This time ... it found it (<kuid:523:1972916>) ... and set the Engine type to STEAM!
Please ... feel free to share your experiences ... and I hope it works for you too! Good Luck!
Last edited:
