Hi Folks,
Re: Conversation on Elvas (http://www.elvastower.com/forums/ind...g/page__st__10)
Just wanted to add people here in the loop - over on Elvas we started a discussion with a developer to redesign the Train HUD [F5] - this pertains only to the Train HUD [F5] and not the Debug HUDs [Alt F5]... He already has some working examples posted over there...
A couple more thoughts - let's make the Train HUD - the Train HUD - and remove information that doesn't pertain to actually "driving" a train...
I'm a minimalist - while we need the information - we need it compact, concise, and as unobtrusive as possible - how about something like this ?
(19 characters wide in example)
Deletions:
Using Carlo's Example of Electrics:
Four letter identifiers should be more than sufficient to get the point across for any value and would probably only take a few minutes to get used to... It also keeps everything aligned nicely which helps get the needed information to the user as quickly and efficiently as possible...
The developer is making an option in the settings to slect "full text" or "abbreviated text" in the settings so you can decide how much screen real estate to sacrifice to the "Train HUD"
The multiline train brake string seems to make it more "readable" to me vs the single line long string...
I think if we implemented something like what's listed above - in a window with tinted background - it may pretty much negate the need for control confirmations... The whole reason we needed "Control Confirmations" was the HUD was so difficult to see... Perhaps we could (one or more of the following) highlight/blink/bold/underline the actual value being actively changed by the user for a few seconds - in the HUD - as a new control confirmation - to immediately draw your eye to the value being modified ? This would eliminate the redundancy of control confirmations and the additional screen clutter that comes with it... This will also free up the key (in short supply) to blank "Control Confirmations" for PIX or VIDS - as you can simply close the HUD...
If there's any interest - I'll certainly make Steam and Diesel examples as well...
Very happy the HUD is finally getting some much needed and deserved TLC - please don't give up on us - Mauricio...
Attached is my vision of what the new Steam HUD should look like - doing similar for Diesels and Electrics... The highlighted label (magenta) - indicates the control has just been moved by the operator and should stay magenta for a similar time period that Control Confirmations remain visible - with the end goal of removing Control Confirmations entirely...
Since this will affect us all - you might want to take this opportunity to get your two cents in - with ideas, agreement, and/or objections... I'm not the developer and I'm merely making suggestions...
Regards,
Scott
Re: Conversation on Elvas (http://www.elvastower.com/forums/ind...g/page__st__10)
Just wanted to add people here in the loop - over on Elvas we started a discussion with a developer to redesign the Train HUD [F5] - this pertains only to the Train HUD [F5] and not the Debug HUDs [Alt F5]... He already has some working examples posted over there...
A couple more thoughts - let's make the Train HUD - the Train HUD - and remove information that doesn't pertain to actually "driving" a train...
I'm a minimalist - while we need the information - we need it compact, concise, and as unobtrusive as possible - how about something like this ?
(19 characters wide in example)
Code:
TRAIN HUD
----------------------
TIME: 12:00:55
SPED: 0,0 kph
THRO: 0%
DIRC: N
BTRN: Serv 41% EQ60
FOT BC30/BP60
EOT BC30/BP60
BLOC: 0%
BDYN: 0%
PANT: Down/Down
CIRC: Open
POWR: Off
----------------------
Deletions:
- We don't need the software version staring us in the face - all the time - available elsewhere.
- Gradient is already on the Track Monitor.
- FPS - get it some other way - tends to be more of a distraction anyway - move to DEBUG HUDS ?
- Multiplayer - do something else for the probably relatively few that use this feature - "Multiplayer HUD" ?
Using Carlo's Example of Electrics:
- SPED = Speed
- THRO = Throttle
- DIRC = Reverser or Direction
- BTRN = Brakes Train
- _FOT = Front Of Train
- _EOT = End Of Train
- BLOC = Brakes Locomotive
- BDYN = Brakes Dynamic
- PANT = Pantographs
- CIRC = Circuit Breakers
- POWR = Power
Four letter identifiers should be more than sufficient to get the point across for any value and would probably only take a few minutes to get used to... It also keeps everything aligned nicely which helps get the needed information to the user as quickly and efficiently as possible...
The developer is making an option in the settings to slect "full text" or "abbreviated text" in the settings so you can decide how much screen real estate to sacrifice to the "Train HUD"
The multiline train brake string seems to make it more "readable" to me vs the single line long string...
I think if we implemented something like what's listed above - in a window with tinted background - it may pretty much negate the need for control confirmations... The whole reason we needed "Control Confirmations" was the HUD was so difficult to see... Perhaps we could (one or more of the following) highlight/blink/bold/underline the actual value being actively changed by the user for a few seconds - in the HUD - as a new control confirmation - to immediately draw your eye to the value being modified ? This would eliminate the redundancy of control confirmations and the additional screen clutter that comes with it... This will also free up the key (in short supply) to blank "Control Confirmations" for PIX or VIDS - as you can simply close the HUD...
If there's any interest - I'll certainly make Steam and Diesel examples as well...
Very happy the HUD is finally getting some much needed and deserved TLC - please don't give up on us - Mauricio...
Attached is my vision of what the new Steam HUD should look like - doing similar for Diesels and Electrics... The highlighted label (magenta) - indicates the control has just been moved by the operator and should stay magenta for a similar time period that Control Confirmations remain visible - with the end goal of removing Control Confirmations entirely...
Since this will affect us all - you might want to take this opportunity to get your two cents in - with ideas, agreement, and/or objections... I'm not the developer and I'm merely making suggestions...
Regards,
Scott














Comment