This is running ORMG95, haven't tried any newer versions yet.
Anybody else see anything like this?
https://youtu.be/6_Tsid3I9C8
https://youtu.be/OUUgMBoHVPM
OpenRailsLog.txt (12.17K)
Number of downloads: 168
Page 1 of 1
This is interesting Probably a route problem
#2
Posted 11 September 2021 - 10:29 AM
I had the same thing on one of the Polish routes, PSK I believe but don`t remember which version. But that was well over a year ago and I just reinstalled an older version of the route that I knew this wasn`t happening on.
Mark
Mark
#4
Posted 11 September 2021 - 12:01 PM
Powered up TSRE and found this.
Not sure how it runs at all.
Saved the run with the train stopped on the missing track DB entry.
Fixed it, started from the save and all is good.
Weird.
I might have Z'd it out when running terrain textures or fences or telephone poles or, who knows.
How would MSTS have handled this?
Ha!
Not sure how it runs at all.
Saved the run with the train stopped on the missing track DB entry.
Fixed it, started from the save and all is good.
Weird.
I might have Z'd it out when running terrain textures or fences or telephone poles or, who knows.
How would MSTS have handled this?
Ha!
#5
Posted 11 September 2021 - 12:46 PM
I've had vectors reverse before right at the end of a switch, which I once used to stand a -2 on end. If you remove the errant piece from the TDB and put it back in (which it sounds like you did), it'll fix itself. I suspect it's actually a TSRE bug, rather than OR, since I've actually watched it happen while laying track
#6
Posted 11 September 2021 - 01:28 PM
I just selected it then clicked on the adjacent piece and saved.
Every once in a while I'll remove the TDB lines to isolate a piece of track so I can auto place things/textures.
Sometimes I forget to turn it back on.
Since the route kept running I blew it off and forgot about it.
Every once in a while I'll remove the TDB lines to isolate a piece of track so I can auto place things/textures.
Sometimes I forget to turn it back on.
Since the route kept running I blew it off and forgot about it.
#7
Posted 11 September 2021 - 10:04 PM
ebnertra000, on 11 September 2021 - 12:46 PM, said:
I've had vectors reverse before right at the end of a switch, which I once used to stand a -2 on end. If you remove the errant piece from the TDB and put it back in (which it sounds like you did), it'll fix itself. I suspect it's actually a TSRE bug, rather than OR, since I've actually watched it happen while laying track
It's not a bug rather the way track vectors are handled in TSRE. Vectors are always numbered and computed in one direction. If you try laying track from 2 ends and join them in the middle, one end right next to the node will show this behavior
Likewise if you laid track in a certain direction, then went back and reworked it in the opposite direction
Page 1 of 1