Forest objects not loading on startup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Open Rails |
Fix Released
|
Medium
|
James Ross |
Bug Description
1) Forests are not loading at the correct elevation in the original X tiles loaded on startup (I'm assuming nine; the starting tile plus one in each direction)
2) As soon as the camera moves beyond the original X tiles, forests are loading correctly on subsequent tiles, including fragments of forests which originated on one of the original X tiles
3) If I go 10-20 miles down the track, reverse direction and return to the starting point, the forests on those N starting tiles are loading properly
Discussion, screenshots and speculation at:
http://
I experienced on a custom route, as did Rob Roeter on a separate route.
Should be replicable on any route with forest objects...
Version 2334
World object density 10
Viewing distance 6000m
Distant mountains 40km
Extend object max viewing distance to horizon
Changed in or: | |
status: | In Progress → Fix Committed |
milestone: | none → 1.0 |
Changed in or: | |
status: | Fix Committed → Fix Released |
I could not reproduce this and the code looks like it should not really happen, but I have nevertheless attempted a fix for the theoretical problem of tile data not being loaded when the forests (and transfers) need it. Please let me know if X2379 works any better.