A lot of the time I think it's better to make a series of 25m scenes for the left and again for the right. They can then be used as freeobj, wall or dike, and if used in a cycle command will give a very good scenery variation. Adding a sprinkling of other freeobjs to these scenes really does make them all look unique.
I agree that 25m incriments, or to be precise I use 25.2m to avoid gaps appearing around the outside of curves, are far better. If you are using gradients at all then the BVE graphics leave gaps between sections as a result.This does not occur in walls and dikes.
However on flat ground then the cycle command can be used on grounds which is very handy as you can cycle through as many grounds as you want which has a very good effect on the route!
.Wall and .Dike commands are very similar to each other. .Wall is mostly used for objects the rise from tracklevel upwards. .Dike is the opposite, but it's not mandatory to use then this way. Really one of the two commands could be discontinued. But there are times when you need to use a .Wall command to run an object along by the side of the track. If you also want to run another object alongside the same track you can do it with a .Dike command.
The alternative would be to start another track - a hidden one, a null track - which would have to run at the same location as the first one. This is not always very satisfactory and by using .Dike as well as .Wall you can run two objects alongside the track and they will be independant of each other.
Thanks. I think I can understand the various commands, its just that sometimes I don't seem to have the imagination or creativity to use them to create good scenery.
There is a small but growing collection of public domain/freeware/open source objects starting to show up. At least one of our members is creating a collection site that may accessable soon.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We do not share information about our users with anyone. For additional details, refer to our Privacy Policy.
By clicking "I UNDERSTAND" below, you consent to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment