[R H Steele]

The situation
1. Activity is started, raildriver is engaged, activity runs and activity saved.
2. Activity is resumed from the save
3. If raildriver is not engaged when resuming, the keyboard throttle controls are locked out.
4. To regain throttle control you have no option but to use the raildriver again.

Is this by design, the way saves are managed by Open Rails? I like the raildriver, but the controls are sometimes not as precise as the keyboard, especially when needing small percentage control on braking and throttle.
I have tried this with various locomotives, including default Dash9, activities and routes - always occurs. It would be nice not to have the throttle control interface "locked" into the save. If when resuming, the Raildriver interface is not engaged then the keyboard interface throttle control is fully functional.

So when resuming from a save default control goes to the keyboard regardless of previous control interface. Only when raildriver is engaged does control move to it. Is that possible?