Changing services in free roam scenarios

[NickF]

Are there limitations on changing from one loco to another in free roam? I seem to be having inconsistancies with this.

As an example (I just chose this as one example; I've had it else where, so I know it's not the route or scenario.)

Last night I was playing the freem roam at Kleeburn(?) on the BN bighorn. I was driving the 2-unit lashup of SD40's, assembling and loading three individual strings of coal hoppers into one train. On the siding across from the yard tracks is another SD40. When I started out, I could switch to this other unit with no problems. I did this several times, jumping back and forth from one train to the other and doing switching operations with both.

I spent a fair amount of time loading coal into the assembled unit coal train I'd created. Finally I planned to add the single SD40 to the rear of the train as a helper, but I couldn't access it anymore.

Anybody have any idea why not? I've seen this in several other situations as well. At first I can switch trains; then I can't.

[dieseldown]

This happens all the time with me, but I have no clue as to why. To get around this I set up a 'view' where both trains or engines are close, then I save the scenario and quit and restart or Continue the scenario. When it comes active the 1st thing I do is click on the engine or train I want to jump to and this has always worked.
Good luck, Paul

[Machinist]

Hi Nick,

It never hapenned to me in "free-roam" scenarios, but only in "standart" scenarios instead in which are many driveable engines but none is assigned as "player" train. This is why even in a standart scenario (remarking: with no "player" train) you can jump forth and back from one train to other (like in a free-roam scenario), however when you are driving a (say) Train A and couple to it a Train B, this Train B loose its independency and can't be driven anymore; even after you decouple B from A, only A remains driveable. Something like that...

Doc.