Steam Raildriver User Feedback Wanted Please

There's then the monetary factor aswell, would the price of certification be worth it, would it draw in more sales, the rail driver isn't cheap, and the average player isn't going to fork out nearly £300 on a device for a game, like I said, the cheaper option would be for DTG to get Hotas flight sticks working with the game.

 

You do make a valid point as to the cost "ROI", for many the RD is $219 or thereabouts, and in some other nations it's double, that is a major issue, but many are finding a way to buy the RD, either way DTG should find a way to work something out even if it is a "Hotas flight sticks" after all these years and nothing but some keyboard options and controller. As I have said, where there is a will there is a way.

 

The point is, is that DTG should work to get Railerdriver and Hotas flight throttle working. Hotas will have limitations, I don't know.
The real argument for DTG to fix RD is that they started working with RD back in TSW2 and it still in BETA. It looks like with so many things, fixes, whatever of the past NOTHING gets done. To many fixes are left to the community.
They use the excuse of there are so many tractions, yes there are a lot but split them into geographical regions and the task becomes a lot easier. So UI for the USA, Germany, UK and and one for Steam. For example nearly all UK passenger tractions DMU and EMU have the same single lever control, the same safety systems, the same door controls, lights and wipers. Other functions like camera control are the same. The only variations are Freight traction and Class 101.
The current UI is flawed, the blue button mapping varies so much between tractions, Why?

 

I hardly ever use my RailDriver unfortunately. I was hoping that with physical controls I could get rid of the HUD on trains where the controls are out of sight. I don't think that the RailDriver is flawed itself as I've looked at the raw data for the control movements and they seem fairly consistent. The Dovetail train simulators have this extremely irritating feature where you press a key to move a lever and instead of it moving into the next notch or step, the lever springs back if you don't hold the key down for a certain amount of time depending on system resources. I think that this irritation is still enabled when using the rail driver like it doesn't get to takeover control positions directly the way it would in OpenBVE meaning that say half way on the brake lever might only be initial if you move the control slowly. I drive some British locomotives with the RailDriver but for most trains in TSW I would say that the RailDriver just adds something to fight with, although I'm pretty sure it's TSW that's the problem and not the RailDriver controller itself.

 

And here is the RUB, in TSW2, 3, and 4 the Railriver works VERY well no need for Cobraone's program, I have yet to try his program with the PieHid file his program creates and recalibrating in-game as I did in TSW5 which is working well for me, with a few throttle jumps here and there and I'm using the mods from Roman72, for the german trains and few new ones for UK trains, I can't explain it but it is working in TSW5.
And as I have said why can't DTG get this worked out, properly, and why BETA after all these years? My RD reverser has almost lost its feel for the neutral notch. but still works, very well be it with Cobraone's program or in TSW2 ->> 4 Bottom line.

JUST FIX IT DTG...

 

Has anyone managed to create a button mapping that works using Cobraone's tool?

Today I tried to create a new button mapping. For the most part it went well until I wanted to create the buttons for setting Vigilance, AWS.
The keyboard shortcut is Ctrl+enter and Shift+enter this combination I could not find in the CobraOnes app pick list, and you cannot just type them in. Anyway I got mapped 12 out of the 14 and saved the mapping .xml file, then loaded as the mapping file.

Started game, backed out to CobraOne. Started callback. Back to game to test, all the buttons functioned... YES!. BUT, None of the other levers, switches or main function buttons worked, all dead.

Any ideas folks?

 

I got Matt to address the Rail Driver issue in stream he is doing today and he said "I am not aware that Rail Driver is having issues in TSW5." After several others chimed in, he said he would talk to his testers about this. We will see.

 

I was there, but had to leave. This thread has not seen anyone from DTG for some time.

 

After all the talk on here and on Cobraones thread about the Raildriver and multiple posts that I found doing a search on DTG Forums, NO ONE from DTG saw anything, yet we are told and led to believe that the threads are monitored and read, why I say this? I have seen many posts edited by a moderator and some posts removed by a moderator.
So no one is informing the lead Dev what is talked about? Matt is the Lead is he not, every so often I see him jump in and comment and even get involved with the conversation.
So what is going on here?
I will not buy that for a dollar.

 

You are being generous, I wouldn't buy it for ten cents.
I should add, I forgot to add this to the original post. Matt's response when I mentioned the thread on this topic, "I don't have time to read all the threads". Geeze, that is what you have subordinates for.
Thank the Lord we have people like CobraOne and JetWash to get us past these issues that DTG brings into the sim.

 

Yes, too bad that no-one seems to be reading the RD thread.

Makes you wonder what else they're not reading.

Maybe Raildriver Feedback could be a sub forum in the Player Feedback section?? Might get noticed there.

 

When I heard Matt's comment I was shocked, but not really. I felt he had a bit of an attitude during October Roadmap, calling out negativity in the comments window on Youtube. If TSW5 had got off to a good start there would be no negativity, right? I doubt that the patch will do much as far as this thread is concerned. It sounded to me that the major fixes will be for consoles.
Believe me, like all of us here all I want to do is enjoy driving trains.

I will pm CobraOne and see if he can look at this thread, You never know he maybe able to help out.

 

PM sent, fingers crossed.

 

You know I am not surprised at all, the only time I see a moderator is when they feel it is a negative comment. I Tagged Matt and JD in the Red Bug light thread, no reply of any kind, it is looking more and more like sell it broken or not and just leave it be.
-

Then Matt should not go reading the threads on Steam, many more sour notes are being sung there, and not in the kindest way or terms. More and more people are walking away or just waiting for a sale and jumping on Free TSW5, you can get they will not do this again. That is when I believe it will hit them all hard, and who knows how things will be then.

 

Sure why not, just need to get someone at DTG to put it there.

 

I'm using Cobraones app and there is no twitchy-ness. Some tractions are troublesome like the UK Class 47, but I do not know what is was like before.

 

Bought the RailDriver back in the MSTS days. I still have it but I suspect it's so dirty inside that it may never work reliably. I find the lack of printable keypad legends and the lack of consistency of button assignments frustrating. I think it needs to be re-worked for TSW so that all assignments are consistent.

 

Yes, I agree The Raildrivers needs much more attention, and they need to get it out of Beta, yes they need to get the button assignment as you stated. But for now Get CobraOne's program and user guide with the quick start guide if you have not already, and get it set up. I followed the quick start guide and it was still shakey then I Re-calibrated again in the game and all is working for me well, my reverser is losing its notch but still works.

 

In the rare event a dev is reading through this thread, I just captured two videos showing what exactly we're experiencing in the base game. First video is normal behavior in TSW4. Second is the problematic TSW5. These were done within minutes of each other eliminating any problem with the Raildriver. Both are on SEHS with a 375 with the same service.

TSW4:



TSW5:




There's twitching all throughout the video, but you can most clearly see it in the following stamps:
0:26 You can see B2 twitching
0:47 twitching at neutral
1:21 twitching at B1 braking

You can see the ghost inputs on the notifications on the right side of the screen where any micro input gets picked up and displayed in the small text. None in TSW4, but constant in TSW5.

 

Wishful thinking, but we can live in hope.
Thank you for taking the time to record the videos that prove without doubt the issue with Raildriver is ongoing.
So far we have had a few posts from DTG and nothing since. It would be really good to hear from a dev that is actually looking into this.

 

I could not agree more. As I have said in my previous posts on this thread there needs to be a common set of functions for the blue buttons. As I suggested a set for UK, Germany, USA and Steam Loco's. All the commonly used function should be clustered in the outer buttons.

1 2 3 4 5 -----------------------10 11 12 13 14
15 16 17 18 19 -----------------------24 25 26 27 28

The above layout should then be implemented using the same function/button regardless of traction, in each operating country. In the past there has been no consistency of button functionality. How are we expected to learn not only a new traction, but also a new set of button functions for each released traction. This approach would make life a whole lot easier for the DTG dev's.

 

When did you record your videos?

I have just spotted this line in the Patch Notes. This should have come into effect after the patch installed yesterday. Unfortunately I will not be on TSW5 until Saturday to test this out.

• Localisation improvements for raildriver controls across all stock

 

I took the footage post patch this morning. I was also curious about that line in the patch notes, which is why I started recording to see if it changed anything, but unfortunately, that seems to have not been the case.


I ended up submitting another support ticket with those two clips included along with a link to this thread, and I got a non automated response from a DTG employee saying they were fully aware of this thread and the problems with the Raildriver. Maybe it was a PR response, but it seems like they are at the very least, aware it's an issue and know of the existence of this thread.


Maybe more people can open up a few more support tickets and share their own clips within those tickets, so they can be aware of how widespread the problem is and maybe increase the priority for it.

 

I have to ask did they test their fix in game??

 

That is a good question? I would suspect not, it's only been A month since the release of TSW5, and I'm sure they have been working none stop to get the next [DLC MBTA "I may have missed where they stated who is the DEV team DTG?"] out the door, which makes one wonder where and how they had the time for all these patches.

 

Posting one last example here because they've closed my support ticket. This is probably the most egregious example of how annoying this bug is. Leaving the Raildriver on a low throttle while operating the M9 is borderline unplayable. Hopefully this gets addressed very soon.

 

Took me a while to get this done and with a shared computer, it was late-night hours til the sun arose. You are not the first to report that a support ticket was closed, this is just another case showing that it is not something they at DTG care about.
A bit long and this was not intended to be so, but there was no other way to show what is happening.

 

I do get the ghost input notifications sometimes in TSW4, but way less frequent.

 

Needless to say, I got myself roped into an utterly useless childish tit-for-tat on Steam, but the other person did push me to reach out to PI Engineering. please see the attached image of the e-mail exchange between PI Engineering and I. So If anyone from DTG is reading this thread, which I would expect they are to some degree as well as the other threads and postings on the issue of the Raildriver. This is direct from PI Engineering/Xkeys I did remove names and private details.
--

With TSW4 I have not had anything like that happen. This includes on day-one release of TSW4

 

For some apparent reason today my Raildriver threw a wobbly and decided to do all sorts including buttons not working and got a case of the shakes on the Brake/Throttle and the Reverser. To get it back to anywhere near right I had to uninstall/reinstall the app. Now I am left with the shakes on the throttle/brake and reverser.
The sad thing is, is that because there was a line in the Patch information regarding Raildriver DTG think they have fixed it.
But, you have not.

 

That was localisation.

 

What was that supposed to do.

 

Localisation is basically translation.

 

Well…I still haven’t switched from TSW4 to TSW5 because of the reported RailDriver issues. However, with Preston-Carlisle having got a release date, there’s now a deadline. I won’t be missing out on that route, so if DTG still haven’t taken any action to address the issue by then, that’s when I find out whether I’m one of the (sounds like) fortunate few who don’t experience issues, or whether I’m one of the majority who do.

Has anyone heard any indications that DTG might have a fix by any chance?

 

None that I had heard of, and searching the general TSW thread or the announcements thread is just older posts.
There is complete silence from DTG on this issue as they have done with other major issues.
So at this point, IMHO is as if they just let go, and "hey the modding community" will figure out something.

 

I do not think that the modding community will be fixing Raildriver for DTG. If they were going to do it, we would have had a mod already. Cobraone cannot help. This is down to DTG I'm afraid.
Even with Cobraones app my lever controls shake like one of my Mom's jellies.
All joking aside, it would be really good if someone from DTG would respond.

 

You are correct, the only thing that I have found and use are the Raildriver mods for the German trains made by Roman72, but this still does not correct/fix the jiggly wiggle of the levers like the throttle and brakes. The program created by Cobraone is the one saving grace, for the time being, that seems to minimize and in some trains has stopped this hot mess.

It's not like they, DTG don't know of this and other threads talking of the Raildriver mess, I have seen someone jump in on a few other issues related to TSW5, are those issues deemed easier/less complex issues to deal with, and or they are having a time of it trying to figure out what is causing this mess with the Raildriver. And they feel like making any statements will put them in the hot seat and questioned even more so as to "Is it fixed yet" Well they are already in the hot seat already and this needs fixing and silence does not make for happy for happy camper gamers.

 

Is there a keyboard control for inserting and removing reverser lever?

 

Any and all keyboard control options are in the settings under controls. I noticed they are in alphabetical order.

 

In the Default_ButtonMapper file, there is Wipers Decrease command but no Wipers Increase command. There is no command for sitting in seats, going up and down ladders, etc. Is it possible for me to add these commands to the file? I built a train controller similar to Dave's Loco Controller.

 

Just read through the update to TSW5 released today.
There is no mention of Raildriver.
It would be very good if a member of the DTG team could provide at the very least an update of some kind.

 

Honestly, I'm not at all surprised, They actually don't have a clue what the problem is! "most likely?" Never mind how to fix it.
And this will stay like this til the Next iteration of TSW___

 

I drive the 1938 Tube stock and watch the lever jiggling and I just pretend it's one of the ghosts of the Underground trying to control the train

 

Sometimes ya just have to laugh...

 

After reading through Cobra's thread on his utility program, it seems like the Raildriver deadzone configurations data is stored in an .ini file inside the My Games folder in Documents, the same location where the Engine.ini file is located. Having opened both it and the TSW4 raildriver.ini file, it seems like the values differ slightly which might explain why we are getting much more twitchy behavior versus previous TSW titles. I don't have time at the moment to test it, but changing the values around and using TSW4's values might solve these issues. It would be interesting to see what any of you experience after this (make sure to backup the original file before messing with it).

 

Would be interested in hearing Cobraones thoughts on this, I did not think of looking at these values.

Spoiler: TSW5

[/Script/DTGComm.DTGCommRailDriverConfig]
Devices=(DevicePath="\\\\?\\hid#vid_05f3&pid_00d2#8&1535b36b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}",Calibration=((CalibrationPointValues=(0.278431,0.501961,0.511961)),(ControlIndex=1,CalibrationPointValues=(0.239216,0.513726,0.592157,0.843137)),(ControlIndex=2,CalibrationPointValues=(0.305882,0.411765,0.800000)),(ControlIndex=3,CalibrationPointValues=(0.239216,0.768628)),(ControlIndex=4,CalibrationPointValues=(0.643137,0.823529)),(ControlIndex=5,CalibrationPointValues=(0.400000,0.521569,0.733333)),(ControlIndex=6,CalibrationPointValues=(0.349020,0.509804,0.654902))))
Devices=(DevicePath="\\\\.\\TrainSimWorld",Calibration=((CalibrationPointValues=(0.000000,0.525490,0.541176)),(ControlIndex=1,CalibrationPointValues=(0.000000,0.447059,0.498039,1.000000)),(ControlIndex=2,CalibrationPointValues=(0.000000,0.141176,0.964706)),(ControlIndex=3,CalibrationPointValues=(0.003922,0.984314)),(ControlIndex=4,CalibrationPointValues=(0.000000,1.000000)),(ControlIndex=5,CalibrationPointValues=(0.039216,0.509804,0.956863)),(ControlIndex=6,CalibrationPointValues=(0.000000,0.486275,1.000000))))

Spoiler: TSW4

[/Script/DTGComm.DTGCommRailDriverConfig]
Devices=(DevicePath="\\\\?\\hid#vid_05f3&pid_00d2#8&1535b36b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}",Calibration=((CalibrationPointValues=(0.278431,0.494118,0.504118)),(ControlIndex=1,CalibrationPointValues=(0.235294,0.498039,0.592157,0.839216)),(ControlIndex=2,CalibrationPointValues=(0.313726,0.407843,0.803922)),(ControlIndex=3,CalibrationPointValues=(0.235294,0.752941)),(ControlIndex=4,CalibrationPointValues=(0.627451,0.819608)),(ControlIndex=5,CalibrationPointValues=(0.403922,0.541176,0.733333)),(ControlIndex=6,CalibrationPointValues=(0.352941,0.545098,0.650980))))
Devices=(DevicePath="\\\\.\\TrainSimWorld",Calibration=((CalibrationPointValues=(0.000000,0.010000,0.020000)),(ControlIndex=1,CalibrationPointValues=(0.000000,0.010000,0.020000,0.030000)),(ControlIndex=2,CalibrationPointValues=(0.000000,0.010000,0.020000)),(ControlIndex=3,CalibrationPointValues=(0.000000,0.010000)),(ControlIndex=4,CalibrationPointValues=(0.000000,0.010000)),(ControlIndex=5,CalibrationPointValues=(0.000000,0.010000,0.020000)),(ControlIndex=6,CalibrationPointValues=(0.000000,0.010000,0.020000))))

 

Just in case anyone hasn't stumbled upon it yet (it's mentioned on another thread, but it took me a while to come across it) this mod solves the issue of the RailDriver not working properly with the 87. With this mod it works perfectly.

Also - interestingly - it seems to solve the TSW5 lever-jiggling issue. I had none of it on the 87 (and some of the lever movements need to be quite precise on the power controller). I haven't tried it on other locos/units yet, but it says it works for:

Class 87
Class 87 IC
Class 47
Class 101
Class 08

 

A bit off topic, but the game Derail Valley recently implemented full rail driver controller support. Has anybody who owns the game had a chance to test it and see if their implementation features the jittery mess that is still present in TSW5? Absolutely shameful that there has been no mention of this on any of the roadmaps, but I guess I shouldn't be surprised considering they haven't mentioned implementing suspension on the TSW4 era trains either.

The Dovetail method of conducting business where they promise something to sell a product, and then completely ignore it so their consumers forget about it and flock towards the latest new DLC is still alive and well today.

 

I actually have not played Derail Valley in 6 to 8 months, if not more, I lost save games, the way they changed Freeroam and made it so you have to spend a fair amount of hours to unlock most of the locos, just so you can use them in Freeroam, after all these years, DV is still very lifeless "yes there are the sounds of wild life, and they added some farm animals, and cats". No AI traffic, it's still a single-track game world. Some mods are never updated, but that is the mod authors' choice, not the DV devs.

Well, I suspect DTG is trying to figure out how best to add suspension and not break more of the game, as it has done in TSW4 with a couple of German locos/routes you can't move faster than 2kph, and in another, you get to a point where speed is lost and can't make it up 1.5% grade?

Well, sometimes it sure seems like that is the case, and there is defining silence more often than not, they have corrected many aspects of the game, but they really should get a group of coders, devs to work out all the issues that have been around since the days of TSW2020 and TSW2.