In case you hadn't heard:

The Aerosoft A340-600 Professional has received a new update to version 1.0.2, bringing new functionality, hardware support improvements, and multiple bug fixes to enhance stability and realism.

New Features
- Added pinned charts and airport quick access in the Navigraph EFB  
- Added LVAR to inhibit rotary acceleration for hardware FCU interfacing  
- Added SimBrief import option to not populate INIT B  
- Added support for SayIntentions CPDLC  
- Added a fifth line to the DCDU to match real-life configuration  
- Added data output for hardware MCDUs via the Aerosoft interface  
- Added LVAR for external replay tools to freeze system modelling  

Fixes & Improvements
- Fixed an issue leading to loss of MAN FLEX on engine failure during a FLEX takeoff  
- Fixed the cause for possible freezes of the FCU buttons after replay  
- Fixed an issue that could lead to certain mouse clicks in the Navigraph EFB page being ignored  
- Fixed an issue that caused a delay when downloading chart data for a new airport in the Navigraph EFB  
- Reduced the number of messages rejected by the ACARS system  
- Automatic clearing of the "F-PLN DATALINK IN PROG" message once the datalink is complete  
- Inhibited certain input events (e.g. terrain detection) during replay to preserve system state  
- Removed the "Always use SimBrief winds" option (SimBrief is now the only wind data source)

Make sure to update your aircraft to the latest version via Aerosoft ONE to benefit from these improvements.

Happy flying!

 

 

HELPFUL LINKS

• Aerosoft One
• Returns
• Updates
• Aerosoft Forum
• Submit a request
• Gift vouchers
• Freeware

INFORMATION

• Contact
• Press
• About us
• Corporate responsibility
• Careers
• Partners
• Terms & Conditions
• Payment and dispatch
• Information for battery disposal
• Revocation right
• Privacy Policy
• Accessibility
• Imprint

DON'T MISS THE LATEST NEWS

 

SUBSCRIBE

I have read the data protection declaration.

Copyright © Aerosoft GmbH - Copyright reserved

*All prices are quoted net of the statutory value-added tax and shipping costs, if not otherwise described
** Applies to deliveries within Germany, delivery times for other countries can be found in the shipping information.

Welc

How are frame rates with this update? I haven't really used it much since purchase because it felt very heavy on frames compared to A340-300. I understand this is due to the complexity of this product, just curious if FPS are improved for others with the updates since release?

I haven't used it much either. The frame rates were acceptable, but it took 15 minutes from pushing "start flight" until the aircraft was loaded. I just tested it: it's down to 5 minutes. Some progress, but that waiting timer is still annoying.

41 minutes ago, qqwertz said:

I haven't used it much either. The frame rates were acceptable, but it took 15 minutes from pushing "start flight" until the aircraft was loaded. I just tested it: it's down to 5 minutes. Some progress, but that waiting timer is still annoying.

Thanks for mentioning that @qqwertz. I have experienced the 15 minute wait too and basically gave up on using the aircraft becuase of it. My SIM time is limited enough without waiting for 15mins for an aircraft to load.

I'll try the new version and see if it has improved for me.

They haven’t mentioned lvar for “pilots life 2” Before it glitched with neofly which basically can’t detect take off. Not sure it addressed .

compare with inbuild list of changes those two updates log kind of pale 😞

Glad I'm not the only one with the issues loading. It often stalls during load with the spinning circle and I'm never sure whether to keep waiting or abort and try again. It's the only aircraft for me that does this, and it's not just the initial load like some that compile their WASM binaries on first load, it happens every single load.

3 hours ago, Purr said:

How are frame rates with this update? I haven't really used it much since purchase because it felt very heavy on frames compared to A340-300. I understand this is due to the complexity of this product, just curious if FPS are improved for others with the updates since release?

Who cares about what the frames are. Just jump in the plane and fly and enjoy.

2 hours ago, Bigmack said:

Who cares about what the frames are. Just jump in the plane and fly and enjoy.

Uh...yeah okay. I guess people who haven't had good frame rates so far with the product might be those who care. Maybe your line would be a great marketing slogan for new aircraft: "Who cares about what the frames are. Just jump in our plane and fly and enjoy."

 

5 minutes ago, Purr said:

Uh...yeah okay. I guess people who haven't had good frame rates so far with the product might be those who care. Maybe your line would be a great marketing slogan for new aircraft: "Who cares about what the frames are. Just jump in our plane and fly and enjoy."

 

My point was to stop looking at the frame rate counter and enjoy the flight and performance the A340-600 has to offer. I've completed 2 flights from LFPG to CYYZ and it flew perfectly with no issues. I don't care what the frame rates were during flight, just the performance and system operation.

Frame rate can effect aircraft performance. 

I never saw FPS issues in my flights with the A340-600 with my System specs.

Furthermore, I haven't really been able to detect these seemingly long loading times that some people have mentioned.

I hope that we now have support for the WinCTRL MCDU Display mode that didn't worked from the first release of the A340-600..

cheers 😉

9 hours ago, Tom Wright said:

Glad I'm not the only one with the issues loading. It often stalls during load with the spinning circle and I'm never sure whether to keep waiting or abort and try again. It's the only aircraft for me that does this, and it's not just the initial load like some that compile their WASM binaries on first load, it happens every single load.

I wonder if it is inadvertently re-triggering a Wasm compile on every load. Maybe something about the cache isn't working right?

Does anyone know if this has been reported on the official Aerosoft forum? If not, maybe the dev isn't even aware if it's not triggering on their system.

It still needs a lot of QoL improvements. Pushback isn't fixed, there's no way to persist the "OFF" on that annoying auto-save feature, there's no auto step climb among many others (bad modeling and textures included). All the rest seems to work fine and i had a nice uneventful 13h30 flight yesterday. This is what it was built for (very long hauls) and it delivers there.

26 minutes ago, weaklink said:

I wonder if it is inadvertently re-triggering a Wasm compile on every load. Maybe something about the cache isn't working right?

Does anyone know if this has been reported on the official Aerosoft forum? If not, maybe the dev isn't even aware if it's not triggering on their system.

Thanks for reminding me. I had even worse problems with the initial release (WASM crash every time I started a flight) and Aerosoft told me to delete the WASM folder of the plane to recompile it. That took 20 minutes and resolved the issue. Every other time I started the plane afterwards still took very long, but more like 15 minutes. 

After your post, I loaded a flight two more times. The plane needed about 3 minutes to load. That's in a range that I find acceptable. The only other plane on my system that needs longer to load is the iniBuilds A350 with about 1-2 minutes. So, the loading time is now roughly comparable. Thanks to Aerosoft and ToLiss. 

I also checked frame rates, they are very good. My system is now 5 years old and certainly not top of the line anymore, but I get (at very basic airports in a remote area) 60 fps when the plane is cold and dark, and 45 fps after starting up the systems. That is pretty good on my system and better than the iniBuilds A350.

I think I will take the plane for a spin this weekend 🙂

1 hour ago, weaklink said:

I wonder if it is inadvertently re-triggering a Wasm compile on every load. Maybe something about the cache isn't working right?

Does anyone know if this has been reported on the official Aerosoft forum? If not, maybe the dev isn't even aware if it's not triggering on their system.

Yeah I reported it, didn't get an official response.

As with others here, my sim time is limited so waiting 15 mins to load a plane isn't really that great for me when I could be up and flying in something else in a fraction of that. Never had loading times this long with Inibuilds, PMDG, Fenix etc.