Steam Rail Driver: Levers Ingame Move Uncontrollably In Tsw5

The thing is, after calibrating, the levers move without me doing anything. e.g. When in full throttle postion the levers in game constantly move between 100%-97%. The same goes with every other position and even with the brake lever.

I don't know, if I'm the only one with this issue, but im pretty sure that my Rail Driver setup is not broken. That's because in TSW4 it works perfectly fine.

 

RD's electronics are notoriously noisy.
Isn't there a sensitivity setting to dampen those movements?

 

I have the exact same problem with my RailDriver.
From when I sit in the driver's seat, both the traction lever and the brake lever start moving without me even touching the levers of the RailDriver. This with every train. The RailDriver is calculated though. As fenox#5917 said; It's not down to my RailDriver itself because in TSW4 it does work as it should.

Hopefully this will be fixed soon.

 

I have the same problem with RailDriver as well. Not only that, but my xbox controller for pc does the same thing. It's like having a ghost in the cab that monkeys around with your levers, effectively stopping me from playing the game.

 

Should note that did not have this self movement of the switches and controls in TSW4 and earlier.
I have also tried the 710 in WCML and it is affected by whatever this issue is, even though its a TSW4 emu. Since I have found that earlier route loaded via the TSW5 frontend work fine with Rail Driver, its sure looks like a TSW 5 core issue. Now if we could just get Matt or other DTG person to address this.

 

Same here. No issues in TSW4.

 

I have contacted Raildriver and they say it will be a DTG issue as it is working in TSW4. They did send me a link to what could be a useful tool
Not only does it calibrate, it also checks button functionality out side of game. Raildriver will still require calibration within TSW
https://raildriver.com/support/TrainSimulator.php

Trust my luck my Raildriver is arriving from the US next weekend.

 

Yep RailDriver is totally screwed for me here in TSW5. It was never great in 4, but at least it calibrated and worked for some routes.

The irony is they took ‘Beta’ out of the name in settings… but definitely now makes sense why my questions in this forum and on live streams about RailDriver were ignored.

I bought Deluxe Edition on Steam but just requested a refund.

 

As others have said Raildrivers have been seen on desks during the TSW5 Diary series, so they must use them, and therefore they must know of the issues in TSW5. When it will be fixed?
I think I will hold onto TSW4 for a while and keep TSW5 only for the new content. Just in case.

 

I think the fix will be after the official release of the game on September 17

 

Thank you I could cry! Was this already on the radar or is there anything more to share?

 

Thank you Jamie for checking out this post and moving this problem that is effecting Raildriver Controller users up a notch.

 

I have gone through the calibration process several times with no improvement to the twitching of the levers. My Rail Driver works fine in TSW4, Run8 and TSC. Definitely something with TSW5 Raildriver implementation.

 

Several time now without any change to the jiggling or fact that the train brake will not release fully in German locos.

 

calibrated several times according to the video... raildriver still not working properly in TSW 5. in TSW4 no problem

 

The producer of those tutorial videos, trainsimulatordriver mentions the problems with TSW5 and Raildriver Controller in his YouTube video tutorial for driving the Wareloo tube train in WCMLS in TSW5. He highlights the issues by demonstrating the fluctuations with the throttle lever.

 

What I noted today, after following the instructions in the video to make sure that your levers were in the neutral position before and after calibrating that lever, that on the reverser, moved the lever to the full reverse position as requested and when I confirmed calibrate, it also calibrated the neutral position there. So, when I attempted to run it I had no reverse. Now, the throttle did the same thing on the braking side so in game I went straight from handle off to emergency brakes.

 

Thank you Jamie for looking into this for us

 

In this thread in the General section they discuss an interface program written by CobraOne, PC - Raildriver User Feedback Wanted Please | Page 2 | Dovetail Games Forums . It has detailed manuals including a Quick Strat guide and allows the remapping of all buttons and keys and the ability to assign separate ones to individual locos. I have installed and set it up and in WCM using the class 350 the Rail Driver is responding much better. Further there is a sensitivity selector for the controls. Its not DTG giving us what we desire, but again, a member of the community coming to our rescue.

 

I quite like TSW5 (free edition); just wish I could use my Raildriver on it.

 

I have the same issue here. TSW 5 is too sensitive to small jittering of the raildriver, there should be some threshold/sensitivity setting. And yes, in TSW 4 it didn't behave like this and was stable, it's a pure software issue.

 

I see that after more than 2 months of the Raildriver not working very well in TSW5, nothing at all has been fixed as usual.

 

Very very sad - I refunded my deluxe edition for this reason and considering Dovetail go radio silent on any question they don't want to answer, I'm glad I did. Pretty poor show.

 

As noted in similar threads in the General area, its the interface program written by CobraOne long ago for TSC, now updated for TSW, which makes it possible to use your Rail Driver in TSW5. Since installing this program, I have not had any additional issues with the jiggling of controls.

 

I have re calibrated Raildriver 4 or 5 times using Cobraone and I now have the jiggles. Also I have tried to recalibrate in TSW5 with no luck. So Frustrating.
I doubt if DTG will fix this. But, judging by the latest Patch for TSW5 they are very good at breaking things.

 

Interesting MercDriver, I ran WCML today without any problems. What setting are you using for sensitivity, mine is 3. Also, when I do a calibration with the interface, I do not have TSW started. You are calibrating your Rail Driver to the interface, not to TSW.

 

I tried to re-set in TSW, it made no difference. So I went back to Cobraone. I will have to check sensitivity setting.

 

I’m having the same issues discussed here—the brake/throttle levers fidgeting around by themselves only on TSW5 (worked fine up until this update). I hope someone is looking into this!

 

Same here! I miss my Raildriver - unusable ATM

 

Re-calibrated in CobraOne app, set sensitivity set to 3 and I now get no problems with my Raildriver in TSW5.

I had left sensitivity on 0 no wonder I had probs.

Thanks Sharon for the reminder.

 

With all due respect, Please see page 3 Steam - Raildriver User Feedback Wanted Please | Page 3 | Dovetail Games Forums
Several videos are posted showing the issue at hand and an e-mail exchange with PIEngeering/XKeys.

 

Well, it has nothing to do with Pi Engineering there. The Raildriver itself didn't change for sure. The TSW code did.

 

Yes does DTG know how to correct the code so that it works as well as it does in TSW2 -> TSW4 considering it's in Beta after all these years?

 

I am still not able to understand, why some have issues and some not. If it's "the code" than why does it not affect me?

 

You are using the Raildriver with no issues, in TSW5? Not even the Raildriver Mod by Cobraone?

 

I am Adding this e-mail exchange with PI Engineering/Xkeys, in the event you did not see it.
And the link to the video which is a bit long, but it does show several different Locos in TSW5 compared to TSW4

 

SGTDRE I follow this issue on all the recent threads and contributed already, your mail exchange with X-Keys is known to me already

I only have RailDriver acting up, if I play around with the USB ports, you might remember my observation that the ghost inputs only happen, when too much current from the USB port is drawn (and my old story that I once had problems when I got my RailDriver 100 years ago and it immediately went away upon using a different USB port - I simply continued to use THIS port because I don't want Microsoft Windows to detect a new RailDriver all the time and have to go through that calibration process in TSW all the time - you might have noticed that each time a "new" RD is detected, a new ini file is created for it in the TSW local user folder?) .
I don't use and I don't need CobraOne 's tool since my RailDriver is not acting anything different than in TSW4. That's not a problem with the game, it's a problem with your local setup. That's why no one can help you as long as you don't follow that path to rule out errors. BUT as I said I'm following the discussion(s) about this topic and I'm not suggesting it can't be an error with the RailDriver itself, considering it's on the market for a long time and maybe there are different hardware revisions, where newer ones have this ghost issue, older ones not? It's not (yet) investigated by the community.

Of course it's strange that DTG isn't writing anything regarding this topic, maybe they know how the community shoots the messenger when they don't want to hear bad news (it's not our code it's your system) and as long as this silence continues, people come up with "the code has changed" postings even though only DTG knows IF there were changes. Until then, we can speculate as much as we want. Thankfully there is a community tool that seems to help those with jumpy inputs.

I am an IT guy and in my world an issue like that needs investigation and no speculation. You can't be "a little bit pregnant", it's working or not considering the setup, hardware and gameversion is all the same at all participants.

 

The above post with the e-mail exchange, was to get the attention of DTG, as long as you are having no issues, then that is a good thing for you, The one thing that cannot be dismissed is that more than just a couple people are having this issue, where it never happened in TSW2 -> TSW4, there have been no hardware updates, or changes, at least not on my system or RD, trying a different USB port is worth trying, but I have used this same RailDriver with TSW2 -> TSW4 with zero issues, even though it's still in Beta.

And yes it is very disconcerting that DTG can't take more time to get involved to even try and see what could be the issue, But that is just the problem, in the way the game is coded and when the manufacture PI Engineering makes the statement that it has something to do with the coding and not device, that says something.
Are you referring to "AppData\Local\PI Engineering\MacroWorks 3\AppSettings" If so I only see one ini file as well and in "Documents\My Games\TrainSimWorld5\Saved\Config\WindowsNoEditor" I see only one RD.ini


Now that I think about it, my Raildriver has been plugged into the same USB port while playing TSW3 and TSW4 on my PC and now TSW5, and I never changed the USB port. But there is one thing I have not tried, unplugging all USB devices, cables included, shutting the PC down and turning off the power supply waiting 10 minutes, Plug in all USB devices, and starting up the PC and seeing how everything is working. This suggestion is directly from MS, like a refresh of the system.

 

What baffles me is that there was a fix for issues with RailDriver in TSW2-3-4, but not in TSW5. It is the one consistent thing that has been fixed with updates, but now it seems there is not acknowledgement of the problem. I understand the comment above about local set-up; maybe it's time to delete my Raildriver.ini file and let it reload. But this could also be fixed with an update, for the many many people who are having issues with RailDriver in TSW5.

 

Many thanks for your reply! I'm refering to the RaildRiver.ini in Documents\My Games\TrainSimWorld5\Saved\Config\WindowsNoEditor and I got it wrong - there is not a new file created each time the RailDriver is connected to a different port, but a new LINE inside that ini file (pointing to the hardware id of the USB device). From what I can see this file saves the calibration information. I guess there might be some sort of conflict, if more than one device is listed there.

 

I just looked at mine while the game is running, here is what I see.
Documents\My Games\TrainSimWorld5\Saved\Config\WindowsNoEditor

 

Upgraded to TSW5 this weekend, having read previously about Raildriver issues with it in this thread. I re-calibrated it a couple of times to get it more or less where it was back in TSW4 (it had 'uncalibrated' status when I first launched into 5, so the settings didn't carry across).

Today's test was a 375 on SEHS and then 710 on Suffragette. The Raildriver is definitely more jittery in TSW5. I noticed it mostly on my Reverser lever, which showed the status of the reverser frequently on the 710 despite me not touching it.

The 710 (on AC, per above) may have changed for me or it may have been that way in TSW4 but I feel like there's a difference - I seem to have much more granular control over the Throttle percentage now. I'm sure in 4 it was much more stepped with the Raildriver. Not necessarily a bad thing, just different.
Additionally, I played the 'Sector OC' scenario on Suffragette for the first time, and when the prompt asked me to put the CBTC into Emergency Brake, it wouldn't accept the Raildriver doing it (even though I got a feedback popup showing that the handle was in that position). I had to move the handle out of Emergency, then back in using the keyboard, and then the game acknowledged. Can't say this is directly TSW5's fault though, but it's a problem nonetheless.

The main issue I had in that session was the 'Alert' button not triggering AWS Reset/DVD reset. In my final run (a Free Roam on Suffragette to try and reproduce the issue) I got the Alert button to work fine, but I had just re-calibrated in the Main Menu. I'm not sure calibrating mid-game produces good results; it seemed to cause me issues - any other anecdotes there?

Anyway, hopefully my Raildriver is settled now, but I need to try some non-EMUs and see what happens. I sympathise with anyone whose device isn't working properly - I hope this gets sorted soon.

 

And you are not using the cobraone RD tool? And it is working without the wiggles and jiggles?

 

Hi Jamie
Can you please advise of works completed to date on the Raildriver issue, and how far off you are in delivering a permanent fix/update.
Thanks and Merry Christmas to you all at DTG

 

Hi Sharon
Can you please advise where you downloaded Cobraone software from, I found one site but had problems when unpacking it from the Zip file, I had to skip a few files that refused to unpack. Thanks

 

Don’t worry all good, I managed to find CobraOnes post on the DTG forum and so far so good.

 

Personally I've given up hope on this being fixed. This hasn't even shown up on any of the past roadmaps with zero acknowledgement of it other than Jamie's post. I can see why since I doubt any of the Thomas the Tank Engine vehicles will support it, so this will likely go to the back of the Dovetail priority list along with suspension to TSW4 trains. Until they at the very least, publicly address it on a roadmap video, my wallet remains closed.