dagghito Posted October 9, 2019 Share Posted October 9, 2019 Hello there. I've tried everything, I have the following situation at Bilbao. Add-ons: LEBB 1.1.0, latest version of Landclass EU, Vector, Global. Tried to run AEC with no success, LEBB isn't either in the 'AEC enabled' or 'AEC disabled' list. I have a file in scenery\world\scenery LEBB_ADEP3_MN_ALT.bgl. Tried to uninstall and reinstall again with no luck. It work perfeclty before, could it be related to P3D v4.5 hotifx 2? Any advice? Link to comment Share on other sites More sharing options...
Nick Cooper Posted October 9, 2019 Share Posted October 9, 2019 Hello, the quickest way to find out would be to spend a few moments returning to the P3D v4 hotfix (1) client version. Before you do, please ensure that you still have "Default Terrain" at the foot of your scenery library. I have hotfix 2 installed and do not see a problem with the airport. Link to comment Share on other sites More sharing options...
dagghito Posted October 9, 2019 Author Share Posted October 9, 2019 Thanks Nick for the quick reply, I'll try tomorrow. To be more specific, I updated the client content and scenery modules to hf2. Regards. Link to comment Share on other sites More sharing options...
Nick Cooper Posted October 9, 2019 Share Posted October 9, 2019 Thanks, as far as I am given to understand, it is only the client update that influences this behaviour. You do not need to touch either of the other two. Link to comment Share on other sites More sharing options...
dagghito Posted October 9, 2019 Author Share Posted October 9, 2019 Interesting. Returning to HF1 client: Reinstalling HF2 client: So the issue seems to be something related to the handling of airport altitude with HF2 client. Digging a bit LM forums I'm not the only one having this issue: https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=135117. Do you know if there's a way to fix this which won't mean reinstalling the whole simulator from scratch or force me using HF1? Link to comment Share on other sites More sharing options...
dagghito Posted October 9, 2019 Author Share Posted October 9, 2019 Update: I have FSAerodata, deactivating its entries in scnerey.cfg or putting them below ORBX ones, just above the bathymetry solves the elevation issue (FSAerodata files contain the stock airport elevation and in HF2, from what I've understand, the airport elevation is read from the highest layer) I have yet to discover if moving FSAerodata entries leads for other side-effects. Thanks for your help - you may consider this one solved from your side. Link to comment Share on other sites More sharing options...
Nick Cooper Posted October 9, 2019 Share Posted October 9, 2019 Hello, thanks, that is my understanding too. I am rather surprised that this sea change in airport elevations is not highlighted or even mentioned in the release notes. Perhaps they think that we will be so dazzled by the improved PBR that we will not notice being underground. Link to comment Share on other sites More sharing options...
panzer2181 Posted February 22, 2020 Share Posted February 22, 2020 LOL wow! Who in would of thought of that! Great catch! This was an easy fix! I was a bit shocked when landing last night at LEBB... Did NOT expect to see a runway and scenery underground... Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.