Tom

Hello, For guaranteed support, the helpdesk is the only official way to request support -- you can find the support link in the top navigation header. The forum is more geared towards community support. That said, I don't believe these are raindrops; they're intended to be fingerprints to show a used cockpit.

Hello, The update process in general should not require you to redeem the key each upgrade; however, update version 1.0.3 changed the aircraft into a 2024 native SimObject layout. Because of this, the folder the WASM modules are stored in changed from (example path for MSFS 2024 on Steam): %AppData%\Microsoft Flight Simulator 2024\WASM\MSFS2020\aerosoft-aircraft-a346-proTo %AppData%\Microsoft Flight Simulator 2024\WASM\MSFS2024\aerosoft-aircraft-a346-proThis also happens to be the same folder the activation information is stored in, and so when upgrading from 1.0.2 to any version above for the first time, the new folder location is created, and a new activation setup is required. Upgrading from version 1.0.3 to 1.0.4, for example, should not require an activation again (but downgrading from 1.0.3+ to 1.0.2 may). When the next update rolls out, 1.0.5, providing you were on 1.0.4 you should not get the prompt to reenter your key.

The activation issue with the A340-600 Pro should now be resolved. We apologize for the inconvenience this has caused, and thank you for your patience while we worked to resolve the issue! If you have any remaining issues with activation, please reach out to our team via the helpdesk.

Hi all, We are currently investigating widespread activation issues and have just sent a message to our DRM provider regarding the issue since it seems like an issue on their side. We should have an update very soon, sorry for the inconvenience. Version 1.0.2, which is available via the experiential branch in Aerosoft One, is not affected by this issue.

For the folks not in our Discord, here's a quick copy of our message regarding this: If you're having these issues consistently, please do fill out the above form.

Hello, Yes - You're welcome to submit tickets regardless if you have purchased a product or not. I'm not sure this particular issue has been identified before, however, so I will log this as an issue internally. Thanks for the images.

This is likely because the aircraft changed to a native model in version 1.0.3 and higher. As such, third party liveries will need to be updated appropriately.

Hello, It sounds like this issue could be due to the community path in Aerosoft One being set incorrectly. Please try updating the path by following the steps below. Open Aerosoft One and click the "Settings" tab on the top navigation bar. Select "Manage Simulators" from the left sidebar. On the "Select Simulator" dropdown that should now be displayed, select your simulator. Click "Select" next to the "Installation Folder" path and set the path to the community fold. Note that this should be the folder that contains the simulators community folder and not the community folder itself. For example, if your community folders path is G:/MSFS/Community, the path in Aerosoft One should be G:/MSFS/ Once set, click "Save Simulator" and navigate back to the "Library" tab in the top navigation bar. If the product no longer shows as installed, reinstall the product. The issue should now be resolved.

Glad to hear you found it! I just closed out your ticket, and it looks like my reply did send this time, so it may have just been a temporary outage. Unfortunately, Zendesk doesn't provide us with in-depth email logs, so all I'm able to provide is that the mail server had a 550 status.

Hello, I've taken a quick look, and it looks like our reply to your ticket on Monday was rejected by your email provider/your provider was unavailable so you wouldn't have received an email response, however, the response should be there if you login to the helpdesk and view the ticket via the helpdesk. For the issue itself, we unfortunately are unable to reset FlightSim studio keys as they use their own activation servers. For assistance with FSS key resets, please contact the developers directly via the contact methods below. E-Mail: https://www.flightsim-studio.com/contact/ Discord: https://discord.gg/thcrb5UQaf

Hello, Can you please confirm if the file exists on your PC? Can you also try a reinstall of the product?

I've just replied to your ticket regarding this!

Hello, WASM crashes can occur for a variety of reasons, which are usually system specific, and some of which might not be directly because of the A340. Since this is something you're able to constantly reproduce, I'd first recommend trying a reset of the A340. If the crashes still occur after the reset, please drop us a ticket and we'll be happy to assist further.

Hello, I will pass this over to the project manager, thanks for letting us know!

Hello, I can confirm we are aware of this, and will work on resolving it!