456.71 is a good one too, very smooth here. (1660ti)
Fantastic Asobo! Good job!
they didnt fix live traffic or multiplayer issue.
Nice hotfix now my throttle doesnât work
The 0.4a of the Arrow and the latest of the FBW (0.6) and the Dev versions.
3 attempted flights. Sub 20 fps, regardless what my settings are. And all 3 ended in a CTD.
Looks like my cockpit is being put away again until the next update.
My confidence in Asoboâs ability to get things right is waning with every subsequent update.
What happens if you just load the game without any additional hardware attached?
Sorry for the stupid question but what is WASM?
I test flew the 0.4 arrow with no issues. Nice and smooth
I tried. I tried 3 flights.
-
Connected up my cockpit setup. My settings were 1440p with a mix of medium and high. Limped along at about 18-20 fps at an autogen airport in a non-PG area (my home town). Tried lowering my settings to all lowest and resolution scaling down to 70% (roughly 1080p with my 1440p monitor). No difference in fps. Switched to Ultra everything. Still no different in fps. Still at 18-20. Took off, did a couple of circuits. Left the circuit to fly over the city. CTD.
-
No hardware other than my XBOX controller. Community folder empty. Performance is the same as when everything is connected. Didnât even make it off the ground when doing that test with the XBOX controller. CTD while taxiing to the runway.
-
Restored all my community mods and cockpit. Restored my mix of high / med settings. Took off from KSAN, a custom airport in a PG-heavy area. Still the same 18-20 fps, but tons of stuttering and dips down to low teens. Made it about 20 miles north towards LAX. CTD.
Still no word from Microsoft regarding the new botched SDK process?
Thatâs specifically what this patch addressed.
Just landed at KSAN on 27 in the M20R, flying from KPHX. Tower had me fly a go-around. (Darned pokey 747 driver!)
No stutters, smooth performance in the Mooney. I didnât check my fps, but it had to be 40+ for the smoothness I was getting. Same report from Sky Harbor. Lots of traffic in the pattern and on the ground at both places; both Class B airspaces.
All I have in the Community folder is Navigraph. Since the update, if I have anything at all in the Community folder (other than Navigraph) I get CTD events. Looking at the Event Log, it is typically either an error with MSFS, or the (in)famous VCRuntime error.
So far, with a âcleanâ Community folder, I have had good luck. The stutters and three-to-five second-long freezes I was getting two days ago seem to have disappeared.
I am getting horrible performance now too around 10 fps average. Dipping down to as low as 5 fps. Unplayable 
Itâs not a KSAN issue. Pre-SU3, and post SU-3 hotfix, I never had any issue in that area.
So youâre saying this patch addressed the issue of now having to restart the sim every time a texture change is made in blender to be able to see progress in the sim? I donât see that anywhere in their notes, only WASM was addressed.
I misunderstood your post. Didnât even know that was an issue. Only SDK(-ish) issue I was aware of was the WASM issue.
Sorry about that.
Ahh all good mate 
Today was the first time Iâve ever landed there. I usually land at KSEE if Iâm flying down to the San Diego area.
Interesting that the issue has just cropped up for you post update. Youâve gotta wonder about why it happens this way⊠seems as though it is hardware and (perhaps?) driver related?
Last time around (SU3) I was out for about a month. Others (regulars) werenât having any issues. Truly a mystery wrapped in an enigmaâŠ
Thatâs right. Persons to be fired are quarantined before they can do mischief and escorted out.