Steam Raildriver User Feedback Wanted Please

Where can you get it?

 

https://forums.dovetailgames.com/threads/ts-world-raildriver-and-joystick-interface.61440/

The above is the thread discussing the evolution of the program ever since TSW2.

https://www.dropbox.com/scl/fi/8qh3...ey=y28j41v1002trj53n43a4n9f1&st=k7kfg7t3&dl=1

and the above is a link to the latest version

 

Did you try the same 66 or the new DB Red one that comes with TSW5? Part of the issue I think is that RD is still done on a per loco basis. If you get someone who knows what to do (e.g. Just Trains) or you get someone who has done it before then you'll get a decent outcome. If you get someone who has not done it and is doing it for the first time it is not a great experience. We did see this on TSW4 locos too which got fixed after I bugged them. I have bugged lots of TSW5 specific loco feedback and will likely log some more from this thread.

 

I didn’t run any 66’s. The problem was noticeable on all the locos I ran on the new routes. Even on tsw4 emu’s like the 710 on the goblin line I noticed the jitter which I hadn’t noticed before. I would not think the Raildriver’s sensitivity would vary train to train since they all use the same calibration. Button mapping and axis mappings yes of course, but not calibration.

But I am now using CobraOne’s interface, while not eliminating the inherent jitter totally, it has made it where it isn’t a concern. I do like the fact you can modify the Raildriver axis assignments and button maps on a per train basis as well. This feature is not readily available in TSW’s Raildriver implementation.

 

I have installed and setup CobraOne's interface program and it seems to help, at least on WCM using the class 350. It took me a number of try's to get it right. Will work on sensitivity setting to see how they help. One question, when changing the sensitivity, do you have to press the callback button again.

 

Just did a short run with the DB Vectron in new German route and worked fine. Slight fidgeting with the levers but moved the sensitivity to 2 and it settled down some. So, Rail Driver is back thanks to CobraOne.

 

Interesting. I will have to look at CobraOne.
I played routes back to back today in TSW4 and then TSW5 to compare not only the RD but also the routes visually. I re-calibrated RD for each change.
My first route was WCML in the 390, after calibrating twice, the second from after escaping to menu from within the 390 the RD did seem stable, that Hill Start clicking on an off is so annoying. However when I changed to BCC and the 323 still in TSW5 I had to re-calibrate the RD for it to work in the 323. In TSW4 the RD is rock steady.
I moved to one of my favorites, Class 101, Its a real treat to drive with RD, rock steady in TSW4. All over the place in TSW5 even after 3 re calibrations with the throttle, brake, and gear selector shaking about.
So is this the norm re-calibrating the RD for each train driven?
It seems that DTG have not come back to us yet apart from advice on calibration that does not fix the issue.
We need to post on a regular basis to keep this thread noticed.

 

I do not know if you experienced this issue with the class 66. I always, when releasing the train brake, had to play this little dance of moving the handle back and forth slightly to get full release. It had a tendency to go back into hold if it wasn't moving. Well, with this interface installed that problem has gone away. Put the brake handle into release and it does, no dance needed. I have now driven the class 350, DB red Vectron and the DB red class 66 and did not have to recalibrate the Rail Drive once.

 

Can someone give me the quick run down of how Cobra's interface works with the Raildriver? Is it something that must be opened on its own each time we play the game, or is it something that integrates natively when we open TSW5?

 

It is a separate program that runs outside of TSW. What I like about the program is it give you control over both axis and button assignments and you can set up different profiles for different locomotives. I have used CobraOne’s driver for TSC for years and it isn’t really any hassle to start the program then start TSW — you can start it after you open TSW as well because you can start and stop callback as well in the interface for the program

 

Just a fast feedback before I forget again

I calibrated my RD with TSW5 once and it works like a charm, no degradation compared toTSW4.
Paul's video was quoted already and the most important part is "keep headroom during calibration" - with this in mind all the stuff (bail off etc.) works like a charm, the throttles have the entire "spectrum".

During calibration you have visual feedback if RD is acting up. I've had this behavior once when I got the unit like 5-6 years ago. The "fix" was to use a different USB port. I connect my RD to the same port every time and get the same (good) results all the time.

 

I am finding that I have to start this program each time I run TSW, though that is not an issue for me. Open it and click the start callback button and that's it. You will note here that I have settled on a sensitivity of 2 as best for me.

 

Looking at CobraOne’s interface apart from getting stable levers, my main objective is to map the buttons so that the main functions remain the same regardless of train driven. For example:- Return to menu, Camera 1, Camera 2, 3, 4 and 8, also view Timetable and map. Looking at steam locos the levers should cover most controls and mouse control for the valves. Is that possible or will TSW5 over right the settings when a loco is selected.

 

Once you load CobraOne’s software, it is used exclusively for TSW. Besides the lever/axis assignments, you will load a standard button map assignment as well. This you can customize and use one for all locomotives or do a button map for each individual locomotive… assign that map to the locomotive and it will load when you select that loco.

I am in the process of creating a custom button map for Germany locos/EMU/DMU so I can finally have consistent buttons for PZB controls as well as AFB .

 

I'm wondering if it's possible to directly copy over the Raildriver dll file from TSW4 over to TSW5 to see if that makes a difference.

 

Thanks, all good now.

 

No that will not work I just tried it, and while it did work about 2% better, everything is still very much a nervous wreck "Well that is what the train is looking like".

It is just amazing how key features that have been in TSW__ going back to TSW2 and work have worked even being in Beta all these years. DTG still has a hard time keeping things working.

Over the years I have come to rely on and "Really" need the Raildriver, without getting too deep into personal issues, My dexterity is not what it used to be, on top of having learned to be a southpaw, the Raildriver "Really" is indispensable more so now. And I would think and expect DTG to do a much better job at keeping ALL the control interface(s) working at its peak efficiency. Silly me.

And again I say, if it was not for the modding community, I doubt I would still be involved with TSW__... For the German trains, I have been using modded files for the Raildriver made by a modder so that the Raildriver controls matched the train controls.
Looks like I to will have to have another program running made by a modder CobraOne, Just so I can use the Raildriver as it should be, I do appreciate the time and effort it took to create the program, for us all to use and yes enjoy, I'm thankful, it's just that I have plenty of programs running already. And seeing that it will make things easier for me, then I have little choice and it's the modding community to the rescue.

 

I have to say, that once I got CobraOne's interface set up the way I wanted it, it runs without any major issues.

 

Good to hear. It's a strange situation. While many are having issues with RD in TSW5, mine is working normally without mods. Just an occasional issue with the reverser slipping out. I rarely play German routes these days, perhaps that has something to do with it.

Obviously though, DTG needs to refresh the software for the RD app. I assume it's still in beta.

 

I really do not think that anyone from DTG is looking at this thread, let alone trying to fix the issues.

Raildriver users maybe a minority group, however, collectively this minority group has spent many, many, many £'s $'s or Euros on your product. So please fix it, or at the very least keeps us informed of any progress you are making. One last thing do you not think that the set-up pages in game for Raildriver should be out of BETA after all these years.
TSW5 is my first encounter with a new DTG product release. WCML is still the runt of the litter and in your own words will never be brought to the same level of the German F&F.

 

Maybe someone should tag Matt Peddlesden

 

I think Dovetail have got a lot on their plates at the moment fixing up the launch routes, so it's understandable that the Raildriver issues are put on the backburner for now. However, I just want to comment that the Raildriver implementation for the Class 350 is the worst one I've ever encountered.


Typically the Raildriver will allow itself to be overridden by the user input, which is extremely helpful for those of us with older devices that might have a stuck wiper key or reverser. This means I can leave an input on the Raildriver at a comfortable position, then use the mouse to manually set it inside the virtual cab, and it will save it at that position. However, the 350 will always prioritize the Raildriver, meaning I am constantly fighting against the wipers or the throttle despite attempting to use the mouse to manually set it, and it will always revert back to whatever position the Raildriver is at.


Personally, I've always had problems with my hand accidentally touching the reverser handle while operating the throttle, so this workaround was great for me since I can just move the throttle all the way forward so I won't ever come into contact with it, but the way the 350 is set up means operating using it is borderline impossible, especially since it's set up to emulate how it is in real life with the reverser notches in between the middle and off position.

Although it wasn't their intention, it really feels like they're deliberately sabotaging the Raildriver experience with TSW5. The twitchy-ness feeling and this has me resorting to my Dualsense controller for the time being operating the newer routes, and I've even installed TSW4 back on to my hard drive, because it was significantly more stable and generally a more fun experience using this bit of kit. This brings us back to the question of why change something that didn't need to be changed. Whether it's this or the background image for the live track map, they always try to innovate by changing something for the sake of changing it, without thinking of the user input. The time they spent changing the Raildriver could have been used to actually innovate on something meaningful like automated announcements, ebula, or PTC for US routes. It makes zero sense and just boggles the mind the thought process behind this.

 

Like you say they have a lot on their plates. However, who's fault is that.

Why mess with something that was working. I have seen Raildriver Controllers on desks in DTG video's post TSW5, so we know they must do something with them otherwise it is just a very large object of clutter on a desk. Like you say they tinker at the edges of things that do not need it. So it just becomes change for the sake of change. What really annoys me is that I have only just received my Raildriver, it and TSW5 arrived near enough together!

CobraOnes interface does work but I find it a bit clunky, and I still have had to recalibrate in game to get certain trains to work well with RD.
I will give it another go tomorrow.

 

MercDriver, I thought with CobraOne's interface, the in game calibration was not effective.

 

It did recalibrate in game. I was finding that after I had calibrated RD in CobraOne and after Start Callback that the range of control was compressed and only operated in the final sections of travel on the combined throttle/brake lever.
I don't think that I set CobraOne up correctly. In the end I just wanted to drive as I do not get much free time to to drive and experiments eat away at that time.
I will try and take my time tomorrow and try again. I wish I had the luxury of a spare room with my rig permanently set-up

 

For those who have a flight sim stick with a throttle, (for example a hotas 1 or hotas x, assign your throttle unit as a throttle in cobras TSW programme, brings driving trains to a whole new level!

 

Why do we need a third-party mod or whatever it is, to use a standard controller in-game which is now indicated to be out of Beta and has been adjusted/fixed on every iteration of the game.

 

Because it works . It also provides one the ability to modify not only the lever and axes profile but remap the buttons as well. Finally, it supports other peripherals other than the Raildriver.

 

MercDriver, Well I tried using in game calibration on the 390 in WCML and now my reverser is totally messed up. I have gone back and recalibrated it twice in the interface program and I am unable to get the reverse setting with the Rail Driver. I have tried several different locos on different route, same result. I can live with this since reverse is hardly used and can get to it via keyboard. Based on this I do not recommend using the in-game calibration with this program. If anyone has thoughts on how to correct this, I am listening.
Going to see, later, if a third recal will help. After the first I had off and forward, the second go got me neutral, maybe the third will restore reverse.
The third recalibration did not help, still can't get the reverser handle into reverse.

 

Hi Sharon sorry Raildriver is messed up for you.

Before I started today the first I did was to add the PIEHid64Net.dll file in the following directory C:\Program Files (x86)\Steam\steamapps\common\Train Sim World 5\WindowsNoEditor\TS2Prototype\Binaries\ThirdParty\PieHid\Binaries

Then I started TSW5 and opened CobraOne and re calibrated Raildriver as if I were using it for the first time, then Started Callback. All of my levers and control switches and top buttons acted as expected in game when I loaded up a service in a Class 350. Those same controls functioned in all of the trains I tried Class 390, 710, 101, the exception was the Bakerloo 72 class which I was not that bothered with.

The problem I no have is with the 28 buttons. The only buttons I find useful are 1 escape to menu 15 close HUD and 3 DRA.
Some useful presets would be good, Using the last 5 pairs for camera views, view Map, View Timetable etc etc. Some useful instructions/video on how to map the buttons. the manual does not even provide a single example of how to program a button.

 

MercDriver, I looked in my Binaries folder and it's there with the original as a bk file. I then found the default folder in the TSW Rail Driver file on my C drive adn copied this one, deleted the active one in binary and replaced it with the one taken from the default folder. Made not difference, I still have no reverse and checked several locos.
I have also posted in the Ts World Raildriver And Joystick Interface thread.

 

As LeadCatcher stated, it does give more freedom to make it like you want it, and if you choose a joystick to play you are free to do so. This is how all this should have been scripted and coded into the game, it just baffles me how after all these years DTG still can't get this worked out, yet the modding community can, or is it just, "leave it for the modders to come up with a fix".

 

Soooo, something strange happened today, all of the sudden I've had my throttle, AFB and Brake jump around 1-2% in an ICE1 where as yesterday (and the years before) I've not have had this issue.

So while I was driving I thought about "where does this come from now? the people in the forums told you so? what changed?", the last update was a couple of days ago so why should the issues with the RailDriver start today and not already yesterday? Then I noticed what's different: I've had my phone charging via USB while driving, something I haven't done yesterday evening.
I pulled the USB cable out of the phone in in that very moment the twiching/jumping stopped immediately and RailDriver was back to normal. To test my theory (it's all about the USB port and not about TSW or the RD unit), I plugged the loading cable back into the phone and the issue started again in that very moment. Of course I won't charge my phone on my PC while playing TSW anymore ;-)

Hope this helps someone. Try different USB ports and try to unplug devices that suck current via USB while you want to use your RailDriver.

 

While I never charge my phone via my PC, I do have a USB HUB that has just charging ports x3, and the rest are either mice Xbox dongle, HDD Dock, portable CD/DVD player all my USB ports are used on the back of my PC even USB C ports, and one of the solutions to USB issues is to power down the PC, unplug ALL USB cables and devices, wait 10 minutes or so, reconnect everything and boot the PC, and all "should" be working better, something to do with Win 11.

So what you did was and could be a solution, it is worth a try, but then why is it only in TSW5 that the RD is acting like a nervous wreck? And yet Sharon E has done what we all have done and yet has no reveres but all else works, software is a fickle lady.

 

I am sure you are on to something there -- but with 14 USB devices plugged in -- (Keyboard, mouse, TrackIR, Honeycomb Alpha, Bravo, Rudder pedals Bose Sound amongst others) all on powered USB hubs - nothing on my configuration when is comes to USB configuration changed and TSW5's raildriver was twitchy... TSW4's (with the same USB configuration) raildriver was not twitchy. Anyway - no problem since I do like the CobraOne interface better and it has been rock solid after I adjusted the sensitivity level.

While that might have solved your particular case, I rather doubt everone who has reported the twitchiness were in the process of charging their phones. It would be a good ides to see if their raildriver is on an unpowered hub - changing to a powered hub or dedicated USB port on the mother board to see if the twitchiness is fixed.

 

Since I have sorted out CobraOne I no longer have any twitchiness in the control levers. They all work in the tractions I have tried so far, but there is no consistency in the range of operation. Some tractions have no dead zone in the Reverser, Combined brake/throttle, and brake levers, whilst others have a very small range at almost the end of travel, but still cover the range of settings.

What I really need is some guidance on how to set up the 28 buttons so that I can have a common set of functions to use on all tractions. I cannot see me no longer using my mouse for in cab functions, it is the things that have me reaching for the keyboard that I want to have on the RD. The CobraOne manual does not provide even one example of setting the buttons.

 

I am working through how to map the buttons myself - I have copied the default button map and modified it to use the alert button on the raildriver for AWS/DSD/PZB acknowledge so that is consitent across the locomotives - but that is as far I have gotten - top row buttons on the raildriver are buttons 1 -14 and bottom 14 - 28 but have noticed on especially the german stock the actions in TSW are all over the place as they are with DTG's driver- to be honest - haven't had time to dig into any further but have noticed on Train Sim community webiste there are modes available for button assignments.

 

The thing that winds me up with the DTG settings is that there is no consistency at all in the button operation between tractions. They could not be bothered to try and match up commonly used functions.
One of the functions I wanted to add that is in one of the DTG RD settings is DRA. How do you match that when there is not even a key mapping?
Perhaps we could reach out to the creator of CobraOne?

 

For TSW4 I have all the RD mods made by Roman72 but most of what is made to date is all German trains. Now that TSW5 is out Roman72 has made a few new ones

You can download the Raildriver button remapping for DB TSW5 locomotives from DLC Frankfurt - Fulda here.
TSW5 DB Raildriver remapping - Train Sim Community

And some were made for UK trains,
Raildriver button remapping of UK locomotives for TSW 5. - Train Sim Community

Here are downloads of additional Raildriver button remaps for some DB locomotives. <<--TSW4
DB Raildriver remapping - Train Sim Community
I tried the RD Mod for one of the DB trains in TSW5 and for the most part, it works but between the mod by Roman72 and Cobraone's program this is a bit of a conflict, where the Alerter is activating PZB also, I have yet to try and figure out the best way to correct this.

I have held off on trying any other of RD mods because TSW5 and RD are so erratic that I don't see how they could be better, With Cobraone's program it does help immensely, but as stated the button mapping is all over the place, there is no rhyme or reason to the way it was coded, scripted, however, they got this all to work. And that is the Rub...

 

I took a look at the Roman 72 mods and his button assignments are not really what I am looking for. For the mapping to be compatible with CobraOne they need to be in the form of a .xml file and not a .pak. I just wish that CobraOne had provided some clear simple examples of how to program the buttons which creates the .xml in the button mapping section of his manual.

 

Yes, I to would have like to have that also, and I understand many modders like Cobraone are busy with full-time jobs, and other life matters, maybe one day we can get a mapping guide. As for roman72, like the way the RD is mapped but Roman72 mods are limited to German trains mainly, and just recently added a couple for UK trains. I wish there was a good and better wat for the button and lever mapping to be done.

 

I know that LeadCatcher is having a go, and when I get the chance I will have a real go. I have CobraOne on my laptop so I'll plug RD in and have a go. Getting all of my sim rig set-up is job and takes up so much space.

 

Not much has changed still in BETA

Where has all the interest gone?

The ability to map the buttons to your liking, or at the very least have the same buttons have the same function regardless of Traction. Then have a German, USA , UK and Steam versions all preset and picked as a menu item.

 

That is why it's PC only for the moment! Of almost 4 years now, well going on that is. But yet not much changed with the exception of all the issues in TSW54

 

It'll never work on console, it would need certification from the relevant platform holders to work on console.

 

If that is how all that works with consoles, DTG had plenty of time to get it sorted out, there are plenty of devices that are made for people with mobility issues that can be used on consoles, how and what needed to be done to get those devices working with say Xbox would be nice to get a handle on. The will needs to be there.

 

I think you misunderstood, certification of the raildriver hardware is nothing to do with DTG.

PI engineering who developed and manufactured the raildriver will need to get the device certified to work on the consoles.

 

I Would have thought the game developer using the device "Raildriver" would need to work out all the details, seeing that the game developer is using in their game in this case DTG. Why would PI Engineering need/have to get the cert, is it because they created/designed the Raildriver?

 

Basically yes, for example, you can't just pick up a off the shelf joystick and expect it to work on MSFS2020 on Xbox, you need the one that says Designed for Xbox etc.

So yes it falls down to PI to develop a version of the raildriver that works on the consoles, and with train simulation and the raildriver being such a niche product, PI have probably thought its not worth it.

Now this is where DTG could do something, enable joystick support on the consoles so at least those with a Hotas can use the throttle part of the unit, as a Thottle for the trains in TSW.

 

Okay understand what you are saying, it is a bit odd that it works like that, at the same time DTG and PI could get together figure out a way to get a proper train control device be it the RD or something new, console players are "I do play on my XB now and then" left out of the loop so to speak. Who knows maybe one day.