DeeJay

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.

OK, but at the location where I think it should be, there is no "WASM" folder: %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\ => WASM\MSFS2024\inibuilds... Even when I navigate to the "packages" folder within the LocalState folder, there are a lot of addon folders such as your A300 package and your KLAX folder. But no A330 and no A350 either BTW. %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\packages => inibuilds-a330 I've got the MS Store edition of MSFS 2024. I've also checked the standard WASM path for the Steam edition, but as expected, nothing there either. Did I miss a change of the WASM location?

Hi there, I just had very strange problems with the A330 in MSFS 2024, when I tried to start a flight at the gate and chose the panel state "on APU": - The engines were "half running": EPR was 1.002, N3 = 30.8, N1 = 6.5, N1 = 14.9, from the outside the engine souded like they were running (and they looked like the nacelles were spinning), from the cockpit I got the engine start sounds all the time. All this while the starter switch was in the OFF position. - Engines could be started "normally" then. However, while being pushed by GSX (as many times before), an MSFS message "aircraft malfunction - gear system" showed up. I had to set more than 50% N1 to be able to move on the ground. - The scrachpad of the FMGC did NOT clear, when I inserted values into any LSK. For example, when I typed in "18.1" for the fuel quantity and entered it into the R LSK 2 of the init B page, it accepted the value, but "18.1" was still shown on the scratchpad and had to be cleared every time when I wanted to enter something else. Guess what fun it is to enter a longer flight plan 😛 - Fuel consumption in flight is WAY!! too high. I can't say, wheather 6000 kg/h per engine is wrong in climb, but the estimated fuel on arrival decreased by 0.1 every 10-20 seconds of flight. - In flight the TCAS reported "climb", and showed a green positive and red negativ scale of the variometer, but the ND didn't show any traffic at all. The TCAS remained stuck in exactly this stage for the rest of the flight (before I cancelled). - The throttle detents don't represent the set "null zones" in the calibration system of the EFB. Last time I flew it (days ago), they were completely fine. - FPS dropped extremely (!) while climbing and became a slide show from time to time, with no addon scenery used there. 10 minutes prior (Departure in LEMD / LVFR) and FSLTL traffic models, there was no problem with that. All this just happened out of nothing now! Restarting the sim, or reloading the aircraft doesn't change anything. And even the other panel states are messed up. Extremely strange. Have you got an idea, what could be wrong here? Thanks in advance. Best regards, Dominik

A no brainer: 1. EDDF - Frankfurt, please!!! There has never ever been a good rendition of this. And many others have avoided it for performance reasons, or because they haven't been let in by the authorities, obviously. A developer who can make such amazing EGLL and KLAX mega airports, is certainly able to do a very good EDDF, as well, right? 🙂 2. KOAK - Oakland. I don't know if I can call the existing scenery version even a "version" at all^^ 3. KATL - Atlanta. I've got ImagineSim's P3d version, and that one is really good. But we can hear a lot of complaints about the MSFS version, which I've never tried because of that.