• Our new ticketing site is now live! Using either this or the original site (both powered by TrainSplit) helps support the running of the forum with every ticket purchase! Find out more and ask any questions/give us feedback in this thread!

openbve

Status
Not open for further replies.

Adam_Harrison

Member
Joined
3 Aug 2009
Messages
208
Location
Hartlepool
how come there is other trains on the track which move? is there a way i can stop this it is really annoying.

thanks
 

Attachments

  • dd.png
    dd.png
    721 KB · Views: 36
Sponsor Post - registered members do not see these adverts; click here to register, or click here to log in
R

RailUK Forums

mbonwick

Established Member
Joined
26 Oct 2006
Messages
6,311
Location
Kendal
I think it must be to do with the .pretrain command which developers use to make signals stay red.
 

Tugzrule

Member
Joined
30 Jun 2009
Messages
129
Location
Carlisle
That used to happen to me on a much earlier version of openbve, dont think that anything can be done about it, but you could always report it to Michelle to see if she can do anything about it.
 

bengley

Established Member
Joined
18 May 2008
Messages
1,987
I don't see why you'd want to do that. You should never be able to catch up with the previous train.
 

bengley

Established Member
Joined
18 May 2008
Messages
1,987
Then that's a bug with that specific route. Try contacting the person who made the route.
 

eezypeazy

Member
Joined
4 Jul 2005
Messages
626
Location
UK
... which was me!

mbonwick is correct, the .pretrain command is used to make the signals change.

My Aln Valley route was written well before openBVE was even a twinkle in Michelle's eye, so there will probably be a number of issues when you try to drive it in openBVE.

I'll see if I can look at it this week.

Regards

eezypeazy
--- old post above --- --- new post below ---
... and, having looked at the route and asked a question over on Michelle's forum, the error was, as we suspected, down to my poor coding... I really must improve!

The problem was caused by using both .runinterval and .pretrain commands. The easiest solution for Adam (and anyone else) is to open each route in Notepad and remove the .runinterval 0 statement, which is quite near the top of the file.

But a reminder that this route was written some years ago, and there are transparency issues when running it in openBVE. I will address these later this year.

Regards

eezypeazy
 
Status
Not open for further replies.

Top