TS2015 Raildriver Interface

[CobraOne]

I haven't got a raildriver, so unfortunately I can't experience your hard work, but all the same I have to congratulate you for such a fantastic achievement. Potentially, your software could open up opportunities for custom built control devices, as James suggests on the previous page. An authentic replica cab setting would be amazing.

Chris

Hi Chris
Thanks for the comment, it certainly helps boost confidence. I am also thinking of converting this to be used with joystick input as well, it shouldn't be that hard, but that will be a project for next year.

Chris

[CobraOne]

Hi Chris,
Version 1.0.1 Feedback

• Speaker option works just fine. Thanks for that.
• I still had problems with the 166. When releasing the brake I can get moving but applying the brake via the DynBrake / Throttle lever (combined throttle and brake) does nothing as the "TrainBrakeControl" value is fixed at 0.
  If I edit the "Railworks_GetData_Script.lua" to stop it detecting the TrainBrakeControl then it works fine as your (fantastic) program no longer sends a brake value of 0 for TrainBrakeControl as it has not detected it. Otherwise it still found it even after removing all old script edits and applying on the simulation script.
• Relating to previous 166 bug. I think we need a way of telling your program to ignore certain controls and it needs to be per keymap. If the setting is stored in the KeyMap file then it will hopefully avoid you having to try and deal with all the difficulties inside you Railworks_GetData_Script.lua script. Simply a custom keymap would be enough to fix many issues (I hope). Maybe an extra tick box at the end of each line with "Disable"
• .rdbak seems to working fine

I am very much enjoying my RailDriver again thanks to you Chris

Jim

Hi Jim
When I run my program and drive the class 166 my program is only sending the ThrottleAndBrake and not the train brake as indicated in the left window. The right window which does show the TrainBrake at 0 is the data I am receiving from TS2015

I have written my program in a way that checks to see if you have a ThrottleAndBrake and if you have, it will then check the key map you have loaded to see if there is anything in the RangeValues or NotchValues for the TrainBrake and if it finds them will use the TrainBrake lever as the TrainBrake instead of the Dyamic brake part of the throttle lever
See Page 11 of TS2015 Interface Readme V1.01.pdf.

Can I get you to restore my Railworks_Getdata_Script and check the key map you are using to make sure there is nothing in either the RangeValues or NotchValues for the TrainBrake ( not even a space). The best way to do this is right click on the TrainBrake row and select in turn 'Delete Notch Values' and 'Delete Range Values'. Also did you edit the simulation files as I suggested.
I am running the class 166 perfectly fine using the 'Default_Inputmapper.xml' map.

Chris

[CobraOne]

Hi Jim
After having a discussion on another forum about this problem with the class 166 I decided to look in the engine bin files for the class 166 and found that the engine script they call are in the MOS folder and not the DMOS or DMOCL.
I used the engine script editor program to revert all my class 166 files back and then edit these 2 files
Assets\RSC\Class444Pack01\RailVehicles\Diesel\Class166\FGW\MOS\Class166EngineScript.lua
Assets\Kuju\RailSimulator\RailVehicles\Diesel\Class166\Default\MOS\Class166EngineScript.lua
and the class 166 ThrottleandBrake works as it should.
As editing the simulation files seems to work fine too, I won't bother updating the documents at the moment. What I will look at doing is updating the Engine Data Extractor to extract the location of the engine script from the engine.bin file, but that won't be just yet, I have other things to do that have been put on hold.
Chris

[Nobkins]

Hi Chris,

I will have another try. I am sure I haven't got any values set for the train brake notch or range values. Will experiment again and send screenshots tonight if not sorted.

Jim

[CobraOne]

Hi Jim
I thought I had better check with you that you don't have another version of the 166 that I don't have. In quick drive I get



Chris.

[Nobkins]

Hey Chris,

Pretty sure I am testing a 100% default unit. I am using a scenario on the Great Western Main Line (Ox Padd by another name) that comes with the route and uses a 166. I don't have any mod's etc installed.

I am on nights. When I get back in the small hours I will have another play with the 166 and send screenshots / attachments of the settings I am using to see if it is me being a fool.

Jim

[CobraOne]

To all who have downloaded my program

To help Jim out can I ask you to look and see if you have the class 166 and if so, try a quick drive with it to see if you can drive it okay.
The two engine files that may need editing are located in
Assets\RSC\Class444Pack01\RailVehicles\Diesel\Class166\FGW\MOS\Class166EngineScript.lua
Assets\Kuju\RailSimulator\RailVehicles\Diesel\Class166\Default\MOS\Class166EngineScript.lua

In the mean time I will try a different machine with TS2015 installed on the D: drive.
Chris

[CobraOne]

Well Jim
I have just run the Oxford to Reading local scenario on another machine with railworks installed on the D: drive and the Class 166 performed perfectly. The only thing I had to do was update my program with the location of the installation.
Chris.

[Nobkins]

Hi Chris,

Ok some progress. Using the default key map it works. Using my custom key map it does not. I get the TrainBrakeControl value in the left panel as described before.

Attached is my 166 keymap. It only has settings specified for Reverser and ThrottleAndBrake. All other settings are as per the default and TrainBrake is empty.
Have I done something wrong?

Jim

[CobraOne]

Hi Jim
I may have just found your problem, by accident!
I ran the Oxford to Reading route with your key map, all fine.
I then exited the scenario, and pressed 'Stop Callback' on my program.
I then clicked 'Start Callback' Alt Tab back into Railworks and when I ran a quick drive using the class 166 I got your problem of the brake pressure fluctuating around zero.

To fix this I Alt Tab out of Railworks, stop and then restart the callback, Alt Tab back into Railworks, move the ThrottleAndBrake lever and all works well.

The answer is to either only start the callback when you are in the scenario/quick drive or completely exit my program and restart it before starting a scenario.
I think the problem is in the fact that the getdata.txt file is not being deleted when you stop and start the callback while Railworks is running, only when you shut my program down. I will have a look at my code logic later and see if I can fix it.

Anyway, give this a go and see if it solves the problem for you.

Chris

PS Your key map is fine too.