Yeah, it seems they're still in the 'fix tiny things' phase. Although most of the now fixed bugs, I didn't experience.  I'm also waiting for some real QoL updates. For example let the user set one of the custom saved flights/configs as the default spawn config. This would also solve many problems with the EFB.

Still the jetway wants to connect to the 1L door no matter what (and breaks his back while doing it), even if your position is totally accurate at the gate. I know this is also a scenery/airport problem, but there has to be a way to make 1L (temporary) invisible for the jetway.

I have no fps issue here (2020). And no loading issues.  

Edited April 24Apr 24 by Watsi

The latest patch seems to have cured my load time problem in FS2024. Tested at a small, stock airport (EGNT) and the load time was less that 2 minutes. Exited the sim and tested again with a custom airport (EDDF) and the load time was again less than 2 minutes.

initial load time too excessive here. way beyond 25min. deleted WASM folder but no cure. how long did you let it sit and stew for the initial compiling?

My load times are 1min 45secs at KJFK with AIG loading at the same time.

Judging from the preview hype, this addon was supposed to be the shiznit. 

I guess not.🙃

16 hours ago, Bigmack said:

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

 

14 hours ago, Bigmack said:

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.

But you don't have the same system or configuration as @Purr, so how does the fact that you don't need to worry about performance, help him, if he's not seeing acceptable performance?
 

You probably "don't care about frame rates" because you have good frame rates.  Those on the borderline of acceptable smoothness and performance are clearly going to need to be looking at FPS, as part of their tuning of settings.

30 minutes ago, DAD said:

initial load time too excessive here. way beyond 25min. deleted WASM folder but no cure. how long did you let it sit and stew for the initial compiling?

Of course deleting the WASM folder will not cure it. It CAUSES it. The initial WASM compilation is what takes so long. Depending on systems it can take 15-30 minutes.

Subsequent loading should be faster.

All things considered, I remain hugely disappointed with this addon.  Each time, I really try to like it but there are always so many issues and 'non-optimal' things with it on every flight.  I was a huge ToLiss fan in my XP days but all of the areas of contribution by Aerosoft are just so weak.

I told myself I could live with the awful texture quality in the cockpit, if the experience overall was good. But it's not. 

The single only thing I like about this plane is the flight handling characteristics (hand flying).

I deleted it last night and - until it gets a very significant update - will stick with the Ini A340, when I need to scratch a 4-holer itch.

Considering the price of this, I find it the biggest overall disappointment, since moving to 2024.

Edited April 24Apr 24 by JYW

Just now, JYW said:

All things considered, I remain hugely disappointed with this addon.  Each time, I really try to like it but there are always so many issues and 'non-optimal' things with it on every flight.  I was a huge ToLiss fan in my XP days but all of the areas of contribution by Aerosoft are just so weak.

I told myself I could live with the awful texture quality in the cockpit, if the experience overall was good. But it's not. 

The single only thing I like about this plane is the flight handling characteristics.

I deleted it last night and - until it gets a very significant update - will stick with the Ini A340, when I need to scratch a 4-holer itch.

Considering the price of this, I find it the biggest overall disappointment, since moving to 2024.

Can't say I disagree much. I really expected more from the Aerosoft side of the aircraft. They used to be good modellers, but it seems they let go of all the talent and their project manager was content with mediocrity. The systems modeling is what saves this aircraft and I would very much this partnership to continue and bring us an A330Neo. But Aersoft really need to get their act together and learn to do good and detailed 3D-Modelling for MS2024 again.

36 minutes ago, Farlis said:

Of course deleting the WASM folder will not cure it. It CAUSES it. The initial WASM compilation is what takes so long. Depending on systems it can take 15-30 minutes.

Subsequent loading should be faster.

I am sure I let it sit at least 30min as I was working and in a call. but let me ensure, start MSFS2024 again, load that A340 and sit with my wife on the terrace in the sun which will easily take more than 30min...

There is one issue I have everytime Aerosoft issued an update (so two for two now). Afterwards when loading the aircraft the external model is missing. This is caused by the layout.json not being automatically updated and I had to run it through the generator myself after both updates.

I hope now WinCTRL's SimAppPro does a fast support now for MSFS A340-600 so we can use all the Airbus Hardware especially the MCDU where the display mode didn't work; the API is supposed to be fixed with the 1.02 update.

cheers 😉

1 minute ago, pmplayer said:

SimAppPro does a fast support now for MSFS A340-600

First AS must release the API SDK or whatsoever. Then WW can make their HW compatible. Based on my ticket I opened with AS 

1 hour ago, Farlis said:

There is one issue I have everytime Aerosoft issued an update (so two for two now). Afterwards when loading the aircraft the external model is missing. This is caused by the layout.json not being automatically updated and I had to run it through the generator myself after both updates.

Happens to me too. I just uninstall/install and that's it.

47 minutes ago, xender said:

Happens to me too. I just uninstall/install and that's it.

That's certainly another way to do it, but not necessary. The simple rerunning of the Layoutgenerator is sufficient.