Actually the only (major) problem I’ve had with the new patch was the above “Application Error”, which has not recurred.
The problem I had with the Start button was a few weeks ago, and looks to have been caused by a bug in the controller settings page.
I too have the gtx1080Ti, chosen because of the 11GB VRAM - dx12 was known to cause problems in FS2020 with VRAM, and the 8GB of many later GPUs is really not sufficient for VR in particular (as I’ve outlined in a previous topic).
Ahh interesting feedback - checking NVidia’s website VRAM is:
I feel you are right about 8GB, which may explain why 3070 and 4060 users are struggling with FS24.
BTW What CPU do you use with the 1080TI?
Pity again VR users got the middle finger.
It’s unbelievable where are we going to?
More and more Vram means increasingly expensive video cards. 
From my POV all correct.
I have a 3060TI ((8GB) on a Ryzen7/5800 system with 64GB RAM, zero technical problems and absolutely smooth experience with FSLTL traffic at standard settings even at KLAX or KJFK. All locked in the sim to 30 FPS, which gives me on screen 60 
(Edit 12/21, 1945 z: This is with 2 monitors, one 2560x1440 for the sim, one 1920x1200 for things like LNM, chrome etc…)
Since Nov.19th I’m monitoring performance of my system VERY closely when running MSFS 2024:
The ‘trick’ for me was keeping texture resolution at medium and raytraced shadows off.
This way VRAM stays solidly under 7 GB = NO GPU spikes = smooth FS = (relatively) low GPU energy consumption (sorry, I’m European…the more German! 
).
If I crank up anything of my shown settings below, VRAM goes over 7,4 GB = STALL, STALL, STALL. (Jayne chimes in 
…)
CPU i9-12900K. 8P + 8E / 24 threads
By the look of it, still not fully utilized in FS2024, which says I am main thread limited, so the gtx1080Ti is apparently not a problem.
Exactly. Those two parameters have been the key to start enjoying FS24.
Even after limiting the power of my 3070 to 80% via Afterburner, with those parameter off and just like you, having limited the framerate to 30 using the Nvidia Control Panel, and then I double it with the Lossless Scaling app (not hacking at all) I’m getting a solid 60fps.
But not only that: I have also configured TLOD at 100 below 1000ft and changed the setting to 400 beyond that altitude . And still, I get 60fps 
With shadows maps at 1536 I don’t miss the raytraced ones.
Thanks for your excellent report, which confirms what Seb was saying in the dev video.
We have to experiment with Med to High settings to prevent the GPU being overloaded and stalled.
Thanks. The more I dive into the internals, the more I recognize how much better MSFS2024’s CPU/GPU/Memory handling is compared to MSFS2020. MSFS2024 seems way more scalable with acceptable results…
What is your boost clock speed?
I’m thinking we need at least 5GHz.
EDIT: 5.2GHz boost says Cpumark
Funny graphic and I get your point.
Perhaps Nvidia has traditionally chosen higher clock speeds? Hence 30xx and 40xx generations with higher clock speeds, but the same 8GB VRAM.
That has worked well for 2D games, but for the latest high res 3D scenery in FS24 we are now seeing VRAM as a barrier. Hence happy simmers are using low/med/high settings carefully.
Nvidia/AMD could produce 16GB and 24GB GPUs with modest clockrates at modest prices. At a price point they have to strike a balance of chip and VRAM area/speed/heat.
My 1080TI with 11GB continues to give good value. A short Cessna flight used about 6.5GB, smooth and stutter free; there is a margin of 4.5GB for improved detail.
If I was upgrading the GPU, I would target 16GB or 24GB.
Btw It remains to been seen if the X3D L3 cache of 96MB continues to offer a premium boost for FS24 (there is anecdotal evidence the premium has reduced, plus higher core Ryzens now offer 64MB L3)
Amd X3D CPU’s has a high temp. problem.
This is caused by the extra and larger L3 cache chips.
When they want to increase the core speed of the processor then they will have to curtail the L3 cache. Under volting can reduce heat production, but has the risk of instability.
I’m on 5.1GHz.
In VR on relatively modest settings, I achieve about 30fps average (except at various airports), and normally in the range 25-35. This is acceptable for me, as stuttering is minimal, it feels fairly smooth, and detail level is OK though obviously not as good as 2D.
I don’t really think I’ll be able to improve on that in FS2024. By comparison, in FS2020 I used DX11 and fps was about 5 higher, at higher detail level.
It is a pity Asobo chose to go 100% on DX12 in FS2024. It was never out of Beta in FS2020 and caused a VRAM problem for VR users even then.
Perhaps they will have a change of heart and include an option to switch to DX11, though I doubt they ever will.
It’s difficult for Asobo. DX12 has some streaming benifits that DX11 does not have.
As I mentioned my 1080TI and quad core Xeon @3.2GHz is smoother in FS24, so I’m happy with the changes. I am using low to med settings though.
I’m fascinated how you are still cpu bound with a 5.1GHz boost clock driving a 1080TI.
Perhaps it doesn’t boost as often as it could?
don’t want to be ungrateful. I appreciate the amount of work the team has done with the last patches
Still I had hoped for a little Christmas present. Well. Christmas Eve is on Tuesday, so maybe there’ll be a little something waiting for us come Christmas morning. 
Well, one down, 28746187465287436 more to go to give players what they have advertised… This is so disappointing. Nothing got fixed, and I mean major bugs. 110 kts windspeed at 2000 ft? What? And had to restart my career mode because of the random unrecoverable stalls crashed all my planes… I do not remember signing up as a beta tester, or is it a new subscription model where you have to pay $200 and work for free? It would be fine if devs just listened to us, but support is one sorry sight. I reported the science mission end bug where the sim crashes to desktop and hits you with a huge reputation drop, then the support just told me to set my clock properly on my pc and other irrelevant stuff, then it was admitted as a bug and got fixed. Now the tornado is not where the mission points the player.
Overall this is barely in a beta state, and I highly doubt that devs didn’t know about it… Shame on Asobo for releasing a product in this state. I get that this is becoming the industry standard, but this means that the userbase is growing more and more frustrated every time, and then Asobo stops being profitable, they close it, and then they blame the player base, who are demanding at least a somewhat finished product for their cash. Then the shareholders step in and want a get rich quick scheme… This is disappointing as hell, MS and Asobo… Hell I would even pay a monthly fee to keep this up and running, just to have a decent flight sim I can use, but this is just my opinion…
Doubt it. Theyre on break till mid January it seems
I doubt they spend all their days off in this period. I hope the marketing department takes a year off
no it’s too much until 15th january lol
Oh joy, the latest update is making my sim crash every time I leave a flight in Career and re-enter the headquarters. No error code just a stutter in the sim and a crash back to desktop. Sim worked perfectly fine before this update, thanks developers.
