DeeJay

Made 3 long haul flights without a problem. Now on the 4th flight, I get exactly this freeze on the way back from Dehli to Frankfurt shortly before arrival. Very frustrating! I only know that from the ATR before.

No, RW pilots such as "A330 driver" (youtube) have confirmed that these clunks are just A320 specific. They are not audible in the A330/A340 cockpit. Other characteristic "electric startup" sounds don't exist in the widebody Airbuses either.

OK, but the pitch difference may be the most significant one, I would say. Thanks a lot in advance for working on it. And no, I don't agree with the sounds being "just" bad. I think with some tweaks at the right places they could be really good.

OK, thanks a lot for the quick reaction and for caring so much. Sorry, I discribed it a little more exactly in another thread. But if we have the chance to talk to you as the sound designer, I try to discribe the problem even very exactly by video. I'm rather sure it is NOT a problem of the recordings, but of how the numbers in the configuration file handle them. So, I catched a short video of the spool up of the A340 in my simulator with some comments at the times when problems show up: - When increasing thrust from idle, the idle sound increases in pitch and decreases in volume, until it slowly disapears with increasing power %, which is both correct. - At the same time, the "whine" sound comes in, becomes a little louder and increases in pitch, which is also correct. BUT: The pitch increase is way too small! To be precise, from the first apprarence just above idle to full power, it increases by just a fourth (to speak in music intervals). In reality, it increases by about a great sixth to a small seventh, which is a lot more. - Shortly before full power (or even any FLX power), the buzzsaw comes in - also correct. The buzzsaw sound itself is very correct concerning the pitch and general sound. BUT: The fact that the whine sound, which is still present at full power, is way too low on pitch, gives the wrong intervall between the idle sound and the buzzsaw at full or FLX power. And that is what makes people think the whole buzzsaw would sound unrealistic. But it's just the "whine part", and maybe its volume. BTW, the pitches/tones do not depend on the microphone, nor on the position of the microphone, but just on the amount of power. A recoding of a tone pitch on a cheap cellphone mic will have the same tones than a high end studio mic, but just wouldn't sound as nice. And the difference between a lower FLX power and full power isn't that significant concerning the pitch. Of course you can tell the difference with some experience, but the interval between the whine and the buzzsaw should be correct (and nearly the same) in both cases. Just the absolute pitches of each own of them is a little different. Furthermore, I find the whine sound just too low on volume. No matter which video, it's always a little more penetrant in comparison to the idle sound than in the current state of the inibuilds A340. Sorry for the excessive "music language". Music is a big part of my job. That's why I'm so focussed on the sounds. But let's be honest: Isn't an A340 sound a peace of music for many of us aviation enthusiasts?! 😉 In P3d times, there was a sound configuration called sound.cfg, which coordinated the single sound files (*.wav). There, besides the "vparams" which controlled the volumes of the original sound file at different power settings, we could find... ..."rparams=0.20, 1.0, 0.50, 2.0" (example) => which translates like: "At 0.2 (= 20%) power, the corresponing *.wav is played at 1.0 (= 100%) of its original pitch; and at 0.5 (= 50%) power, the same file is played at 1.5 (= 150%) of its pitch. In between the sound engine of FS/P3d slided the pitch accordingly. It just created a linear function of the pitch of the original file by defining 2 "power points" and assigning a 2 "pitch points" to them. As simple as that. And that was the main parameter that controlled the realism of the engine sound recordings - particually important for the spool sound. By just alterating the "rparams" (trial and error), I could solve a lot of "pitch problems" in some aircraft without any special audio app, whenever 2 files didn't have a good transition into each other, even in professional aircraft. The Piper 34 Seneca II from Carenado comes to mind. I think the A340 in the current state has got the same problem, assuming that there is at least one sound file for the "idle" sound, one for "spool" sound, and one for the "buzzsaw" sound: The percentage of the spool/whine sound has to be increased at the "upper" point, until it matches the proper interval at full power between the (still present) whine sound and buzzsaw sound. So much for the music theory 😛 However, I've got no idea, if these parameters and this configuratoion file still exist in MSFS. And even if it does, it's certainly encrypted, at least if we buy something from the MSFS store like this A340. I hope I could point out the obvious problem IMO a little more exact. No matter if the engines are modelled completely correct or don't: If the engine simulation remains what it is, it's "just" a matter of adjusting the pitch problem to make it sound more realistic. I think that is what flight simmers care about a lot more, as we are not CFM engeneers 😉 11:25 I'm not adressing the problem yet, that the sound in the cabin is currently the same in front of the engine as far behind the engine, because for me, the cockpit sound at this time is the most important thing for me personally. Best regards, Dominik

Absolutely! I'm curious why exactly for the newest airplane, the sounds are so underwhelming. The ones in the A350 are much better and even those in the A300. If you only take the cockpit sounds, even the engine sounds in the A330 sound a lot more credible "A330-like" from the cockpit.

First, congratiulations for a really good aircraft. I've just flown from FRA to BOS without a showstopper like a CTD or similar. Flew very nicely and smooth on FPS. But my far the biggest (and so far my only) thing I'm really disappointed of, are the sounds: 1) Engine sounds: As mentioned above, it just doesn't sound like an A340 from the inside. It's not about volume. I know you don't hear the engines too loud from the cockpit. But it's about the typical high pitch whine that is completely missing, and the typical roaring sound of the A340, that just sounds different. The idle sounds are fit in a little better, but still sounds quite strange when spooling up. In this matter, I find even the sounds of the free A330 matched a lot better. 2) Touchdown sound: Your A330 has been the first aircraft ever, where you could really feel the famous "double" touchdown of the main wheels of the A330/340 series: First, a light rattle when the aft main wheels touch down, and then a firm bump sound and a more intensive rattle when the front wheels of the main gear touch. I loved that so much in the A330, as it added so much immersion. Could you pleeeeease add this feature for the A340, too, especially as the knowledge of how to do that, seems to be there. That would add so much immersion while landing. Because at the moment, there is just one single "Boom" when landing the A340. Thanks.

Thanks a lot! I quickly tested my most important aicraft, among them your A300, 330, 350 and some other models and they finally seem to work fine now again 🙂 (even if switching back versions brings its own problems with the general controls). However, I didn't do a full flight so far.

OK, thanks. Obviously I can't anymore, because the note with the need to do that seems to have disappeared from the installer page. This once was noted at the installer page of the A350 withon the ini manager, along with the advice to erase the WASM folder. Both seem to be removed for obvious reasons.

Well, I only joint the beta option because your A350 site told me to do so in order enable the updates to work properly. If you tell me that this isn't neccecary anymore for the A350, I will be happy to go back to the stable version again. Can you confirm that? Meanwhile, similar problems as described above also crop up at the A350.

Yes, the info at "release notes" says SU 3 - version 1.5.21.0

Hey! The A330 is messing up again at my system. Like every time before, it happened suddenly, but continuously, without having changed anything. It wasn't even after a MSFS 2024 update. So, what happens: - Several knobs don't illuminate or don't go extinguish, when pressed. For example: The "FD" button. the "AP1" and "AP2" buttons, the APU buttons, the "CSTR" button,... They are functional, but their state isn't visible, they remain in the state of illumination as they have been when the flight initialized. - Manually inserting waypoints (into discontinuities) creates a huge mess in the ND. They are not recognized, neither by the FMGC, nor by the AP. However, they do show up in the ND, but "additionally" to the old waypoints. From that point, even the DIR function doesn't overwrite any waypoint before the DIR point. The AP flies it correctly, but the ND shows a mess of casual lines, the more DIR you enter, the more wrong lines. - Fuel calculation is completely wrong. The FMGC calculates too much consumption, thus showing values up to -90 tons for the destination, however, when I arrive, I have 40 tons too much onboard. I've also got the impression, that the plane ignores time acceleration. So when it flies 2 hours in 4x mode, it burns the fuel for 2 hours, not for 8 hours, as it should. - The plane "half" starts the engines as soon as the APU bleed is switched on (!), even before the engine mode selector is in IGN/START position. If you then start the engines by procedure, it only starts "the rest", which is basically only a few seconds to full idle. I already have deleted the WASM folder, which resulted in no change. So, I have no idea, which direction I should troubleshoot in. Have you got an idea, what could be so wrong here. Similar things already happened before, then, they have suddenly disappeared (without action), and suddenly came again (and again without any action by my side). Only happens in the A330, no such problems so far in the A350 or the A300. Thanks in advance. Best regards, Dominik

Hey! Are there plans for a MSFS 2024 version of OMAA? And if so, will this be an enhanced version? Or is the current 2020 scenery even compatibe with MSFS 2024? Thanks. Regards, Dominik

Well, I tried to test it. But meanwhile, I always get CTDs... and nothing else! Mostly, before I can even select an aircraft, let alone start a flight. I only have the inibuilds A320-330 default planes plus some liveries in my community folder. Horrible! Nothing is working anymore! From one day to the next, without modifying anything. I've got no idea what to do, especially, since MSFS 2020 runs fine. I don't think a RTX 4070 ti Super and 32 GB RAM isn't tooo bad, especially because it already has worked without problems before?!

OK, first of all, MSFS 2024 downloaded an update, and after updating, the whole sim always got a CTD as soon as the start screen showed up. I've now removed my whole Community folder. Now, it launches again. And in the A330, everything seems to work fine again. However, the complete LocalState\WASM folder has gone again. And in the LocalState\Packages, there is again the only inibuilds folder is the one of the A300. No idea if that's normal (?), as a didn't really understand what the files in the WASM folder do. But I'm gonna try to slowly add the other Community content again and see when starts to become unstable - even if I couldn't even closely find the real problem so far.

Thanks! You might guess it: There is no "Streamed Packages" folder inside "Local State". I've now manually downloaded the A330. Now there is at least a "microsoft-aircraft-a330" folder under ...Local State\WASM\MSFS2024, but only with a subfolder "work" which again contains only "flightplans", "simbrief.xml" and "ThrottleData.ini", but none of those encrypted looking files that should probably have been deleted. I'm gonna test the aircaft tomorrow and report back.