Track Generator
2 posters
Page 1 of 1
Track Generator
Hello again. After a false start on a Linux based system (about a year ago), I've put together a Windows 7 PC for my OpenBVE project. Having worked through Dennis Lance's excellent tutorials, and watched Dexter's well presented "Building with Dexter" video's, I've started on my own route project, Stratford to Honeybourne. I can see that there is a lot of work ahead ...
I've managed to work out answers to many questions, but one or two have me puzzled. I've created my track work using Track Generator 1.6.2. Two of my turnouts needed to be 50m long. TG creates such objects with a "switch length multiplier", which I set to 2. The result looks very fine. But when these get added to the route they disappear as the view point crosses them! i.e. they are visible as the train approaches, then vanish as the view point reaches 25m along. This happens in Route Viewer and also any OpenBVE version I've tried.
Any ideas for a solution?
Locomotion
I've managed to work out answers to many questions, but one or two have me puzzled. I've created my track work using Track Generator 1.6.2. Two of my turnouts needed to be 50m long. TG creates such objects with a "switch length multiplier", which I set to 2. The result looks very fine. But when these get added to the route they disappear as the view point crosses them! i.e. they are visible as the train approaches, then vanish as the view point reaches 25m along. This happens in Route Viewer and also any OpenBVE version I've tried.
Any ideas for a solution?
Locomotion
Locomotion- Posts : 30
Join date : 2015-05-28
Re: Track Generator
You need to add the following code to the start of your route:
Mode 0:
Let's assume you place your object at 150m.
openBVE works in 25m blocks.
Thus, our points object will be 'disposed' (vanish) when the front of the train passes 175m.
Not good in this case!
Mode 1:
Again, place the object at 150m.
When the object is loaded, it's total length is measured.
This is 50m, so it is added to 150m to give a vanishing point of 200m.
This time, the object is out of view when it is disposed
- Code:
Options.ObjectVisibility 1;
0: Legacy: An object is made invisible as soon as the end of the block which it resides in has been passed by the camera. This does not work well when turning the camera around. Self-intersecting track (e.g. loops) is not possible.
1: Track-based: An object is made invisible as soon as its end has been passed by the camera. This is measured in track positions. Self-intersecting track (e.g. loops) is not possible.
Mode 0:
Let's assume you place your object at 150m.
openBVE works in 25m blocks.
Thus, our points object will be 'disposed' (vanish) when the front of the train passes 175m.
Not good in this case!
Mode 1:
Again, place the object at 150m.
When the object is loaded, it's total length is measured.
This is 50m, so it is added to 150m to give a vanishing point of 200m.
This time, the object is out of view when it is disposed
Re: Track Generator
Thank you! That explains it.
I'm sure there will be more questions in future...
I'm sure there will be more questions in future...
Locomotion- Posts : 30
Join date : 2015-05-28
Similar topics
» Track position (Track namespace)
» Another Utility: Cylinder Generator
» Is it possible to add objects to a track?
» Landscape and Route Generator
» Platform Nameboard Generator: A Replacement
» Another Utility: Cylinder Generator
» Is it possible to add objects to a track?
» Landscape and Route Generator
» Platform Nameboard Generator: A Replacement
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum