[R H Steele]

Is there a reason why some keyboard controls are locked out after using the raildriver? Once the raildriver is engaged for an activity, activity is saved then resumed some keyboard controls are inop, others are active. It seems a better solution that the keyboard is the default unless the raildriver is engaged (by using "raildriver run" blue button), once the raildriver is engaged any information is included in the save but not used unless the raildriver is engaged again after resuming. Once you've started using the raildriver for an activity you have no choice but to continue.

Answering my own question? ---- is it because of the continuous control interface?

[James Ross]

I don't know what information about the RailDriver we would need to save or why it would affect any keys. Which keys are you having problems with specifically?

[R H Steele]

James Ross, on 28 June 2014 - 01:44 AM, said:

I don't know what information about the RailDriver we would need to save or why it would affect any keys. Which keys are you having problems with specifically?

Throttle controls are locked out. Other basic controls appear fine. Did not try all the keystrokes, some I'm not familiar with.
Used default DASH9 (default consist) ran explore on the SLI BNSF Scenic Sub using X2319. Saved, exit, then resumed save, did not engage raildriver and throttle controls were inop.
(same situtation occurs when running activities regardless of locomotive or route)
Hopefully all that is affected are the throttle controls, best use would be to have all keys available for use unless the raildriver is engaged when resuming a save.

Attached File(s)

•  OpenRailsLog.txt (10.09K)
  Number of downloads: 160