ESzczesniak Posted December 21, 2016 Share Posted December 21, 2016 I have this "step" off to the left or runway 23 at Orbx PAJN. Any thoughts as to whats causing this? I have Orbx SAK (all regions actually), global, vector, OpenLC NA as well as Tongass Fjords X. In fact, I just installed Tongass Fjords in to P3D today and this is when I noticed the problem, although I haven't flown to PAJN recently and this could have been there for a while. I tried disabling the Tongass entries and this did not solve the problem. I searched my P3D v3 folder for all files with "PAJN" in the name, and they were all either related to Orbx or AIRAC data. Link to comment Share on other sites More sharing options...
Doug Sawatzky Posted December 22, 2016 Share Posted December 22, 2016 Did you run the AEC tool in Vector? Link to comment Share on other sites More sharing options...
ESzczesniak Posted December 22, 2016 Author Share Posted December 22, 2016 57 minutes ago, Doogles said: Did you run the AEC tool in Vector? Yes, I both ran the auto correction and looked to disable it manually and PAJN is not in the list of airports with AEC data (I suppose that may make sense since it's in Orbx SAK). Link to comment Share on other sites More sharing options...
Doug Sawatzky Posted December 22, 2016 Share Posted December 22, 2016 Are you using My Traffic 6? Link to comment Share on other sites More sharing options...
Doug Sawatzky Posted December 22, 2016 Share Posted December 22, 2016 Maybe also do search using "PAJN Elevation" seems to be a lot of other info. Cheers Doug Link to comment Share on other sites More sharing options...
Stewart Hobson Posted December 22, 2016 Share Posted December 22, 2016 Some other scenery placed above PAJN is interfering with Vector's AEC for PAJN, would be my guess. Link to comment Share on other sites More sharing options...
ESzczesniak Posted December 22, 2016 Author Share Posted December 22, 2016 I do not have MT6. I have also tried disabling the elevation correction file (from this thread: ). All that did was put everything in a canyon. It's not that this is all that bad or that the airport is unuseable, but I'm pretty sure it's not supposed to be that way and would like to figure it out. Link to comment Share on other sites More sharing options...
Doug Sawatzky Posted December 22, 2016 Share Posted December 22, 2016 Is your mesh resolution set at 5m? Link to comment Share on other sites More sharing options...
Jon Clarke Posted December 22, 2016 Share Posted December 22, 2016 Disable Vector and see if it does anything. Vector contains a file called ABL_PAJN.bgl in it's FTX Vector APT folder which may be interfering. Vector should be disabled in a Full Fat Region like SAK if you intend to just remain in that Region. Obviously enable Vector if you are going to fly from a Full Fat Region to another area not covered by a FTX Region. Link to comment Share on other sites More sharing options...
Stewart Hobson Posted December 22, 2016 Share Posted December 22, 2016 I don't see the need to disable Vector if flying in a full fat region. I have Vector enabled when I fly SAK, for example, and I don't have an elevation problem at PAJN and never have. I've recently been flying in NRM and PNW in Canada and Washington state, with Vector enabled with no problems with *any* of the airports, big or small, that I visit. In fact, Vector is disabled only when flying in Australia. If I do encounter an elevation problem, which is rare, I try to manually disable the AEC with Vector's AEC tool. There's something else interfering with the OP's PAJN elevation, imo. It could be, as Doug mentions, the OP's mesh resolution is set incorrectly. Link to comment Share on other sites More sharing options...
Holger Sandmann Posted December 22, 2016 Share Posted December 22, 2016 Hi guys, it's difficult to say from that single screenshot but perhaps it's the same issue as discussed here: http://www.orbxsystems.com/forum/topic/73167-vector-causes-mesh-issue-at-pajn-payware-within-sak/ If not then I'd suggest running another Windows search of your entire P3D folder tree (including any external scenery locations you may have) for .bgl files that include the airport's ICAO as part of their names -- e.g., search term *PAJN*.bgl -- and post a list or screenshot of the results with full file names and folder paths so we can help you tease out the incompatible file(s). Cheers, Holger Link to comment Share on other sites More sharing options...
ESzczesniak Posted December 22, 2016 Author Share Posted December 22, 2016 6 hours ago, Holger Sandmann said: Hi guys, it's difficult to say from that single screenshot but perhaps it's the same issue as discussed here: http://www.orbxsystems.com/forum/topic/73167-vector-causes-mesh-issue-at-pajn-payware-within-sak/ If not then I'd suggest running another Windows search of your entire P3D folder tree (including any external scenery locations you may have) for .bgl files that include the airport's ICAO as part of their names -- e.g., search term *PAJN*.bgl -- and post a list or screenshot of the results with full file names and folder paths so we can help you tease out the incompatible file(s). Cheers, Holger Disabling the vector files mentioned in the above thread did the trick. Thanks! Link to comment Share on other sites More sharing options...
Holger Sandmann Posted December 23, 2016 Share Posted December 23, 2016 Hi there, good to hear. I wish I knew what the cause for that odd behavior is so that the Vector devs could work on an updated file... Cheers, Holger Link to comment Share on other sites More sharing options...
Stewart Hobson Posted December 23, 2016 Share Posted December 23, 2016 On closer look, I saw the same problem as was discussed here and the previous referenced threads. Deleting the file in question solved the problem. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.