campinge give me a DM, let's get you under NDA and on the beta programme, then you can access everything and help with feedback to make sure it runs the best it can, it's also easier to talk directly with the dev team and get answers to technical questions. The variation on the notch setup, as i've seen it, is that there is some variation in whether "input" or "output" positions define the notch. For those unaware - TSW has two lever position representations. The "input" is usually 0 to 1 and just matches the minimum and maximum extents. The "output" is range-mapped to something that makes more sense, and might map it to say -1 to 4 - if you have one step below zero, then four steps above it. But this input/output difference can be confusing, and the way notches are defined using an inconsistent (as far as I know ) mix of the two, doesn't help matters at all. In one loco - i think it's the 350, the *fixed* notches are defined with one, and the *continuous* positions are defined in another. Move on to test a different loco and now its all done on the inputs and another loco its another mix. I think ultimately it's down to the loco author who simply sets the notches up the way they feel most comfortable for the configuration they're trying to achieve. I have some code that is trying to make sense of it - my goal is to have a set of vibration motors which I'll attach to the TSC-X throttle handles, then as you move the throttle to a new "notch", it'll buzz the motor - giving you direct haptic feedback. My code is far from finished though, but happy to share notes - this is a personal project, nothing official. I've also been trying to make it work without any configuration needed - so it scans what controls are on the loco once it detects a new loco, and based on which ones it finds, i've got some rules set up so it can say "oh hey this is a two handle BR era loco, set it up like this" or "this is a german sbahn style pbc - set it up like this". Basics of this are working quite nicely but only on a limited configuration thus far, I want to get this notching stuff sorted before I spend more time anywhere else. Matt.
Hos the DTG Raildriver configuration been changed in a recent update - Yesterday everything was working well with Cobra One's TSE raildriver and JHoystick interface - but today TSW threw an Unreal crash on starting with that enabled - replaced the modified Pie DLL from Cobra's software and replaced it with the default and TSW strarted normally - Using the default Pie deel from DTG - it seems better but still has a bit of jitter - on the Meryygo round scenario throttle was jumping 2% and with the CLass 20's slow speed it was enough jitter where the throttle kepe juming out of slow speed to 4% and back - making the unloading a bit tedious
DTG Matt please also pay attention to locos with spring loaded levers like DB BR612 or TSG G6 for example. Current situation is that the lever notches back after 2 seconds or so even if you have the raildriver throttle at full position. To power the loco full up you have to change lever position back and forth an back and forth and ....
Those are going to need something else I think, not sure if the current interface can support controls that adjust themselves - but will add to the list of things to look for a solution to, several affected by it. Matt.
The jitter patch is what will bring me back into the game. Ever since TSW5 released that introduced it, using the RD has been a chore. Hopefully it is improved across all spectrum of trains, or at the very least how it functioned before TSW5.
Yeah I found there was a change made when the API went in which removed something inadvertently (simple logic mistake). Because the raildriver has very noisy potentiometers on the input levers, when you read values from it you dont get a single value even if the lever stays still - you get a bunch of wavering values in around the one you actually want. Which is what gives you the jitter. Depending on how well your potentiometers are doing, depends on how much jitter you experience in the raw data. Before TSW5 we had some code in there that required the lever to have moved more than a small amount before it would accept the new input as valid - which then smooths it out, at the cost of reducing the resolution of the lever a little. The change that went in flipped the logic on a surrounding test and that meant it no longer did the jitter removal for RailDriver. I've had that flipped back and in my tests it's much better (even on my 23 year old OG Rail Driver). I got beta team to test the change too, and they've reported positively. It's a core change that affects input reading of any lever from the raildriver, and is not train specific, so all trains are behaving better. Matt.
Music to my ears. Circling back to the original topic, I find that the Class 350 (along with all of its variants) is difficult to drive with the raildriver. The neutral throttle position feels too small, so I find myself going from B1 to P1 very frequently. Maybe the sensitivity patch will rectify this, but maybe increasing the neutral zone would help as well.
'I find that the Class 350 (along with all of its variants) is difficult to drive ' Try this mod for the 350, it works well for me. https://www.trainsimcommunity.com/m...ping-uk/f16797-rail-driverremapukclass350.pak
I'll give it a try, but it's better to fix the issue at its core because any of the future variants and the mod variants that use the base dependencies will run into the same issues.
Roman72 @ TSC fixed ALL the RailDriver issues for German Locos and made a wayyyyyyyyyyyyy better default profile (throttle pushing forward to accerelrate and backwards for dynamic brakes, brakes pushing forward to release and backward to apply, PZB with real "feeling" because of the switch used). --> https://www.trainsimcommunity.com/mods/c3-train-sim-world/c109-other/i6921-tsw6-raildriver-remapping Without his mods I'm not sure if I would have that much fun anymore. RailDriver is most important for me. The haptics are 100% more realistic and this is what keeps me coming back. He didn't make a profile for the Expert 145 and since then I try to reproduce his magic but was only able to get PZB working like he does. I need way more time and skill to dig into modding to get this done I guess ... Maybe contact him, I reached out many times but never got a response. I assume his handle here in the forums is Romansu72 Just my 2 cents ;-)
These are remappings building on Romans work, there's even one for the 145 expert https://www.trainsimcommunity.com/m...tions/i7676-tsw-rail-driver-remapping-germany
i have the TSC-X and so far i am happy i have not run into any new issues so far but there are loads and loads of trains to test so by far not done testing br 110 still skip a notch sometimes going from 6 to 8 for instance
I switched back to the DTG driver after using the the TSW Raildriver and joystick interface ever since tsw5 came out. Made several runs and have been pleased. The jittery is definitely gone on my Raildriver..
Just to give a short feedback since the last update, I dragged my raildriver out of retirement this afternoon as I wanted to drive the 390 and 800's and my other controllers don't cover the PBC. It's working much better with the latest update, no more fluttering between notches. Only issue I've had is the Emergency Brake applies every time I move beyond B5 on the 390. Maybe a calibration issue, but I can live with that. I have a PBC Pro from TS Controllers arriving soon and then the Raildriver will be put away for good, but the latest update is a big improvement for me.
