jfwharton Posted April 13, 2020 Share Posted April 13, 2020 I was having trouble with 61B in P3D V4.5. I could not get the airport to display correctly. I had uninstalled Base, Vector, OpenLCNA and reinstalled them. I ran the airport elevation correction tool in Vector again and again but still had the issue. I thought if I purchased the newly released Boulder City scenery that it may fix the issue. It did not. Below is a screenshot of what I am seeing. Please advise on what I can do to fix this issue. I also have the Pilot's FS Global Ultimate Next Generation FTX mesh installed. I have tried disabling the mesh in the scenery library but that did not fix the issue. Link to comment Share on other sites More sharing options...
Nick Cooper Posted April 13, 2020 Share Posted April 13, 2020 Hello, you need to be using the very latest version of P3D, 4.5.13.32097, are you? Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 Yes I am using that version. Link to comment Share on other sites More sharing options...
Nick Cooper Posted April 13, 2020 Share Posted April 13, 2020 Are you using a navigation data update? Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 I just reinstalled the scenery installer for 4.5.13.32097. No change. Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 What sort of navigation update? I don't understand. I use the F1 GTN 750. Link to comment Share on other sites More sharing options...
Nick Cooper Posted April 13, 2020 Share Posted April 13, 2020 Hello, it has nothing to do with that but with the client. Are you using a navigation data update? Link to comment Share on other sites More sharing options...
Nick Cooper Posted April 13, 2020 Share Posted April 13, 2020 Something that updates the airport data. Fs aerodata for example. Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 I have a subscription to Navigraph and have updated the navigation data for some of my addons like Pilot2ATC, Active Sky for P3D V4. etc. Link to comment Share on other sites More sharing options...
Nick Cooper Posted April 13, 2020 Share Posted April 13, 2020 If not, try verify files. Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 Tried that, didn't work. Link to comment Share on other sites More sharing options...
Nick Cooper Posted April 13, 2020 Share Posted April 13, 2020 Is Vector AEC for 61B actually disabled, can you check? Link to comment Share on other sites More sharing options...
Nick Cooper Posted April 13, 2020 Share Posted April 13, 2020 Looking at this topic, it does not seem that there is an error in the product. Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 Yes 61B is disabled in vector. Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 I looked at that topic and wish my scenery looked like that. Link to comment Share on other sites More sharing options...
Nick Cooper Posted April 13, 2020 Share Posted April 13, 2020 Did you have a problem here before you added the new product? Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 (edited) Yes, I stated that above. And I couldn't figure out why 61B was not flat before I installed Boulder City. I had, as I said before, uninstalled base, vector, openlc na, my Pilots mesh, and reinstalled but still had the issue. I have been checking out airports all around that area as well as in other parts of the US and everything looks good everywhere, except for 61B. Edited April 13, 2020 by jfwharton Link to comment Share on other sites More sharing options...
Nick Cooper Posted April 13, 2020 Share Posted April 13, 2020 If you have installed this into your P3D v4 folder, can I have a look at your scenery.cfg file please? Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 I have the Orbx scenery installed into a P3D library folder not in the main P3D folder. Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 Here is my scenery config file. And here is what 61B looks like if I uninstall the Boulder City scenery. scenery.cfg Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 I really hate the way Orbx locks the Orbx stuff in the scenery library in P3D. Makes it very difficult to troubleshoot. 1 Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 I thought the issue might be related to Traffic Global Early Access for FSX P3D being installed. I saw an issue before with KLAS. I have since removed Traffic Global and removed the entry from the scenery.cfg file as well as the Traffic Global entries in the Addons folder. That did not fix this issue but fixed the issue with KLAS. Link to comment Share on other sites More sharing options...
Nick Cooper Posted April 13, 2020 Share Posted April 13, 2020 Hello, it is not the way that Orbx locks stuff, it is the way that P3D locks stuff. If it installed into the simulator, nothing of Orbx at all is locked. Are you using someone's mesh? Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 Yes I stated above that I am using the Pilot's FS Global Ultimate Next Generation FTX mesh. I have uncheck that in the scenery library but doing that did not fix the issue. Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 Is there any way to move my Orbx scenery from my library folder into the P3D main folder without uninstalling all of it and reinstalling it? Link to comment Share on other sites More sharing options...
Nick Cooper Posted April 13, 2020 Share Posted April 13, 2020 Logically, there is an influence on this airport that other customers do not have. We seem to have ruled out most possibilities, the most likely being something that updates the airport data and less likely that you have a remnant of another version that is affecting both your default version, if that is what you are showing and the addon. Your image of the addon shows the aircraft "spawned" at a location below the addon which suggests that either the addon's elevation is not working, highly unlikely given Jack's screen shot topic, or that your installation contains something that is setting a different elevation. The presence of an added elevation for KBVU is still my main suspect. An airport named 61B could not exclude it, either in the default version or in the addon version. It could be an AI traffic addon too. There is no way other than what you suggest to return the installation to the root folder. Where does the addon airport appear in your in-game scenery library? Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 (edited) Which addon airport? Are you referring to KBVU which you mentioned above? In my scenery library the following entry in listed as priority 7 FTX_AA_61B M:\P3D Orbx Library\p3dv4\61B Boulder City Municipal Airport\zoTNC\GYC_NA\FTX_AA_61B I have no third party scenery installed in this area. Only my Orbx scenery. Edited April 13, 2020 by jfwharton Link to comment Share on other sites More sharing options...
Nick Cooper Posted April 13, 2020 Share Posted April 13, 2020 KBVU and 61B are the same place. It was 61B and now it is KBVU, in the real world. If a real world ICAO code is changed and then the simulator's navigation database is updated or an addon is added with that updated ICAO code, then any exclude made for 61B will not work and the added KBVU version will interfere. It will do so with both the default airport and any addon. This is what I suspect here. If it helps, imagine someone being told to deny entry to a gathering to a person named Smith. That person arrives, but as she is now married, she is called Jones. Shouting out "Smith, please leave" still refers to her but she pays no attention, because she is no longer called Smith. Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 I uninstalled Boulder City, deleted the folder in my library and then reinstalled Boulder City into the P3D main folder. Still have the same issue. Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 I checked with my internet provider and fortunately since everyone is staying home these days for the virus they removed the internet limit on my service until the end of May. So I just uninstalled all of my Orbx scenery and started P3D and went to 61B and only saw the elevation issue due to the Pilot's mesh being installed. Now I am reinstalling my Orbx scenery and will let you know what I discover. Link to comment Share on other sites More sharing options...
kmelz Posted April 13, 2020 Share Posted April 13, 2020 (edited) I'm having the same issues. It seems as if the non-Orbx scenery that is being displayed is an airfield with the ICAO of KVBU. (This was found out after disabling all Orbx instances of 61B or KVBU) There are no other files in my main P3D folder with KVBU. I also have updated my core NavData from "https://www.aero.sors.fr/" Is there any way to exclude whatever scenery is displaying KVBU? Edited April 13, 2020 by kmelz Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 I installed Global Base, Vector OpenLC NA and Boulder City. Here are screenshots with Boulder City disabled in the scenery library and with it enabled. Link to comment Share on other sites More sharing options...
Nick Cooper Posted April 13, 2020 Share Posted April 13, 2020 Hello, the persistent error could be that your default airports have been modified. If this were to be the case, then the 61B exclude would not work on KBVU and would adversely affect the airport. You could try disabling G:\P3D v4\scenery\0202\scenery\APX17190.bgl and see if the addon then looks as it should. Link to comment Share on other sites More sharing options...
kmelz Posted April 13, 2020 Share Posted April 13, 2020 Nick, Just as you suspected. It looks like those Navdata updates were it. I disabled APX17190 and 61B appears normally. Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 (edited) i added disable to that bgl file. Here is what I have now at 61B. I have noticed that I have no aircraft shadow when at this airport now. Edited April 13, 2020 by jfwharton Link to comment Share on other sites More sharing options...
jfwharton Posted April 13, 2020 Author Share Posted April 13, 2020 Checking out the scenery and I noticed I do not have the arch under the bridge in front of the Dam. Link to comment Share on other sites More sharing options...
medx421 Posted April 13, 2020 Share Posted April 13, 2020 (edited) 2 hours ago, Nick Cooper said: The presence of an added elevation for KBVU is still my main suspect. An airport named 61B could not exclude it, either in the default version or in the addon version. I was hoping this wasn't going to be the case, but had a feeling it was going to be. We had a good discussion about this awhile back. Have a feeling this is going to be a frequent support issue for this product. I'm actually surprised this product didn't get the BVU designation. Edited April 13, 2020 by medx421 Link to comment Share on other sites More sharing options...
Nick Cooper Posted April 13, 2020 Share Posted April 13, 2020 That aside, P3D v5 might well change things a great deal. Link to comment Share on other sites More sharing options...
medx421 Posted April 13, 2020 Share Posted April 13, 2020 (edited) 8 minutes ago, Nick Cooper said: That aside, P3D v5 might well change things a great deal. I don't know. If v5 updates the ICAO's to current, then Boulder City is going to be BVU by default which is the crux of this issue. I plan on buying this product, but am a day or so out before I can get to sit down at my computer. If it's still problematic, I'll try and help with a fix, as I have some experience with this thorn. Edited April 13, 2020 by medx421 1 Link to comment Share on other sites More sharing options...
Nick Cooper Posted April 13, 2020 Share Posted April 13, 2020 This and many other airports will be made P3D v5 compatible, I feel sure. 1 Link to comment Share on other sites More sharing options...
Recommended Posts