The performance issue isn’t new. It started back with the UK update for me. SU3 made it totally unplayable at under 10 fps. The hotfix made it somewhat better, getting me back up to 30 fps.
Then the France update borked my performance again, like it did for many others.
The crashing, however, is new for me. It’s not related to KSAN because it crashed at my home airport twice prior to trying KSAN. I don’t know if the crashing issue came with the France update or today’s patch. Between the WASM issue and performance, it just wasn’t enjoyable to play after the France update and I haven’t touched the sim.
@SocialRegent58 Thanks for the heads up. I was going through everthing this week that may have caused my perfectly stable MSFS & Quest 2 experience go to _ell until I came across your post.
Thank you for sharing this. My bet it this update is causing havick with alot of peoples systems right now and they are wondering what happened and blaming Osobo.
Same here … Before the Recent Update, I had stopped ever getting a CTD.
This evening 90% on my way from Dulles to Boston, with the Airport almost in sigh, CTD!!
I’m on my way home to KPRB from KSAN in the Mooney. Beautiful sunset flight over Catalina, and headed to the Channel Islands as I type.
The only thing I’ve done differently from “before” is to empty - except for Navigraph - my Community folder. (Prior to that I was getting CTD events more bizarre than I’ve ever had.)
I truly don’t understand how we (those of us who seem to be here a lot) can be having such different experiences. (I get hardware differences and driver updates et. al. but still…) The AMD software tells me I’m averaging 59 fps over the past eight hours of flying time.
Flip back to six weeks ago: I couldn’t even start the software no matter what I did. I quit for a month. Others were having no problems, and reporting better performance.
By default:
My “Pause” is set to the “ESC” key on my keyboard.
My “Active Pause” is set to he “Pause” key on my keyboard.
Active pause will freeze my plane but time still continues.
“ESC” Key - Pause takes you back to the Options screen where you can hit “ESC” again to return to the flight.
Yes, me too. That’s the most annoying thing. And it’s here since 1.14.6. Also there’s a major drop in fps in cockpit view compared to external view. Between 10 - 20 fps difference. Only in glass cockpits though. I have multiplayer and air traffic set to off.
The bug related to the absence of mouse-panning following Ctrl-# is not fixed, and I think will now be forgotten. Logging it on Zendesk is just like sending it to the elephants’ graveyard - they acknowledge you’ve told them, but then promptly forget about it.
This hotfix is welcome, but still does not address many of the issues caused by the latest update. A better way of moving forward would be to not move on to the next update until all (and I mean ALL) the bugs introduced by the previous update are resolved. At the moment, we consistently have “one step forward, one step back” with every update. This is not the way to make progress.
