Did you happen to use the updated NXi ? I’ve been meaning to update mine and see if it’s fixed. But have been testing other things first, lol.
I use the Sofly weather presets, never bother with live weather, as like yourself I found a few months ago it appeared to be the cause of a lot of my issues.
1 Like
Yes I downloaded the update, and it has been working fine for me so far, touch wood.
1 Like
I like the vanilla broken and scattered clouds presets. I think they improved since SU7. Live weather is always an unpredictable time bomb for me causing different performance issues.
The Sofly ones are good, although the winds are sometimes a bit mental and need to be adjusted manually.
1 Like
My concern on Xbox is going to be WASM and how that might affect performance, especially if it’s always grabbing data as an web app.
Serious optimization is going to be needed to cut down on some of this bottle necking (RAM issue?) and better use of our SSD drives for saving/moving data.
As it stands we still have WAY too many assets that pop in as you fly over them, they need to load a lot sooner. But if everything is trying to download at the same time and all being stuffed into the RAM, that’s an issue and CTD
3 Likes
Yes I agree regarding optimisation. That process is really still in it’s infancy. I think personally it’s very poorly optimised for Xbox atm.
2 Likes
I am finding a lot of micro-stuttering since this update…. FPS is in the 30’s, but not fluid…
2 Likes
Man… just an example how live weather can be sneaky and unpredictable: Today i was flying the A32NX and my FPS was really low on the ground. Knowing how often FBW update their dev version (especially on weekends), i assumed that one of the patches maybe had a bug or something. Then finally i decided to fly without live weather and my FPS boosted up again all over the place.
By the way, live weather in the area i was flying in barely had any clouds, it was mostly clear.
Ok, so I solved the studders that I noticed in 2D and in VR and this may help someone else out there. I did all the usual things to try and isolate the studders that started in SU9:
None of the following worked for me but here’s the list that I tried:
- Empty community folder
- No live weather
- No live traffic
- No multiplayer
- Clear the rolling cache
- Re-load the entire sim (yes, all ~185gb)
- Update all GPU drivers and chipset drivers and Win11 updates (I had none as I keep those updated constantly)
- Different planes, different airports, different times of day — all the same terrible results.
I was about to re-load Windows 11 and I tried one last thing that I had never messed with because it was never the cause of a problem….but thus time it solved my studders thanks to a tip from one of the regulars (@Shark) on the discord server for VR Flight Sim Guy.
- Backblaze Cloud Backup service: now, I had turned off this cloud backup service from the continuous backups it runs normally and for a long time was just manually running the app to back things up. But when I used Task Manager during a flight with studders, I noticed that there was a file running for Backblaze that was part of startup files and it wasn’t using much of the CPU (less than 1%), but it was there and I didn’t know why since I had set the backup option to “manual, not continuous”. Turns out that the app runs in the background still logging files that change so that when you decide to manually do a backup it quickly has the list of files to backup (a feature but also a problem here). That tiny program running in the background was just enough interference in the same cpu core as MSFS that when I shut it off the studders stopped. Note it wasn’t as simple as shutting the app off from the system tray as that just stopped the gui interface. I found a post on Reddit from a developer at Backblaze that explained that the small executable still runs in Services inside Windows and you have to terminate it there (under Services you will see a long list of stuff that doesn’t look recognizable so google and be careful before terminating non-obvious stuff) and I also set it to Manual so it doesn’t start up again the next time I boot up.
So long story here, but look for anything you don’t need and try terminating it in Task Manager one at a time after you research what it is. If it’s in the Services menu in windows it may also auto start when you boot up so you can also change it there to Manual.
I never had a problem with studders pre SU9 but this was terrible and nearly 10% of the frames were like 5fps, which was just enough on the low end to make it choppy and nauseating in VR. Even with average fps of say 30 or 35 or even 40…the 0.1% lows were 5 fps and 1% lows were at 15fps due to this tiny program running in the background and logging stuff. So, kill all the stuff you can that is running before you give up or reload windows or reload the entire sim.
1 Like
That’s interesting. So the backup solution is recording file writes so it knows what needs backing up and had been running fine with SU8 but caused stutters with SU9. That could mean that SU9 is doing more file writes than SU8.
Did you try running in dev mode already while backblaze was still active?
Tried NXi with update, instant CTD
2 Likes
That is the main issue for me as well. I tried literally everything but it is just snake oil at this point.
I also didn’t find a clear pattern on when exactly the stuttering appears. Sometimes it is right from the beginning, sometimes mid-air. I had40-50 FPS in the cockpit and 50-60 FPS in the outside view. It was a smooth experience until SU9. Now I have around 30. Doesn’t matter if I am in the cockpit or using the external camera.
1 Like
A lot more main thread limitations now…
1 Like
Please vote here if you also experience stuttering or worse FPS in comparison to SU8
1 Like
That’s disappointing. No issues for me so far. Not used it loads so will see what happens with it today as I plan on flying the Kodiak again.
This sim has a long way to go.
I’ll say it again, World Updates need to be shelved for the time being, and more resource needs to be dedicated to ironing out these game breaking issues, particularly on Xbox. A great deal of work is needed on the optimization process, for one. There is no point in creating new fires to put out when the existing ones are still burning.
If they got the sim into a (reasonably) stable state, they could then focus on adding new content, see what happens, fix any bugs that may arise.
4 Likes
I don’t think stopping world updates would help. These are done by 3d modellers and other graphics specialists, not by C++ programmers.
I would much rather have a couple of feature-free bug fix sim updates than what we’ve been getting. I thought Asobo had said that is what these updates were going to be but both SU8 and especially SU9 have introduced so many new problems that I think many users would rather be back in SU7. Certainly there are now more serious bugs than the were a few months ago.
2 Likes
Ok , I am on xbox series x and I can’t even get past the world map to select an airport to fly. the sim has crashed 5 times in a row. this is completely now Unplayable and unacceptable. where is the hot fix? where is the communication? I know I am not the only one here. the votes and the forum topics are clear, this needs to be fixed ASAP, Please
2 Likes
Another Video which shows one of the issues with SU9. I never had this issue in SU8.
Upon starting the sim, I have stable 42FPS in the cockpit.
However, as soon as I move the camera even one bit the frames start to drop and don’t seem to be able to recover again.
As you can see in the video, after moving the camera a few times, the FPS are stuck at 35 with regularly spaced drops inbetween.
At the same time you can see the GPU and the Mainthread load fluctuating.
Here are also two screenshots I made. I only moved my position one inch and the FPS dropped by nearly 5 and did not recover afterwards. And again with those regularly spaced stutters.
Before the update I also could max out my FPS in the outside view to around 50. Overall a big degradation.
1 Like
Yes, I had Dev Mode on and the fps screen said main thread limited during the studdering, but without Backblaze running it went back to GPU limited like I had always seen. Both before and after of course the overall cpu usage is very low but it’s one core that was getting maxed out with the combination of MSFS and Backblaze running. The next highest user of cpu for me is hwinfo64 which monitors temps and usage stats on all the hardware components (and inside of hwinfo64 it runs rivatuner as well to display stats in the system tray). That tool is great but sometimes has small jumps up to 2-3% of the cpu so I will kill that next if studders return to check it for load on the main thread of MSFS. I hope over time that Asobo continues to spread workload across more cores.
1 Like