Railworks America

Is there a way somehow you can disable the T key while in build mode. I hit it a few times and it gets really annoying going back and releveling again.

Hi, search for a thread regarding "shift + t" on the UKTrainSim forums. You can re-map 'T' to 'Shift + T'.

I'll look again. But I looked for like 10 minutes and didn't find anything. Anyone know link?

Using AutoHotKeys, I whipped up a little script for you (I will use this script myself while doing some route-building too, as few times I've also fallen victim of the dreaded accidental pressing the T key mistake, luckily I had recent back-up of my work, so I didn't lose too much, but, it's still a hassle when it happens).

Here's the download link:
http://www.rryard.com/files/T_to_F9.zip

Un-zip the downloaded file. You'll find a "T_to_F9.exe" self-contained executable file which will run the simple script.
Run it before launching RailWorks. It takes very little memory to run. You'll notice an icon appear in your system-tray to indicate it's running.

The script swaps-around the T and the F9 keys. I chose the F9 key in this case as it's not used for any function in RailWorks (as far as I know), and figured it was probably far-enough away from other keys you might typically be using to avoid accidentally pressing it. If you still for some reason want to use the "T" key, then simply press your "F9" key while this script is running. And, if for some reason, you need to use the F9 key, then pressing your "T" will be the same as pressing "F9", but of course, the "F9" key doesn't do anything in RailWorks (to my knowledge), so voila, accidental pressing of the T key won't mess up your work while route-building.

Once you close RailWorks and want to close the script, simply right-click on the script-icon in your system-tray, then select the "Exit" option. That's it!
Hope that helps.

LoneWolfDon wrote:Using AutoHotKeys, I whipped up a little script for you (I will use this script myself while doing some route-building too, as few times I've also fallen victim of the dreaded accidental pressing the T key mistake, luckily I had recent back-up of my work, so I didn't lose too much, but, it's still a hassle when it happens).

Here's the download link:
http://www.rryard.com/files/T_to_F9.zip

Un-zip the downloaded file. You'll find a "T_to_F9.exe" self-contained executable file which will run the simple script.
Run it before launching RailWorks. It takes very little memory to run. You'll notice an icon appear in your system-tray to indicate it's running.

The script swaps-around the T and the F9 keys. I chose the F9 key in this case as it's not used for any function in RailWorks (as far as I know), and figured it was probably far-enough away from other keys you might typically be using to avoid accidentally pressing it. If you still for some reason want to use the "T" key, then simply press your "F9" key while this script is running. And, if for some reason, you need to use the F9 key, then pressing your "T" will be the same as pressing "F9", but of course, the "F9" key doesn't do anything in RailWorks (to my knowledge), so voila, accidental pressing of the T key won't mess up your work while route-building.

Once you close RailWorks and want to close the script, simply right-click on the script-icon in your system-tray, then select the "Exit" option. That's it!
Hope that helps.

Yes this is good. A questions; will this cause trouble with FRAPS? Which uses the F9 key?

kin3 wrote:Will this cause trouble with FRAPS? Which uses the F9 key?

You can always change which key FRAPS uses.

Thanks, anybody who has created a giant hole will appreciate this.

Right, I wasn't thinking about FRAPS, but, as TrainGuy mentioned, you can simply change the F9 key used in FRAPS to another key of your choice, or, with the script running, just remember that pressing "T" should be the same as pressing F9.

Or, if you guys prefer a different key I swap it around with, let me know. But, like I mentioned, I chose F9 because I don't recall it being used for anything in RailWorks and it's probably far away enough from other keys you might use in RailWorks to help avoid accidentally pressing it.

Cheers!

A better method may be to edit the C:\Program Files\Steam\steamapps\common\railworks\Assets\Kuju\RailSimulatorCore\InputMappers\Editor Mode.bin input mapper to reference a different key other than t.


<iInputMapper-cInputMapEntry d:id="19245016">
<State d:type="sInt32">0</State>
<Device d:type="cDeltaString">Keyboard</Device>
<ButtonState d:type="cDeltaString">ButtonDown</ButtonState>
<Button d:type="cDeltaString">Key_T</Button>
<ShiftButton d:type="cDeltaString">NoShift</ShiftButton>
<Axis d:type="cDeltaString">NoAxis</Axis>
<Name d:type="cDeltaString">EditExportTerrain</Name>
<Parameter d:type="cDeltaString"></Parameter>
<NewState d:type="sInt32">0</NewState>
</iInputMapper-cInputMapEntry>

Although, if you do you should make a back up copy of the revised version so you can just paste it back into the folder if RW ever over writes it.

Yep. But, probably not everyone wants to get into fiddling around with the core files of RailWorks, plus, as suggested, if one does a Verify integrity, or if RailWorks does an update, then any changes like that could be overwritten anyways.

But still, it's good for people to have different options and can choose what they feel best suits them.

Cheers!