I've been experimenting with generating distant mountains (DM) and found that much depends on how much standard terrain (ST) is present in the route. I'm working on a Southern California area where you're surrounded by mountains, and after initially generating DM, I noted that some mountains I expected to be there weren't, and peaks of those that were there were flickering horribly. Flying out to the affected areas I noted that no ST were present, nor should there be under normal conditions, as the area was far from any track.Varney wrote:The flickering starts about 15 miles out of Blackfoot, the video is at about 11 miles.
To see what would happen, I imported 19 x 19 ST around the perimeter of my route, returned to the route origin and then regenerated DM. Straight away there was an improvement in draw quality, and only a few areas flickered. I then ran out to those areas, imported more ST, and then repeated the DM generation (the more ST in the route, the longer the time spent generating DM). The final step was to remove my previously imported ST so as not to take up too much disk space (moved to a temp folder so as not to have to do it all over again if necessary). Thus far, all surrounding mountains are fairly smooth, but not yet totally flicker-free. I think a few more tweaks are needed, but everything's looking much better.
One way though that I can see improvement by RSC is to have the DM draw on both sides. This way, the backside of the mountain would display if there was flickering on the top face. IMHO with the DM so far away, I doubt anyone would notice if the backs of hills were drawn through the terrain tears - better that than having the tops of mountains dancing like a jumping bean!
