Jump to content

WebMaximus

Members
  • Posts

    582
  • Joined

  • Last visited

Posts posted by WebMaximus

  1. Thanks again John.

     

    I came to the same conclusion and now after manually moving LGAV over to the disabled side for GSX jetways, I only see one set of gates on the map.

     

    Normally, this will be handled automatically by GSX but that is provided the airport scenery developers used standard MSFS namning convention. Which apparently isn't the case for LGAV. As mentioned, I've also seen this at some other airports. So I've now made sure all my 3rd party airport sceneries have GSX jetways disabled 👍

     

    This is what the GSX manual has to say about this:

     

    The “Exclude 3rd party” button will automatically move all the installed 3rd party airport in the “Disabled” list, it’s typically used after installing a new scenery. In order to be successfully recognized, airport packages must use the standard MSFS naming convention developer-airport-icao-name.

  2. Thanks for trying to help John!

     

    I don't have anything else installed related to LGAV AFAIK. The only thing I can think of which possibly could cause this 🤔 is GSX Pro. Which adds it own jetways etc as I understand it.

     

    Maybe worth asking in the support forum for GSX. Might be my next step.

  3. When at the main screen in MSFS where you select your next flight, for LGAV (and I've seen this for some other airports as well but can't recall which from the top of my head) there are two different starting points where both are connected to the same gate/stand number.

     

    Right now for instance, I'm starting a flight from LGAV where I parked yesterday at the gate named A38. As seen below, there are two starting points for each gate at the A terminal and I learned the hard way, I need to select the outer one for A38 but make sure the aircraft is lined up correctly.

     

    Would be interesting to know what is causing this behavior and if there's anything I can do on my side to sort this issue? To end up with only the correct starting point on the MSFS flight selection map screen for each gate.

     

    FxPw8F9.jpg

  4. Thanks Nick for always being so active in here and supporting us!

     

    Didn't try what you suggest to have GSX reposition the aircraft using the menu. Yesterday, I parked and stopped based on the instructions and today, I loaded up the flight using the menu in MSFS.

     

    Based on your discovery, it looks like the GSX config file which comes with the product could need some tweaking to make sure you end up in the correct position.

  5. Below is how I end up when loading a flight to start at gate 38 at ESSA. Clearly, the jetway is not aligned with the aircraft and I also noticed this yesterday when I flew into ESSA and parked at this gate. Stopping where I was told to. Result...the GSX PAX weren't able to deboard even when I'm using the GSX profile which comes with the scenery.

     

    image.thumb.png.6b537993d0370cd1fbd201fe962106b6.png

  6. So, I've now followed your advice to remove everything and start over with version 2. Below are the steps and the result:

     

    1. Uninstalled EGNM via Orbx Central - Successfully uninstalled according to Orbx Central but the EGNM version 2 folder in the Community folder was not deleted

    2. Manually deleted the EGNM version 2 folder inside the Community folder (EGNM version 1 folder already manually deleted before this)

    3. Noticed how there were left-over .dat files found in ...\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes

    4. Manually deleted the left-over files from step 3

    5. Installed EGNM version 2 via Orbx Central

    6. Looking in the Community folder, ...\Community\Orbx-airport-egnm-leeds-bradford was created (this time it has the same name as EGNM version 1 and it does contain the GSX folder)

    7. After launching MSFS, the .dat file for EGNM version 2 was recreated

     

    Conclusion:

     

    If you end up like me, having the folder for EGNM version 1 not automatically removed when uninstalling EGNM version 1 via Orbx Central, you will end up with a new folder for EGNM version 2 when installing it called ...\Community\Orbx-airport-egnm-leeds-bradford-v2. Not fully sure where that v2 at the end of the name comes from, if it's Windows adding it or Orbx Central when discovering there already is a folder called ...\Community\Orbx-airport-egnm-leeds-bradford.

     

    So there we have it and hopefully all should be sorted now and I copied the GSX profile to the appropriate GSX folder.

     

    All good 👍

    • Thanks 1
  7. Got it Nick, will give it a go. Even when I think this is pretty much what I already did.

     

    Still, what it says now in your post above and also in the release notes isn't correct. Since that path is referring to version 1 of EGNM rather than version 2.

     

    Or are you saying version 2 will have the same folder name as version 1 when it has been  correctly installed? Meaning no -v2 at the end of the folder name?

     

    Will report back.

  8. As you know, I already deleted the folder seen above. This is why I was surprised to see how it's now back again. Also, looking in the version 2 folder, there's no GSX profile. Not even the GSX subfolder.

     

    If you look at the path you just gave me where to find the profile and also the path referred to by the release notes now when you updated those, that folder still indicates version 1 of the scenery. Have another look at the paths I mentioned in my last post just above.

     

    I'll edit my last post and highlight the paths for visibility.

  9. Many thanks Nick!

     

    Still a bit confused though looking at the path. After having uninstalled version 1 of EGNM as per the instructions when installing version 2, I was expecting to find this file in the version 2 folder (...\Community\Orbx-airport-egnm-leeds-bradford-v2) and this was the first place I looked for the profile.

     

    I now see the folder for version 1 (...\Community\Orbx-airport-egnm-leeds-bradford) has been recreated in my Community folder. Even when I no longer have version 1 installed. I also see how there's some other content in there as seen below.

     

    image.thumb.png.5aef6e5cb5da1d753d260eefbc027b8c.png

     

    Looking a few posts up, I asked about this specifically where you said the version 1 folder should have been removed when I uninstalled version 1.

     

    So to me, it looks this GSX profile for version 2 ends up in the folder which used to be for version 1. When that folder isn't found, it's recreated. Which of course leaves me with the question if there's other things in that version 1 folder in addition to the GSX profile which is still required by version 2?

  10. Based on the price, there must see some genuine golden easter eggs included with this one!

     

    Just like with EGNM, I hope we'll see some discount for versions 1 owners here as well?

     

    Also, when looking at the key features section on the product page, I was missing the ability to remove static aircraft models. Any comment on what to expect in version 2 in that regard?

     

    image.thumb.png.db5f58b77724786d1d2dd84c61082692.png

    • Like 1
    • Haha 3
  11. Tonight when flying into ENTO, I noticed something I didn't see before. Could be because I never flew there when it was dark before.

     

    Anyways, what I noticed was a number of white lights hanging in the air. Noticed several of them in various locations during my taxi to the gate after vacating 36. Below is a screenshot after I parked where some of them has been pointed out.

     

    Did a search before posting but couldn't find anyone else reported this. Which makes me wonder if it's an issue just over here. Would seem strange to me though since it looks and feels very much like a scenery issue to me rather than a local issue on my side but what do I know...

     

    This is what I'm referring to

     

    image.thumb.png.2f2b840b1e9e21cf463653f8ea7abfc7.png

  12. Just did another test after uninstalling Orbx LDSP and no more crashes when moving around in drone view. So it looks to be some form of conflict between Orbx LDSP and WU 14 I'm sorry to say.

     

    Guess I'll have to depart Split using default scenery tomorrow. Even when I've so far only experienced the crash when in drone view, I guess same thing will happen when flying properly in an aircraft. Should also mention it happens in various directions from the airport. I've tried moving both in a NE direction along with runway 05 along the water but also in the other direction. I never got very far before I was told I crashed into an object. I think that is what the message said anyway as I recall it.

×
×
  • Create New...