Viseng Posted February 24, 2018 Share Posted February 24, 2018 Hi, Have just installed England + Popham scenery into P3d V4 but am getting huge number of empty, random content tiles in the scenery outside the popham coverage region. The popham region itself appears fine. I get about 30fps update rate. The tiles appear first to be dark blue plain "water" which then infill to random terrain when very close or underneath the a/c. I am used to seeing remote scenery changing of course, but never within a few metres of the a/c. In addition, some tiles, although adjacent to other similar tiles will have sections of motorway or major roads on them, adjacent to plain fields, so you get situations where traffic is depicted moving across a few grass fields then rejoining the motorway! So far i have played with changing all the settings for terrain resolution etc. as listed in the manual for popham and uk, but this has not affected the result. I have also disabled each orbx library in turn starting at the lowest until all libraries were disabled. As I enabled each library in turn, the area which had previously been "randomised" as described remained contiguous with other tiles providing a seamless landscape as you would expect, although visually appeared to be no different from the default autogen scenery in p3d. On enabling the lowest priority "EXT" library, the randomised terrain re-appeared. I could of course leave it like this, but then it would result in paying for a non-operational product in p3d. I suppose I should add that the same libraries work fine in FSX! Regards, Viseng. Link to comment Share on other sites More sharing options...
Nick Cooper Posted February 24, 2018 Share Posted February 24, 2018 Hello, welcome to the forums. Would you mind attaching a copy of C:\programdata\Lockheed Martin\Prepar3Dv4\scenery.cfg please? Link to comment Share on other sites More sharing options...
Viseng Posted February 25, 2018 Author Share Posted February 25, 2018 Hi Nick, thanks for replying so quickly. After posting this, I found the topic, so I followed this having first updated p3d to v4.2 and checked that it was basically working (but with same issue). So replacing the terrain.cfg with the default seems to have solved the problem. thanks Robert Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.