Issues with Route.RunInterval command
2 posters
Page 1 of 1
Issues with Route.RunInterval command
Hi,
In OpenBVE (version 1.7.3.1) I opened a route, which contains "Route.RunInterval 540; -420" command. Everything was okay, the train which should appear 540 seconds ahead of us, showed up properly, but the train which should appear 420 seconds behind us was not appear. Of course, I turned on the automatic control of the player train, after the loading, so the player train moved properly. Unfortunately, the train behind us did not show up at the initial station even 600 seconds later. However, instead of the train that should be appeared behind us, a train appeared 120 seconds ahead of us. I tried to look for it, but I did not find a "Route.RunInterval 120" or a "Train.Interval 120" commands anywhere. I found everything in the log file okay.
Would you look at these in the program code, please?
Thanks,
Andrew
In OpenBVE (version 1.7.3.1) I opened a route, which contains "Route.RunInterval 540; -420" command. Everything was okay, the train which should appear 540 seconds ahead of us, showed up properly, but the train which should appear 420 seconds behind us was not appear. Of course, I turned on the automatic control of the player train, after the loading, so the player train moved properly. Unfortunately, the train behind us did not show up at the initial station even 600 seconds later. However, instead of the train that should be appeared behind us, a train appeared 120 seconds ahead of us. I tried to look for it, but I did not find a "Route.RunInterval 120" or a "Train.Interval 120" commands anywhere. I found everything in the log file okay.
Would you look at these in the program code, please?
Thanks,
Andrew
Gothpaladinus likes this post
Re: Issues with Route.RunInterval command
Fixed in today's daily build, my apologies.
(You can also turn off hacks to tempoarily fix the issue)
TLDR:
With hacks enabled, we check for a *minimum* RunInterval of two minutes.
This is because otherwise in a large number of BVE2 routes you get a train blocking the initial section and causing havoc.
Unfortunately, I overlooked negative values in this (they're not widely used), and so any negative value got 'fixed' to 120s.
(You can also turn off hacks to tempoarily fix the issue)
TLDR:
With hacks enabled, we check for a *minimum* RunInterval of two minutes.
This is because otherwise in a large number of BVE2 routes you get a train blocking the initial section and causing havoc.
Unfortunately, I overlooked negative values in this (they're not widely used), and so any negative value got 'fixed' to 120s.
Gothpaladinus and BPI-919 Andris like this post
Similar topics
» Strange warning: The command Route.TFOXML is not supported
» Cannot load a route, fails with "The selected route is corrupt: No objects defined."
» Transparency issues
» TrainEditor2 issues
» Object brightness issues
» Cannot load a route, fails with "The selected route is corrupt: No objects defined."
» Transparency issues
» TrainEditor2 issues
» Object brightness issues
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|