MustangAce Posted January 15, 2012 Share Posted January 15, 2012 Today I was flying around KORS and I discovered a couple of mesh issues which I'd never seen before. The only things I've installed in FSX since I last flew in this are are the latest PNW patch, KBVS, 74S, JayCo, S43 and W52. I have my mesh at 5m as the KORS manual requests. The first issue is at the Clam Harbor strip. The airfield mesh appears to be bumped up above the surrounding terrain. Here are two screenshots with autogen disabled for clarity. I also enabled the position text up top in case that helps find the locations. The other issue may not be in the KORS scenery, but it's at least in PNW. If you take off from runway 34 and turn west out over the water, there is an island ahead with a grass strip on it with a static plane and house. Near each end of the runway there is an invisible "ditch" which gave me a rude surprise on landing and takeoff. I slewed my aircraft into each one and snapped a screenshot. If I moved up or down the runway several feet in either direction it pops back to the surface. Any suggestions on what I might try to eliminate these? I have no scenery anywhere near this part of the globe except Orbx and OZx on my FSX install. I fly into clam harbor fairly often and suspect that this happened after installing the latest PNW patch, but I don't know for certain. Link to comment Share on other sites More sharing options...
Heiko Glatthorn Posted January 17, 2012 Share Posted January 17, 2012 Hello, please make sure you have both PNW.004 and PNW.004a updates installed. The latest PNW.004a alone won't be enough since it is a smaller update to PNW.004. Please let me know how if the problem is fixed by first installing 004 and then 004a afterward. Link to comment Share on other sites More sharing options...
MustangAce Posted January 17, 2012 Author Share Posted January 17, 2012 I reinstalled the latest KORS patch, still no difference, then I reinstalled PNW 004. Still no change. Then I reinstalled 004a. The mesh problems are still there. Link to comment Share on other sites More sharing options...
Alex Goff Posted January 18, 2012 Share Posted January 18, 2012 Do you have the OZx NA airfields pack installed? Link to comment Share on other sites More sharing options...
Wolter van der Spoel Posted January 18, 2012 Share Posted January 18, 2012 to add to Alex's post, for testing purposes disable all other non FTX sceneries and see if the problem persists Link to comment Share on other sites More sharing options...
MustangAce Posted January 19, 2012 Author Share Posted January 19, 2012 Problem Solved! I had searched the OZx folders for any bgl with wa35 when this first happened and found nothing. I went back last night and found 4 bgls with clmhbr as part of the filename. I removed all 4 and my msh is back to normal. Thanks guys! I should've just disabled it and checked that way right at the start, but I didn't think of it. Link to comment Share on other sites More sharing options...
Ed Correia Posted January 19, 2012 Share Posted January 19, 2012 That is good to hear. Out of curiosity, did you happen to install the OZx NA pack after installing KORS? It's just that the KORS installer is setup to disable these Clam Harbour files. Cheers Link to comment Share on other sites More sharing options...
MustangAce Posted January 21, 2012 Author Share Posted January 21, 2012 Frankly I don't remember. I reinstalled the latest patch for KORS, but I never reinstalled the entire package. I may have installed OZx after the original KORS installation. BTW, Clam Harbour is in Canada. Somewhere in Nova Scotia I believe. It's Clam Harbor here in the States. Link to comment Share on other sites More sharing options...
Alex Goff Posted January 21, 2012 Share Posted January 21, 2012 Frankly I don't remember. I reinstalled the latest patch for KORS, but I never reinstalled the entire package. I may have installed OZx after the original KORS installation. BTW, Clam Harbour is in Canada. Somewhere in Nova Scotia I believe. It's Clam Harbor here in the States. I don't know for sure, but if you install OZx-NA after KORS, the OZx Clam Harbor will be set on top and cause the issues you're seeing. KORS installed after OZx should disable the OZx Clam Harbor like Ed said. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.