YS0430

I flied from KSFO to KLGA, everything was smooth and normal until after I started descend and inputting the D-Atis info, then I turn the distance display to zoom to try load the airport map for BTV selection, instant hangs all WASM and the plan is not responsive to any inputs nor the FD have any movement.

1.1.5 and the default cabin still don't work with co pilot and livery have no effect on the default cabin details, seems like it won't be fixed in a few more months

I recently compared the latest fenix A320 and the ini A350 and discovered that the fenix have almost double the framerate and being more stable on the system front, while the 9070XT always work at the high boost clock ~2700-2900Mhz with >70% GPU usage, while in the A350 it's mostly main thread limited and the frame rate was frequently limited to ~25fps with 14900k overclocked to all P core 5.9ghz and 4.5 E core, I believe this is due to the in game WASM systems, wonder if any chance of the approach of having an external app to make the PC really running it's potential and not having abysmal main thread limited issue?

I disabled autosave, basically mostly just put the sim in background task to let the monitor to sleep mode for a few hours and once get back it's a WASM hangs without any system responding. the recent days also have cases where I opened a youtube on backgound and once flip back all lights are on and no systems responding. I am using a 14900k (to be extrasafe, I run 10x cinebench R15 all pass, intel diagonistic tool passed, XTU AVX2 2 hours test passed), 64GB DDR5 6000 C32 and 9070XT

now every flight over 5 hours will have WASM crash and cannot handle the plane, so frustrating for a long haul airliner

Thanks for the reply, if I have to guess it will be some kind of linking prefex in the code being messed up. maybe need to reimport the 3D model with the latest SDK just like the cabin pack to fix the issue

Get the cabin pack and use anycabin except the default cabin which is somehow broken now... that's the temp solution for me

Then it becomes more akward for me.... it worked in the Fenix for me, but I only used FSLTL traffic injection, which even without it the loading have no GSX sound on A350. I am only using the default ASOBO crappy ATC

First flight after updating, the VNAV in managed descend now somehow just ignores the flight profile and aim at a constant -700fpm rate, and also lets the speed to keep going below the targetted speed, anyone have the same issue?

Yea they are available now, but sadly it kills the main thread even I am using a 14900k.... once the door is open to render the passengers in a 367 passenger config, the FPS dropped from 40 to 15..... just plain useless. Regarding the co-pilot, in my case the DEFAULT CABIN is the culprit, after 1.1.0, the co pilot disappeared altogether in the default cabin setup regardless of settings or livery, but once you use another cabin from the cabin pack, bam the co pilot comes back to work! I was stuck using default cabin since I fly the Cathay Pacific livery and that pairing it with other cabin feels odd, but now I am forced to use it with the british airways cabin for that sake.

Just the A350, in the Fenix A320 it works well, seems linked to the GSX implementation

after 1.1.2 GSX pro, though still working, have all those sounds like "refueling truck is on it's way" disappeared, checked GSX settings and sounds are set to on.

Being one of the largest fleet in service, it's a shame that the cathay pack isn't available

@ eddie, any update? I really love to fly cathay, but it seems that using default cabin will ALWAYS remove the co pilot...

1) It's an iconic airport, that even Asobo didn't include it in the default airport in 2020 later added it as default package 2) It used to have the navigation correctly done in the PREVIOUS ini A350 version, now the runway is flipped after the update, so it is something broken that wasn't how unreasonable for us to request for fixing of something newly broken?