Skip to content

WernerAir

Members
  • Joined

  • Last visited

  1. Hi there, I am wondering whether an update to the EDDF scenery is planned in April when the new Terminal 3 opens in real-world Frankfurt. If so, that woul be a great opportunity to revisit an issue that (for me) is the main problem in an otherwise great scenery, which is the incorrect animation of jetways on the A+ pier. I just repeated a systematic test with version 1.1.1 Rev C., checking all gates from A50 to A69 with two aircraft: the FBW A32NX, and the Inibuilds A350-900. This is the result: A50, A52, A54 and A58 --> animation crooked: final jetway section does not rotate correctly (A58 works by chance on the A350, but the front jetway is used to connect to the second door...) A62 and A66 --> jetway not moving at all with FBW A320, crooked animation with Inibuilds A350 A69 --> OK See below for some illustrating screenshots. I would really appreciate if you could take a look at this. It has been bugging me for a long time.
  2. Das Problem betrifft auch Cusco V. 1.6.1.
  3. Hi there, I just wanted to ask if the latest update is also going to be available on the MSFS 2024 Marketplace. I originally bought the scenery on MSFS 2020 in the Marketplace, and I am currently using version 2.3.0 which works OK in MSFS 2024. I would be happy to do the update to 2.4.0 without having to buy the scenery again...
  4. For me it works now - I could also install addons I had not installed yet. Thanks for the fix!
  5. I just did that. Hope it helps...
  6. In any case, the app unpdate released today does not solve this issue.
  7. I have the same problem. I got it to work by rebooting the computer and opening Aerosoft One before anything else, but even then the app does not work well - I had to products with updates, and for the second product to update I had to reboot again...
  8. Hallo Thorsten, gehe ich recht in der Annahme, dass das Update 1.0.3 gleichzeitig auch beim MSFS Markeptlace eingesteuert wurde? Grüße, Christian
  9. Thank you very much for providing a workaround - I am now able to use Aerosoft VDGS at all airports!
  10. I am having the same problem with Simwings EDDM and Simwings EDDH as well as Aerosoft EDDK and Aerosoft ENVA, all of which I bought from the MSFS Marketplace years ago. I have used them successfully with Aerosoft VDGS in MSFS 2020, and the sceneries themselves seem to work fine in MSFS 2024 as well, but I have found no way to get Aerosoft VDGS to work. From the way I understand the structure of the system, I think there are at least two reasons why it doesn't work: The folder names are different. Aerosoft VDGS finds the right path to my MSFS2024 installation (...\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages), but it expects two subfolders in there: Community and Official. I do have a Community subfolder in the Packages folder, but then there are three other subfolders: Official2020, Official2024, and StreamedPackages. As long as the Aerosoft VDGS driver doesn't look for these subfolder names, it is not going to find anything installed through the MSFS Marketplace. I don't think you can configure the path, so it would be up to Aerosoft to address this. The sceneries are streamed and not installed locally. This in turn has two implications: The package names are different. In my StreamedPackages subfolder, there are packages named "fs20-aerosoft-airport-eddm-munich", "fs20-aerosoft-airport-eddh-hamburg", "fs20-aerosoft-airport-eddk-cologne-bonn", and "fs20-aerosoft-airport-enva-trondheim". These names differ from what is set in the corresponding XML files in the "airports" subfolder of the VDGS driver package folder, although if this were the only problem, it would be simple enough to fix by editing the XML files. The folders under StreamedPackages contain only a few .fsarchive files, and no AFCAD or other files where the VDGS driver could find any devices even if it were to look in the right folder and under the right package name. Now this last problem is probably the interesting one, as I don't know whether it is in Aerosoft's power to fix it. Other than that, the solution would be to wait until MSFS 2024 finally offers an option to install packages locally (I assume the Official2020 and Official2024 subfolders are for this, as they are currently empty). There are some indications that SU 3 will bring about this possibility, so let's keep our fingers crossed... Of course, another possibility would be for Aerosoft to allow us to transfer our MSFS Marketplace purchases to our Aerosoft accounts - then we could install the sceneries in the community folder via Aerosoft One, and Aerosoft VDGS would work under MSFS 2024 as well. (@Aerosoft: How about this option... please?)
  11. I wanted to revive this, as I have seen today that it is still an issue - the A380 capable gates on the A+ pier are practically not usable...
  12. In my experience, probably all A-gate jetway animations need to be looked at. The A5x gates look in the wrong direction as depicted in the screenshot above, and the lower A gates often dock too high and don't connect completely to the aircraft. A1 is fine, I think.

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.