Can anyone explain why forest regions behave like this when over-lapped with each other in Open Rails? Shots are both from the recent freeware Donner Pass, and payware Sherman Hill.
Grey textures happen when you're running out of memory, and I suspect trees are some of the last items drawn.
Does it happen if you dial back to 2000m visibility?
If you like what you see here at Trainsim.com, be it the discussions and knowledge in the forums, or items available in our library, I hope you'll consider a paid membership to help support keeping the site operating.... Thanks!
That is odd, i have been almost constantly running up and down end to end tracks 1,2 and 3 on Sherman hill in OR and have never seen that happen to the trees once and i only have a GTX250. those shots look like the middle section of track 3 as its about the only place at the moment with that ammount of trees on it.
i have distance set to 4000 mtrs and distant mountains as well as ticked the load object max view to horizon.
you have a better processor than me an i7 mines an i5 but i am using a Sound blaster card rather than onboard sound, may or may not have anything to do with it.
Okay, upgraded Nvidia driver to latest (published 6/22), no change.
Changed all my options for distance, unchecked LAA, tinkered with the works, no difference, EXCEPT
When I put object density down to 0, all the other scenery item vanish completely except the problematic forest regions. While remaining, they are different in that the trees drop down to a single 2-sided flat pane from the 6 (or 8?) sided multi-pane, not sure how Marc did his trees. Only thing left to do is delete and re-add the forest regions in question to see what happens, or completely remove this install of Open Rails and download a fresh copy again, as sometimes the updater has bombed in the past, usually waiting until the next week when it works. Can anybody tell me what needs to go, hidden files or registry wise?
I will say that I noticed the problem on the NWP route a few months ago, but at the time I shrugged it off as a route-specific texture issue or whatever, and I really didn't investigate it. As these new routes have come out, freeware Donner first, they have all been afflicted. Point being there have been plenty of Microsoft updates in the last 3 months so I doubt that is a related issue.
Does it happen with the stable V1 release of OR rather than with the updates added, i am only running the V1 stable release, i just made a complete run over track 3 since my previous post with a 2615 foot 3800ton consist and i paid particular attention at the point where all the forests are and saw no probs whatsoever. i never update my Nvidia drivers, after installing from the CD that comes with the card as i found in the past that they often got worse with updated drivers. especially ones offered with microsoft updates.
this is just one of many shots i took while traverring that section
A cleaning of hidden folders and registry entries combined with a fresh install of the experimental solved the problem. Evidently caused by an updater failure months ago.
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