Atomic Systems

Hi guys,

Just got my new cab controller through the post and set it all up accordingly. Now I'm trying to use this with various stock with varying results. Is it not compatible with certain trains that use other physics rather than the default? Such as the AP Class 142, as it doesn't recognise it at all. The few trains that do recognise it all have the same issue however, the AWS reset button leaves the actual AWS button pushed in and the only way to release it is to press 'Q' on the keyboard, pretty pointless, I've tried playing with the macro in MW3 but not had any luck, anyone have any suggestions? I'm sure it is only me doing it wrong!

Not all that happy with the unit currently, I think it has made the overall experience worse!

Sam.

My unit does not do that at all, but I'm not technical enough to tell you why, I'm afraid.

Make sure you have the latest drivers and such from the PI web site...

Thanks for the reply, the website seems to be down at the minute so I cannot check that I do have the latest drivers as the ones I found were from a direct link and I'm not sure if they are right! Hope their site gets fixed soon!

We also bought one recently to try and add 142 functionality.
I also noticed the AWS reset button got stuck down,
The easiest way to fix it is to open the macro program and change the mapping of the AWS button from the function it is currently assigned (AleterReset, I think) to a keyboard commandof "Q"
Problem solved

Dave

DaveDewhurst wrote:We also bought one recently to try and add 142 functionality.
I also noticed the AWS reset button got stuck down,
The easiest way to fix it is to open the macro program and change the mapping of the AWS button from the function it is currently assigned (AleterReset, I think) to a keyboard commandof "Q"
Problem solved

Dave

That sounds very promising! Would you be able to send me the most current rail driver drivers as the PI website is down! Thanks

I havent got a copy of the MW3 program but you can have my script.
It needs to be placed
..Users\USERNAME\AppData\Local\PI Engineering\MacroWorks 3\MyScripts\RailDriver\

It also includes a fix for the sporadic issue of the speed display switching between mph/kph without input and a modification to allow trains with combined throttle/dynamic brake AND a loco brake to work correctly

Just tried to attach it to this post and every extension (.mw3, .rar, .txt is disallowed), PM me your email address and I'll send it over

Dave

DaveDewhurst wrote:I havent got a copy of the MW3 program but you can have my script.
It needs to be placed
..Users\USERNAME\AppData\Local\PI Engineering\MacroWorks 3\MyScripts\RailDriver\

It also includes a fix for the sporadic issue of the speed display switching between mph/kph without input and a modification to allow trains with combined throttle/dynamic brake AND a loco brake to work correctly

Just tried to attach it to this post and every extension (.mw3, .rar, .txt is disallowed), PM me your email address and I'll send it over

Dave

Huge thanks Dave, it works perfectly! Keep me posted on that 142 situation, I'd love it to be compatible!

Regards
Sam.

Just posting as this is the most recent thread about the Raildriver.

Has anyone noticed the Isle of Wight units no longer seem to work? I'm sure they used to on previous versions of either macroworks or RW. Now the throttle doesn't work at all, yet everything else appears fine.. any idea? It's not like its a complex throttle :|

@DaveDewhurst - would it be possible to place a copy of that script someplace? Like the file library? I'd like to try it also.

If the script is not too long maybe just past into a code section as below:
Just use {code}{/code} but replace my curly brackets with square ones.

RD throttle not working is usually down to the engine script updating the throttle every tick, rather than just when it thinks the value should change - it takes maybe 3 extra lines to deal with that but there's many DLC that don't. Brakes is a little more complex as occasionally you'll get someone who's set the built-in brake controller up peculiarily and then done all the rest of the brakes in Lua - as RD just ignores lua ( good eh? ) then it'll be driving the "odd" brake setup.

Might try using it with the joystick driver if you can - that looks sufficiently configurable that you can make full use of all this custom programming we do. I've made my racing pedals work with AutoHotKey before ( quite amusing driving a train with a brake pedal! ), there are a few solutions.

Kariban wrote:RD throttle not working is usually down to the engine script updating the throttle every tick, rather than just when it thinks the value should change - it takes maybe 3 extra lines to deal with that but there's many DLC that don't. Brakes is a little more complex as occasionally you'll get someone who's set the built-in brake controller up peculiarily and then done all the rest of the brakes in Lua - as RD just ignores lua ( good eh? ) then it'll be driving the "odd" brake setup.

Might try using it with the joystick driver if you can - that looks sufficiently configurable that you can make full use of all this custom programming we do. I've made my racing pedals work with AutoHotKey before ( quite amusing driving a train with a brake pedal! ), there are a few solutions.

So can you use the joystick driver with the RD?

I don't understand why suddenly the Isle of Wight units won't respond to the thottle, i'm sure they did before. Not sure what changed, TS or the RD drivers :|

I'd also like to see this script people speak of please

David

I don't have a RD - I just do my best to keep everything at least minimally compatible - but I did understand that it showed up as a game controller; if it does then there's a good chance that it'd work with the joystick driver ( and anything else that can read windows game controllers ).

I don't quite understand why 2013 used some xbox API for gamepads instead of just using the existing game controller interface, but there you go.

Hi Kariban
That's the point the RD does NOT show up as a game controller in windows so it can't be "programmed" like a joystick can. If you use a joystick with RW3 then you need to use a program like Xpadder or software from Pinnacle Game studios or some freeware script here on UKTS for the controller to work optimally.
Neither XPadder or Pinnacle recognise the raildriver as a game controller - that's why it RD uses its own script to interact with TS2013.
The logitech G13 (which is a keyboard type game pad) works seamlessly in RW3 and having 3 "memory" areas you can program keystrokes for differenet locos eg the VR de Br 143 which uses non-standard keystrokes.
Even though TS 2013 is now XBox 360 compatible some locos eg the Class 156 don't have full functionality - in this case pressing the brake lever on the gamepad results in the brake going from 0% to 100% with nothing in between.
TSX may interact with the RD commands as it seems to operate better in non-TSX mode but that may vary PC to PC.
pH

Very unfortunate then ( also utterly daft! ) - other than writing your own windows RD driver that converted it to a normal game controller ( of course then you need to use the joystick driver from here on top of that ), not much anyone can really do then.

Given what a raildriver does is no different to any other game controller, I reckon actually producing a driver probably isn't very hard. I suspect the available & willing percent of the population to do that is miniscule, though.