Notice to all visitors and members of the Train-Sim.Com message forums: If you plan on using a signature banner in your posts, we would like to remind you that there is a maximum size for banners. That maximum is 450 pixels wide by 120 pixels high, and not to exceed 25k. Your compliance is appreciated. FORUM RULES Problems? There are two common reasons for problems with logging in and posting messages. The first is that you are running a firewall that prevents your messages from being sent to the server. The other is that you have cookies disabled; the DCForum software requires cookies to work properly.
A good engineer checks his speedometer by running at a constant speed -- like 30 or 60 MPH -- between known good mileposts and timing with his watch. This is easy to do in flat territory without much else going on. When I try to do this near the Philadelphia end of the NEC (both the original and NEC 2), I get indications of substantial speedometer errors. Running from MP 4 to MP 14 with the speedometer holding near 30 MPH, for example, takes about 15 min and 53 secs, whether measured by the simulator clock or an external stop watch. Obviously, it should take 20 min exactly. 15:53 implies that the true speed was 37.78 MPH. Down at the south end of the corridor the errors are much smaller-- true speeds about 32 MPH versus indicated 30. I run the whole NEC with 2 Dash 9s and 37 chemicars in N1 (which cruise at an almost constant indicated 30 MPH) in 3.5 hours, while it should take 4.4 if the speedometer were true. Does anyone know what causes this problem or how to fix it? Could this distortion in the space-time continium have anything to do with the derailment problem?
In your DEFAULT Wag file in your trainset folder,you will see an entry "on track timestep" "10ms".If you alter to 2.5ms,this makes it more accurate speed wise.However it comes at a price.Lower frame rates,as you're(MSTS)spending four more times calculating the speed parameters than getting info to your monitor.You could change only for the route you're running,and change back to normal for another,as it seems route specific to a certain extent.Me?I just live with it I'm afraid.
I have a question. Whoever said that the milepost placement and the distance between them is accurate in MSTS? Prove to me that on a given MSTS route the mileposts are spaced at a simulated 5280 feet apart and then we can talk about speedometer accuracy.JKP you said A good engineer checks his speedometer by running at a constant speed -- like 30 or 60 MPH -- between known good mileposts and timing with his watch. So are those NEC mileposts known good mileposts? Just my two cents.PatchCrew UP Engineer
I tried changing "on track timestep" to 2.5 ms, but did not see any change in speedometer readings or timings between mileposts or frame rate (Nvidia Ti 500, 64 meg card at 1024x768 not working too hard anyway). Curiously, I did get three derailments in a row where I didn't get them before-- the switch just north of MP 14 heading south in NEC 2.Just measuring distances between mileposts on screen with a ruler in the Route Editor, it really looks like the distances are longer near Washington than they are near Philly.
