Pretty every version of open rails for the last 2 years now. Whenever I restore a save game file. The speed between track monitor and engine is off by 10 or more mph. Even stopping the train and doing the ctrl shift x and alt x. Doesnt fix the problem. Train will look all jittery while moving forward. Was wondering if anyone has this problem? Or if there a option I overlooked. Thanks.
Physics problem when restoring save.
Collapse
X
-
Tags: None
-
-
OR LOG generated during one of these incidents would be helpful. It's not only warnings and other messages your log generates but also the settings you use ...so provide complete log.Cheers, Gerry
"A mind is like a parachute. It doesn't work if it is not open." Frank Zappa
It's my railroad and I'll do what I want! Historically accurate attitude of US Railroad Barons.
Forever, ridin' drag in railroad knowledge.
Audi, Vide, Tace, Si Vis Vivere In Pace
https://www.trainsim.com/forums/filedata/fetch?filedataid=79656&type=medium https://www.trainsim.com/forums/filedata/fetch?filedataid=79654&type=smallComment
-
Open Rails T 1.5.1-1345-ge5b84141d version. Not sure if what fork this would be.
Also log file attached.Attached FilesComment
-
I started noticing it too. Especially the speeds being very different from the F4 and F5 menus. Seems like we take one step forward and two steps back lately. Sigh.-Shawn K-
MEC Mountain Subdivision - Trackwork 70%, Scenery 35%
Comment
-
Comment
-
Don't get me wrong, I'm not trying to knock the devs here, it just gets frustrating when we have one issue fixed at one point, another issue gets fixed, but while fixing the second issue, the first issue sprouts up again needing another fix. It's honestly why I'm at the point of just making repaints for those that still enjoy running the sim, and working on my routes. I haven't been able to enjoy running the sim or creating activities in awhile because of these issues that get fixed and rehash with every new update. 🤷-Shawn K-
MEC Mountain Subdivision - Trackwork 70%, Scenery 35%
Comment
-
Shawn ----- Jason is using AutoSave with an interval of 15 seconds....are you using auto save also? I am not seeing the speed differential or the jitters --- I don't use auto save.
Jitters could be sound errors listed in log piling up....it's small, but I try to clear up all warnings and sound errors....probably nothing to do with the save problem.Cheers, Gerry
"A mind is like a parachute. It doesn't work if it is not open." Frank Zappa
It's my railroad and I'll do what I want! Historically accurate attitude of US Railroad Barons.
Forever, ridin' drag in railroad knowledge.
Audi, Vide, Tace, Si Vis Vivere In Pace
https://www.trainsim.com/forums/filedata/fetch?filedataid=79656&type=medium https://www.trainsim.com/forums/filedata/fetch?filedataid=79654&type=smallComment
-
I'll disable the auto save. See what happens. If not I'll just back date to a version this wasn't a issue in.Comment
-
I noticed the speed on the cab speedometer and the track monitor no longer match whenever there is a bad bout with wheel slip. Even if you get the slip under control, the speeds stay off, non-matching.
After I upgraded to 1435, I could no longer restore saves as young as 1417. I would presume something has changed that has required the breaking of many saves regardless of version.My Open Rails videos https://www.youtube.com/@lakecities3663/videosComment
-
Comment
-
Gerry, I don't run with auto save on. I haven't experienced the jitters, though I have noticed the train will sit there, and the wheels will be moving at mach speed, with the F4 showing 6mph and the F5 showing 7 or 8.
Shawn ----- Jason is using AutoSave with an interval of 15 seconds....are you using auto save also? I am not seeing the speed differential or the jitters --- I don't use auto save.
Jitters could be sound errors listed in log piling up....it's small, but I try to clear up all warnings and sound errors....probably nothing to do with the save problem.
Not all the time, but at various times. This of course is with 1.5.1. so I have no idea. Maybe it's always been there and I just never really noticed until recently due to just basically using ORTS to test my work real quick.-Shawn K-
MEC Mountain Subdivision - Trackwork 70%, Scenery 35%
Comment
-
Comment
-
Attached is a link to a video showing the problem probably better then I can describe it.
Comment
-
This was discussed back in August 2024 on Elvas Tower. ( https://www.elvastower.com/forums/in...page__st__2120 ). It has to do with models using advanced adhesion parameters. Also, the HUD F5, and TrackMonitor F4 compute speed differently. My understanding is that F4 is calculating actual track speed, while F5 is calculating wheel speed, including slippage. In my experiments, I found that the F4/F5 speed discrepancy would widen when the train was pulling hard upgrade, then narrow and/or disappear on a downgrade or level track. There may be an issue when restoring from a save when the speed discrepancy is occurring at the time that the activity was saved.Comment







Comment