Pressing T Key by Mistake!

[AndyUK]

It's been said before but maybe worth repeating - edit the 'Editor Mode.bin' input mapper to replace the 'T' key with a combination of keys that are less likely to be pressed by mistake. That said a more obscure key combination by default would be a good idea.

Andy L

[transadelaide]

That said a more obscure key combination by default would be a good idea.

But what about the people who have to raise terrain over an entire route? Aren't they just as entitled to a little convenience as you, instead of having to use some obscure combination of keys so often?

[AndyUK]

Provided the key combination chosen isn't hard to use but is less prone to being hit by mistake I don't see anyone has to be put at a disadvantage. Would it be that hard for those needing to raise terrain over a whole route to use Shift + T for instance? I didn't.

Andy L

[gptech]

Those that want to alter the key or use a combination can, those that don't can leave it as it is; what is there to argue about?

[AndyUK]

I thought that if it was made less easy to flatten terrain by mistake the casual user or beginner who probably has no idea how to alter the key combination would be less likely to be put off route building and RW having spoiled their work, that's all.

Andy L

[gptech]

I agree with you, I'd rather have a combination of keys, and as you point out pressing 'shift' and 't' can easily be done with one hand so perhaps the answer is to have something like that as default, yet allow those who are that way inclined to edit it back to just 't' ?
Better documentation of this sort of feature is needed, the fact that there's nothing to tell 8 year old 'little Johnny' about the features/pitfalls in RW and the poor wee mite only finds out that doing 'x' causes a problem when it's too late is certainly going to put him off.

[transadelaide]

Better documentation of this sort of feature is needed, the fact that there's nothing to tell 8 year old 'little Johnny' about the features/pitfalls in RW and the poor wee mite only finds out that doing 'x' causes a problem when it's too late is certainly going to put him off.

The controls for the World Editor are already described in the RW Creator Manual. I don't think this is a 'poor little Johnny' issue.

[Acorncomputer]

RS.com are aware of this.

Note that there is - Improved terrain modelling and better import tool - included in TS2012.

[Wikkus]

The T key has to be the most insane feature of Railworks. Who thought it up I wonder? Why would you want to flatten your meticulously crafted terrain all in one go?

But the T key isn't used to flatten terrain, is it? I understood that its function was to create terrain using any DEM data you had loaded...? Therefore, if there's no DEM data, the net effect is to return the environment to sea level...? Or have I misunderstood?

Rik.

[rivimey]

Surely the actual problem here is that some people want to use T to apply DEM to the route - for which T isn't such a bad thing - and some people are creating their own scenery - in which case there's likely no DEM or the DEM that exists is inappropriate.

The solution from my POV is therefore to have a route-specific option that tells RW whether DEM data is appropriate. If it is, then you can apply DEM, if not then T does nothing (or, maybe, flashes an unobtrusive message saying that it's been disabled).

There is of course the issue that once DEM-based terrain has been raised route-builders do modify it; it would be nice if there was a way per tile to lock DEM application, so you can't accidentally / unknowingly undo that tweaking.

And if I'm on a wishlist, I would like it to be much clearer when about to press T exactly what I'm changing... perhaps T invokes a GUI mode in which a highlight square is displayed, decal-like, over the scenery and you can interactively fly out/around to check, then click on an Apply / Cancel button?

Regards
Ruth

[Kromaatikse]

Here's a radical idea - if there is no DEM file corresponding to the current tile, why not leave the terrain where it is rather than defaulting to sea level?

It's all about appropriate exception handling.

[Andysim555]

yea im also a victim of the T key. Its insane!! 99% of the time is not recoverable without a reload from saved. And if you didnt save you are screwed. The undo does never work for me.

Its like a button of doom.

I hope its all solved in TS2012.

[AndyUK]

Here's a radical idea - if there is no DEM file corresponding to the current tile, why not leave the terrain where it is rather than defaulting to sea level?...

Better, but if the DEM data was present wouldn't pressing 'T', by accident or design, still undo any terrain alteration since the DEM was first used?

Andy L

[Kromaatikse]

Yes, but that's a less drastic problem, and easy to solve by removing the DEM data once initially applied.