Dorset coast v6 - Severe trees on tracks
#1
Posted 29 November 2015 - 08:54 AM
Reading the post on here and other forums, the slightest touch of red boundary boxes on the track causes this problem.
I have a couple of questions before i attempt this mammoth task of editing and adjusting the forest boundaries in RE.
1. Waiting for OR to fix this problem ?, if it can be fixed!
2. Is there a function in Route riter that could adjust all the Forest tree boundaries slightly smaller ?
3. A quicker way of adjusting the forest boundaries other than manual adjustment in RE ?.
4. Any other methods or ideas ?
Thanks
#2
Posted 29 November 2015 - 09:05 AM
#3
Posted 29 November 2015 - 11:57 AM
#4
Posted 30 November 2015 - 05:45 AM
Genma Saotome, on 29 November 2015 - 11:57 AM, said:
Okay, so no possible fix in the near future?
Looks like i can now start the tedious and time consuming task of adjusting the forest red boxes in RE?
Thanks
#5
Posted 30 November 2015 - 09:50 AM
#6
Posted 30 November 2015 - 12:10 PM
I will try to find the mod in my \global folder and at least post info that you can search the trainsim,com site and get the mod.
Ahh ... found it. Looks like it's a 'stretched' default forest marker ... Y axis ir +-25 meters above / below shape pivot. Easy mod if you have Shape Manger. (avail in trainsim file library and I think, Steam4Me.
Just stretch that \global\forestmarker.s shape or find erics post on the subject and in the RE, forest region handles will show up loud and clear. Click on the handle you want to move.
:unclesam:A WORD OF CAUTION!
When in the Route Editor if EVER you mistakenly select a track or road section IMMEDIATELY deselect the road or track section and exit the editor without saving.
If you exit the editor with a track or road selected you WILL corrupt the Track Database file.
Make sure NOTHING shows selected in the Editor Object Window when you exit!! . . . . [emphasis added]
After exit just reload the editor and continue with your Forest management.:clapping:
You'll have no problems if you follow this bit of advice.
It is probably a good idea to make a quick route.zip or route.rar compressed file as a backup for the route undergoing the 'forest management' yes?
regards,
vince
#7
Posted 30 November 2015 - 12:47 PM
I am trying to revisit what jtang developed more than two years ago, but at the moment either I don't understand how the code works, or the code doesn't work. I'm not sure I'll arrive at a working result. Simply slightly reducing the forests' size is not a solution, as there are many cases where the forest spans across the tracks.
#8
Posted 30 November 2015 - 01:11 PM
Csantucci, on 30 November 2015 - 12:47 PM, said:
I am trying to revisit what jtang developed more than two years ago, but at the moment either I don't understand how the code works, or the code doesn't work. I'm not sure I'll arrive at a working result. Simply slightly reducing the forests' size is not a solution, as there are many cases where the forest spans across the tracks.
There are probably two workable solutions to this for OR (i.e. without content changes):
- Calculate the collisions between trees and tracks brute-force but cache the results, so only the first load is slow.
- Attempt to optimise the collision calculations so it is acceptable to run on every load, but maybe less accurate?
I don't remember how much the code was brute-force vs optimised, though I feel it was more the former.
Maybe if you can bring that back to life behind an option, someone can look at optimising it? ISTR we more or less just took it out because it was slow without much effort, although I have concerns on how much it can be optimised.
#9
Posted 03 December 2015 - 11:56 PM
#10
Posted 04 December 2015 - 12:17 AM
But it really isn't that hard to do. I just keep a list of the ones I've found, noting how many telegraph poles east or west of MP such-and-such it is then go in to the various routes I have made notes on, bring up AE and find the coordinates of the nearest MP then bring up the routes in RE and move 'em.
For my money (pretty lame statement for a free software!), I'd be happy if you'd just adjust the lat/long to match MSTS so you could more easily find things.....:bigboss: