Camera Adjustments

[RobBaker]

Hi Guys,

A very useful forum this!

Ive been searching for ages for a fix to stop the derail 'end game' notice appearing, and thanks to Aidan etc I finally managed to do just that.

Funnily enough, even though I'd edited the .bin file of the train that I wanted to derail, the 'end game' notice still appeared!
So I then replaced the 'derail camera' file that I'd deleted previously to stop the camera rotation, but still the notice popped up and ended the scenario.
Then I think I must have clicked something in the game options (I'm running RW2), and lo and behold - during my next train derail I was able to pan around afterwards with no time limit.

It took me a long time to get there though. I actually installed RW-Tools to edit the XML file and create a .bin file from that, but that was no use as RW-Tools wouldnt properly 'search for' and find the relevant 'derail' line in the XML file. I then realised that I didnt need a utility to create another bin file from the XML file, I simply had to drop the XML file onto Serz.exe. Duh!!! I'd wasted hours.

Derail heaven

The end result was worth it though: As I sped along at high speeds in (Hagen/German?) countryside on a moonlit night, I decoupled two carriages to increase speed. Soon after that my train derailed at high speed on a corner - and the engine landed half submerged in a river (with moonlight refelecting off the water). One carriage ended up slewed sideways across the track. Then I heard a rumbling noise: It was the two decoupled carriages speeding down the track. They hit the derailed carriage causing further mayhem. Then all went quiet. Panning the camera closely around the upturned carriages I could see the interior lights still on and the passengers all sitting unfazed by the action.

My derail antics will no doubt turn off many 'staight-down-the-line" railsimmers, but most on this forum will know the amount of fun/realism that disabling that darn 'end game' notice can bring about :)

Thanks again,

Rob
UK
-----

[thecanadianrail]

ok, can you figure out what exactly you did so i can do the same thing, because i still get the error message and ends game after a derailment.

[RobBaker]

--
> ok, can you figure out what exactly you did so i can do the same thing, because i still get the error message and ends game after a derailment. <
--------------------------

Hi.

...Here's what I did to fix it:

(Apologies if some of these steps seem obvious, but they may help newbies reading this thread in future).

First I foccused on changing all the .bin files in just the 'Electric' folder (the path in my version is
C:\Program Files\RailSimulator.com\RailWorks 2\Assets\Kuju\RailSimulator\RailVehicles\Electric)

The only model in there was the BR101. The sub folders for the BR101 are: 'Blue', 'Black', 'Silver', and 'Default'.
I edited all four sub folder .bin files (which are found in each 'Engine' folder).

To edit the first .bin file I did this:

1. navigated to this folder: RailVehicles\Electric\BR101\ 'Blue\Engine',
2. then made a copy of the .bin file within that 'Engine' folder
3. then copied Serze.exe onto the desktop (its in the main Railworks folder)
4. copied Serz.exe from the desktop into the BR101\Blue\'Engine' folder.
5. Dragged the original .bin file onto Serze.exe and it created an XML file.
6. Then deleted the original .bin file
7. Right clicked on the XML file and opened it with Wordpad/Notepad.
8. Then searched the XML file for the "ShowDerailment" line (I clicked 'Find Next' 3 times to get to it)
9. I edited the 'ShowDerailment' line and changed "eFalse" to "eTrue". (As Aidan suggested).
10. Then I saved the Xml file and closed it.
11. Next I dragged the XMl file onto Serz.exe and a new .bin file was created.
12. Next I deleted the XML file and 'Serze.exe' from the directory.
(Tip: It might be useful to create another XML file from the new .bin file just to make sure that your edit has worked.
You wouldnt need to do this every time though).
13. Finally, I simply repeated the above steps for every Engine folder for the BR101 Train (i.e. BR101\Silver/Black/and Default).

Fingers crossed

I then Started Railworks(2) and ran in 'Free-roam' with the edited BR101 train (blue). I derailed ok but the dreaded message appeared as normal. So I then replaced the 'DerailCamera' file from the Camera folder that I'd deleted earlier.
I then went into Options/Gameplay and unticked 'UserHints', and 'Exit on SPAD' (none of which should make any difference).

But then I restarted Railworks and ran the BR101 train in a Scenario this time (i.e. not in free-roam mode) and it derailed WITHOUT the end game notice!! And when I then ran the same train (in any colour variation) from Free-Roam, it worked fine with no pesky 'end game' message).

My next step is to edit a few more train .bin files, then I'll save the train folder and bin files on another drive, plus I'll probably Acronis/image my PC to save losing all that hard earned work.

Oh by the way. When I went into the Steam Engine folder to edit the .bin files, they had all been done! (weird). So I was able to take any steam train out and derail it without the message appearing. I cant recall if I ran a scenario or free-roam.

Also, when I tried editing the .bin files in Railworks version 1, I couldnt find the "ShowDerailment" line (but perhaps it was just me). Yet I did find it easily in Railworks-2.

Anyway, Hope this info helps get you derailed ;)

Rob

[simer4]

I also forgot to mention that when having a consist that has different types of locomotive, you must also edit theit .bin too.Some engines do not have this line, so a work around would be to add the line I stated before, to the locomotive .bin that does not have this line. .bin I don't understand why there are problems occurring. I edited the files once, and was rewarded first try.

Aidan

[RobBaker]

> Some engines do not have this line, so a work around would be to add the line I stated before, to the locomotive .bin that does not have this line. <
-----------------------

Thanks for the additional info Aidan.

Funnily enough, Ive now LOST the ability to derail without the 'end message' popping up. I dont know whats changed. Certainly Ive been importing trains and using RW_Tools etc, but the edited .bin files are still in place in the locos Ive edited - my current favourite being the awesome A1 Tormado, which looks great at 90mph, and derails with style too.

Oh well, its back to searching for a fix to the derail problem. Life would have been far easier if Kuju had got their act together to add a simple tickbox in the Options menu, i,e. "Quit After Derail". But maybe the gaming life was never meant to be that simple.
----------
EDIT: I just ran an 'A1 Tormado' custom scenario that I created last week, and the Tormado derailed ok with no persky end game message. Yet If I run a more recent custom scenario on the same stretch of track, the Tormado loco derails then the camera spins and its 'end game'.

What could be causing one scenario to be 'ok' and the other not to? Could it be some setting Ive enabled in the World Editor? Or Perhaps RW_Tools has changed the scenario somehow.
Must admit Ive been using RW_Tools to swop locos in various scenarios, maybe its this swopping of locos that is causing the problem and confusing Railworks/.bin files?
---------

Rob

[dick8299]

Try clearing the cache. The game may be loading an earlier version of your loco (before your edit)

[RobBaker]

Try clearing the cache. The game may be loading an earlier version of your loco (before your edit)

Hi Dick,

I tried that. (I'm in the habit of always flushing the cache before starting the sim).

I can only think that somehow the scenario/world editor somehow has the ability to enable/disable the 'end game' message and the rotating derail camera.

[RobBaker]

SOLVED?

I think I solved the problem:
The original unedited .bin files that I'd made copies of, were being loaded by Railworks/Editor (and/or RW_Tools scenario editor). This created duplicate copies of the trains in the editor, one train with enabled derail, and the other with disabled.

I should have stored these files, plus the created XML files, in a seperate folder, but I got lazy and left them in the original folder. I just assumed RW-2 and RW_Tools would only load .bin files with proper names, instead it seems to have loaded the files named "Copy of ....bin"

Thanks to RW_Tools I eventually spotted the problem by editing a scenario then checking exactly which .bin file was being loaded for that particular loco.

Derails are now fully functional