wolfko

Same here! After the SU4 update yesterday I am getting those red screens with WASM crash notofication, whenever I load the A340 at a runway. Also the landing gear is missing. When I start from a gate everything is fine. Also autosave does not work. When loading an autosaved scenario, the captain's side window will open, no matter if midair or on the ground and the PFD screen goes blank. Just for info: I have the A340 downloaded, not streamed. After having above issues yesterday I uninstalled the A340. The plane was then autonatically streamed and everything was fine. I then downloaded the plane again and it also worked for one time when starting on a runway. After then loading an autosaved scenario, all the issues were back.

I have the same issue even without VR. Extreme stutters and inferior performance on take offs and landings. Even during cruise flight the stutters are not completely gone. This is affecting all A330 variants and makes them unflyable. I wonder, that not more users are complaining about this issue.

I am a bit late to the party, but the issue with snow is not, that the roads are not covered, which reflects how it is in real life (snow will be removed there and also will melt there prior to grass), but the strange artefacts at the edges of the perimeter road and along the approach path lights. This is scnerey induced and has nothting to do with limitations of MSFS 2024.

Have you removed the pitot covers?

I have absolutely no idea, what you mean. Could you perhaps post a picture?

Since the flight levels at the left and at the right are not exactly identical, I would say these two tables are pretty similar. Also MSFS 2024 uses very accurate historical weather data, whereas simbrief has a lack of accuracy regarding historical weather data.

You have to disarm the doors before opening them. Otherwise the emergency slides will deploy. GSX will sometimes open the doors by itself, before you have asked for deboarding and have disarmed the doors. So disarm the doors as quickly after landing as you can.

Since with the streamed version the flightdeck looked like one of those infamous messed up PG sceneries when coming back from the settings menu, I have downloaded the plane and these issues are gone.

This works with any other plane but not with my A340.

I have just streamed the A340 and my first impression ist just WOW! Great performance and a joy to handfly. I did not have the time to have a closer look ate the systems yet but this looks very promisong. Just one question to iniBuilds, at the moment the plane is still streamed but would you recommend a download? Thanks, Wolfgang PS: is there a way to register this rpoduct with iniBuilds?

That depenfs on the payload. I have just done a first take of with a fully loaded plane and it really strugled upon take off and the climb path was very shallow. And BTW I would not judge a real world plane's behavior by watching YouTube videos.

I haven't figured out though how to input a negative time differnce to UTC by using "enter" plus my keyboard. But It works by using the FMS keyboard.

At the bottom of the Position/Time page you can insert the time differnce between UTC and local time (which you can figure out by clicking at the cloud icon in the sim's top screen menu). This will then then display the local time on the Position/Time page of the FMS.

I guess in the real world, the GPU has to be removed before the beacon is set to on, since this shows the plane is ready for pushback. And a pushback with the GPU connected is not possible.