I'm sure there are some good threads on this aspect of legacy control....I've just gotten started. My 1st observation is that it's not very accurate. When I replay a session, the final location is typically 1 or 2 cars 'off'. Is this normal?
Replies sorted oldest to newest
Yea it's normal. I have found the dcs version is about the same also.
The sensor track recording is very accurate. At the LUG meeting I had and engine bouncing back and forth on 3' of track without incident. The main thing, even with a Cab 2 recording, is the speed of the locomotive must be the same as when the recording was started when playback is initiated.
My initial speed was 0 mph. The replay stopped the train a foot shorter than it should have.....consistently & repeatedly. I'll try it again today.....
Was momentum the same? I'll try it today when I have time later. The sensor track recording because it is triggered by the locomotive going over a fixed point seems to do a pretty good job from what we seen at the LUG meeting.
Yes, same momentum. I merely re-position the engine to the same starting point & push RECORD to get the playback.
Phil
I got the same results. For me the engine is past the points when the action happens. The sensor track as I said seems to be more precise.
Marty: What do you mean by "sensor track"?
Soon to be released sensor track that works with Legacy engines that have the IR sensor on them. You can do a recording on them as well but it seems to be pretty precise on playback. We had one at the LUG meeting demo and had an engine going back and forth reliably for about 20 minutes.
I'm just started using the record function this week. I will have at least one engine go about ten inches off as well. Plus (I started a new thread but no one has commented) when I start the playback I will have one engine creep in reverse instead of going forward. That has me stumped as well! Anyone have that problem?
Rob W
Access to this requires an OGR Forum Supporting Membership
