Im trying to get a handle on trains that aren't working at all, or not well, with the Rail Driver. Please post your experiences below, thank you! Matt.
Tap changer locos don’t work with Rail Driver, because when you put the handle into ‘Run Up’ it bounces back to ‘Notch Up’ so you have to constantly alternate between the two. The only exception is the small number of 87s which Roman72 fixed with the mod linked below. JT Benedict has been trying to contact Roman72 to ask how it was done, but with no luck yet. If you could help fathom it out, Matt, what would be fantastic! https://www.trainsimcommunity.com/m...-button-remapping-of-uk-locomotives-for-tsw-5 Outside of that, my only general comment for other traction is the longer the throw of the lever, the better it works. So currently with trains with separate power and brake handles, the game is set up to only use half of RailDriver’s combined Power/Brake handle throw for all of the power notches (i.e. just the ‘power’ half). This means that you move the handle a millimetre, and you’ve gone through 3 or 4 notches. If it could be set up so that the power notches were across the whole throw of the power/brake handle, that would spread them out, which would be much better. Thanks for continuing to spend time on RailDriver compatibility - it’s appreciated. Edit - sorry, I should have given an example - the HST is one where the power notches are all crammed together on a very small section of the throw of RailDriver’s Power/Brake controller.
Ever since the release of TSW5, I have been using Cobra’s Raildriver and Joystick interface to overcome the jitter problem that was prevalent with that release. Besides the jitter, biggest beef I had with DTG’s implementation was the lack of standardization of button assignments… it seems every DE locomotive and EMU has different button assignments for PZB which makes it, well let’s say, exciting to say the least. I thought I was having a problem with the GP60M, but it was operator error on my part… had the wrong profile loaded.
Ok - think we might have a fix for the jitter. I spent a couple of hours scouring the code last night and looking at all the changes that happened around TSW5 and think I spotted a likely candidate for the issue. I've asked for Engineering to fix and then we'll give it a test and see if it actually cured it or not. If not, I will scour more Matt.
Sounds promising, I do have a problem with the Raildriver and joystick interface where it hangs and becomes unresponsive, usually noticed when the alerted button doesn’t work, or the brakes don’t respond when coming into a station. Does keep one’s adrenaline up I must say.. However jousting the native driver (without jitter) would be ideal. One less utility to load.
I belive all implementations of 66 has a problem with train brake bounces back to idle. That way if you have brakes applied you have to constantly shuffle between idle and release.
i think it more that the Raildriver is missing that kind type of lever pull up or down and release the lever always resets to the middle in the cab
The West Cornwall class 37 and 150. Both have the same problem with the throttle going from off to half way open in one move i.e. from zero to about 50% power. Brake is fine though.
Some Just Trains Shap class 47/4's have a problem where the throttle and both brake levers don't work at all, buttons OK. I know the Scotrail livery one has the problem and I'm sure I've had at least one other unresponsive. I'm using the Cobra Raildriver and Joystick interface with a TSC-X
Another two I have problems with:- Rivera 150 throttle range is compressed to only half the the throw of the lever. Nothing to half way then all notches bunched up for the second half. Cardiff 153 is similar but all notches bunched in the first half of the lever throw. Makes it hard to pick a power notch. Note - Cardiff 150 works fine
I’ll second this, it’s the biggest impact to playability for Raildriver or other hardware like the TSC-X I now use. The GP60 has some issues with the throttle / dynamic brakes jumping around that have been documented in the GP60 feedback thread. The only other one I’d mention is the Liberec - Stará Paka route where there is no hardware support without using mods. Thanks for asking Matt!
While the rail drivers works well on TSG’s DB BR 101 expert base locomotive, I noticed it does not work on all the different variations, nor does it work on the cab car
Ok here's a question for you... On many UK trains (and indeed many non UK) the reverser is four position, not three. Off, For, Neu, Rev. The RailDriver lever is a three position lever with a notch in the center for neutral. Should the mapping of the reverser account for all states and you'll just need to find relevant places to let the lever sit that wont be in comfortable notches - or - should it just focus on the for/neu/rev that the device was designed for. I'm torn, because on the one hand I want full control of the reverser on the raildriver - on the other, it feels really odd moving it to places where i have to see what its doing in game to know "this odd position not quite at the end is forwards". Given you only really need to go into Off for a cab shutdown where you're going to need to use the mouse anyway - is it perhaps better to let the "majority" use feel comfortable? My inclination - just map the for/neu/rev. Second Q: Throttle. On the RailDriver, throttle is specifically marked as the top 50% of the control range. It's got the indent between and then what's marked as Dynamic on the other side. If your train has a separate throttle and brake, should it just use the throttle range - or should it use the whole range? My inclination - use the whole range. Interested to hear thoughts. Matt.
Third Q: Where levers have notched resting points, like the reverser, throttle and train brake on the 150 in riviera for example - would it be better for the in-game lever to just snap to those, rather than trying to smooth move between them? Of course is a control is fully smooth then it should do so - i mean specifically like on the 150 throttle or brake where there's no action between notches, just getting to the next notch. My Inclination - map to notches, not smooth motion. I'm playing with the 150 on Riviera at the moment. I've set the reverser up to be for-neu-rev and it lines up perfectly with the raildriver, the throttle is mapped across the whole range and feels much better to control. I've also fixed the headlights which weren't working at all, and the wipers which now have the slow/fast in the right order. Fourth Q: One of the common complaints i hear is that the blue buttons are a bit mixed up between locos without consistency of placement for functions on buttons. I'm considering a review to line them up - but it would obviously mean changing them. Question is - leave the existing ones as they are and conform to a standard going forwards, or, try and create a consistent standard and remap - meaning any overlays you've printed will need to be redone and of course any muscle memory re-learned. On the up side - doing so would mean once you know where "master key is", its always in the same place My inclination - unsure. probably prefer to go through all and create consistency. Matt.
I agree with you: First - only for/neu/rev. Second - use the whole range. Third - map to notches, not smooth motion. Fourth - go through all and create consistency.
As I've said I'm on TSC-X using the Cobra Raildriver and Joystick interface which maps via Rail Driver protocols. I hope my comments are still relevant even though I'm not using a Rail Driver. I'd hope not to lose any functionality on the TSC-X with any changes. Train Sim have put out their own API for the TSC-X but I must admit I've not fully tried it as I'm not sure it allows multiple profiles - I have six for UK traction alone and another batch for mainland Euro stuff wanting the levers to represent the traction layout. Q1 - REVERSER - Like you say a lot of UK traction has an off position for the reverser to allow key removal, I'd like that to be left as is. if you did go to just FOR/EO/REV then where would reverser fall when key was inserted? Q2 - use the whole range. Q3 - map to notches, not smooth motion. Q4 - N/A to me
Have you contacted CobraOne (developer of the interface a lot of us use) to see if he'd have any insights?
This would apply to and affect all users of the raildriver interface - which, i understand it correctly, includes cobra's tool - shouldn't affect the tool itself (so no work required from cobra) but if i make the reverser work differently than it does right now on the raildriver, it will change for all using the raildriver api. I can't see *not * changing some things - for example, the reverser on the class 150 is positively awful atm. The question really is - is consistency more important than upending what you have right now? TBH i'm leaning the other way - fix issues, but dont start going and wholesale changing the library in the name of consistency. Matt.
Q1 I generally just use the keyboard or mouse for reverser TBH. I don’t have anything mapped to it on my TSC-X. Q2 use the whole range Q4 ideally custom mappable. I use CobraOne’s app now and being able to customize buttons (admittedly on my TSC-X now instead of a Raildriver) is great. A general comment is that there are more and more hardware options on the market now than just Raildriver, it would be great to see a future version of TSW have built in generic controller support with mappable levers and buttons, assignable by locomotive (similar to how MSFS2024 handles it). I appreciate that’s likely beyond the scope of what you’re doing in this thread though Matt. Appreciate the engagement!
Q1 - I want all reverser positions available. Several require the reverser to be in the off position to remove the key, Q2 use the whole range Q3 give me the notches Q4 - make them as uniform as possible across the country specific locomotives I.e PZB the same buttons for all German traction. This is my biggest beef with the Raildriver implementation currently, to the fact that for the most part I ignore the buttons since I can never remember them on a loco by loco placement.
Remappable functions probably not in scope, no, and adding support for a generic joystick interface - not currently though it is something i'd like to do at some point. Rather than deepening the well on PC, what i'd like to do is figure out how to open this up for consoles but again that's not on the current radar Matt.
I agree with you - fix issues like throttle range and perhaps add notches where it makes sense. The buttons are not an issue in my case. They are done by key binds so allocate just big yellow button to key bind Q and it covers all flavours of AWS/DVD/TASS/SIFA warnings whatever the internal name is for the command on the traction in the program. I only mentioned CobraOne as he may have had some insight into which traction needed some work and not as a worry about his app. Cheers for looking into this Matt, it's really appreciated. Would love to be able to use the West Cornwall 37 properly
Hi Matt Q1 Agreed, Forward/Neutral/Reverse works. Q2 Agreed, use the whole range. This is the most important one for me. Using the whole range would be a huge step forward. Partly because it reduces the tendency for multiple notches to end up being within a very small part of the range, but also because the ‘notches’ in the RailDriver lever (where the handle moves right and then left through a ‘gate’) are really useful in identifying the position of the RailDriver leaver which corresponds with a particular in-game notch. So, currently if I want notch 3 on the HST I edge the lever in tiny increments through the minuscule zone which includes ALL of the notches until (usually with some back-and-forth between 2-3-4) I finally get the lever into the precise position which the game recognises as notch 3. If the notches could be spread over the entire throw of the lever, I’d soon establish that (for example) moving the lever to the furthest position on one side of the gate = notch 3. That would allow me to select a particular notch instantly without having to jiggle the lever back-and-forth to find the right position. Q3 Agreed, map to notches Q4 Consistency is key. I don’t mind a re-mapping exercise, providing the outcome is consistency across traction. I struggle to remember which button does what at the best of times. When it’s different for different traction, I’ve got no chance. Thanks.
What's the issue with the WCL 37? I just gave it a try and it's mostly sound as far as I can see. Reverser - I couldn't get it quite into reverse. Headlights - not sure what they're doing exactly Wipers - kinda work but can be tuned i think Horn - inverted Otherwise, train brake, loco brake and throttle all worked nicely. Matt.
Bought the Goblin line today as I wanted to explore the DC lines on the WCML South - amused after todays discussion to find the 710 has a 5 position 'reverser'
For me when I open the throttle it goes from off to half open on screen and jumps to about 50% power. I can control it with A / D on keyboard which is what my setup is trying to do. Tees 37 and all other UK diesel locos work fine with same setup. Will have a go at making a custom setup for this loco to see if there's a fix my end. It's odd the West Cornwall 150 is the same too - this uses a different profile along with other 2nd Gen DMU's Cheers for having a look
Oh wait, are you not using the raildriver inputs then for the throttle? or are you using the keyboard because the raildriver inputs arent working? The configuration seems to have a bunch of unnecessary information in it but from the test I did, it didn't have any impact, I had full control over every notch of power on the throttle. Matt.
Using the TSC-X through the interface, the lever is set to throttle in the lever edit and the app takes care if it. I can still use keys binds independently as a fall back in this case. There's a weird thing you need to do for some reason with throttle / leaver allocation I don't quite understand. You have to allocate the lever to both throttle and to throttle / brake and then edit the lever map to only have one active. Hard to explain if you're not familiar with the app. Maybe the cause of this anomaly. Thanks again for trying, especially this late on a Saturday night
Odd. There's nothing special about it that I can see in the setup that would make it work differently to any other throttle. I will grab cobra's app tomorrow and see how it works with my TSC-X. Matt.
I would so like to be able to use my RailDriver, unmodded, with the Routes of TSW6. For me the last good configuration was with TSW4, where there was no "jittering" or jumping of the throttle especially but also the brake; and no phantom notifications like the wipers, reverser. Thank you Matt for looking at this!!
The developer has also created his own software for the TSC-X controller. Those of you who have a TSC-X controller might want to give this software a go. You can find the software here. Sim Workshop Console (Multi-Game Unified Controller Software) – Train Sim Community
wrong link Emmy that is a flight sim link it is Sim Workshop Console (Multi-Game Unified Controller Software) - Train Sim Community and he did loose his software while working on linux version read the comments bellow on that link
@Thorgred Yes, sorry, that was the wrong link – I’ve fixed it. Nevertheless, this software is available to Windows users for the TSC-X controller.
The Sim Workshop app is great, but it still has a few kinks to iron out when it comes to profiles for different trains. Most of the time it crashes or doesn’t recognize specific stock. The best software I’ve found for TSC-X so far is RailBridge - easiest to link, calibrate, and map/split controls out of everything I’ve tried. The most recent updates have made the experience even better. Even the class 350 which has been a nightmare with its lever positions via most controller apps was perfectly fine in RailBridge.
Sim workshop app need a rework/rebuild anyway due to data loss unless they resolved that have not heard any new about its software lately
