Problem for me is maintaining the FPS. It’ll be great for 2 hours then suddenly I’ll go from rock solid 60fps on one race to 40fps on the next race. The race after that will be 20fps. Only way to fix it is to quit the game and restart. Seems like a memory leak.
2 Likes
Has this been acknowledged by Turn 10?
It is such a frustrating experience to have the game running smoothly only for the bext race to drop FPS quite significantly. Memory leak seems like the culprit…
2 Likes
I still have fps issues, first two events the game runs smooth as butter, but after the 3rd event where i change my car or track goes from day to night, the fps drops severely
2 Likes
No idea. Searching the issues section of the forums isn’t showing much but then again it’s all down to how it’s been described. I can’t see how they don’t know about it though.
PC performance issues are among the fixes listed in the Update 5 preview, pinned at the top of this forum:
2 Likes
Do we know which of the pc performance issues are being looked at? It’s hard to understand from the wide variety of issues people are having and what is listed as a known issue.
2 Likes
Another night of MP and exactly the same thing. Hit the two hour mark and the FPS drops off a cliff.
Really hoping this patch improves this as the situation is just not fun.
Reverted but copied what the changes were. Yes, the changes are good enough to reply to myself and confirm that its better. I plan on getting some screen grabs and giving a better before and after.
If you have an Nvidia card, you might want to try this out.
Again. This was suggested by @aliensnUfos
Best advice on getting the game to look better IMO.
Imagine running sharpening through Nvidia’s Game Filters or Reshade, but with a slight FPS improvement instead of a hit.
EDIT: I picked two pics that best illustrates the differences in the settings vs. the default Nvidia 3D settings.
Default title screen…
Modified title screen…
Default On track…
Modified On track…
The modified shots are clearer and sharper than the default images. What you don’t see is the lap at Hakone was hovering in the mid 70FPS with the default settings, but with the modified settings I was sitting at 91FPS for my highs and 87FPS were my lows. This is running the game with triple screens, so I’m kind of running it at 3K, if such a thing existed.
In the video, he has something where he changes the size of the shader cache. I reverted it back to default. My games loaded much quicker in doing that… The tradeoff, you might get lower textures in some areas.
I hope this helps and thanks once again to RoastJeans for this one. It really made the game look and run better!
4 Likes
I use these settings:
Current Dynamic Render Quality: Custom
Dynamic optimization: Custom
Fullscreen: On
Show framerate: On
NVIDIA DLSS: Off
AMD FSR 2.0: Off
Performance target: Unlocked
Resolution scale: 100%
Anistropic filtering: 16x
Raytracing quality: Off
RTAO quality: Low
Shadow quality: High
Cubemap reflection quality: Low
Car model quality: High
Car livery quality: High
Windshield reflection quality: High
Mirror quality: Medium
Track texture quality: High
Particle effects quality: Medium
Motion blur quality: Off
Lens flare quality: Off
These are basicly the Digital Foundry Settings.
In 2160p at 120 HZ with 75 FPS cap and active V-Sync & G-Sync in Nvidia Control Panel. In the beginning for like 30-60 seconds, i get stuttering due to the loading of the liveries but then it works okay ish. It’s not ideal but okay. If i go higher than 75 FPS i get massive juddering, stuttering and bad frame pacing. I blame the horrible CPU optimization of the game it’s single threaded instead of multithreaded.
R9 5950x, RTX 3080 (10 GB V-RAM), 32 GB 3600 MHZ RAM, installed on a Samsung 990 Pro NVMe with active DirectStorage. And i use Windows 11 Auto-HDR.
Benchmarks results without any FPS limit.
3 Likes
Indeed it does take longer to load into the tracks and the shaders at launch but longer loading for the night and day overall look of the game is totally worth it.
If any NV users are having track surfaces that look washed out and that horrid foggyness plus a lack of sharpness the above video will fix all of that.
The video should be pinned in the Troubleshooting hub cause it’s that good 
2 Likes
I originally had my Nivida Control Panel Shader Cache Size set to 100 GB & the game always runs through a quick (~12 seconds) shader optimization at start-up beginning at around 78%.
Per this video’s recommendation, I set Nvidia’s Shader Cache Size to 10 GB, which caused the game to always do a much slower (~3+ minutes) shader optimization at start-up beginning at 0%.
So I reverted the Shader Cache Size back to 100 GB & I’m back to a quick shader optimizations upon game start-up.
2 Likes
I have mine set at 5GB and it takes around a minute to do the shader optimisation.
I’ll set it to 50GB next time I run the game and see if it make a difference
Also the shaders start compliling at 33% for me on 5GB
Edit: scratch that, there’s only settings for 1,5,10,100 or unlimited so went 100GB and cut the shaders in half plus the ingame loading is pretty much instant
2 Likes
I had my Nvidia Shader Cache always at 10 GB and only have one shader compiling after each driver or game update. Just how it should be. No idea why you think the shader cache size matters that much.
I think Forza Motorsport doesn’t even use that specific cache. That is for games that download shader caches on a regular basis, like Cyberpunk 2077 and the good old Valve games like Left 4 Dead and such. These are the tiny updates (just a few kilobytes) the games recieve via steam every few days.
Compiled shaders of FM23 and nvidia shader cache aren’t the same thing. Same like that cache doesn’t matter in games like The Last of Us Part 1 or Mass Effect Andomeda. They save their shaders in their own gamefolders that has nothing to do with the nvidia shader cache. What you are experiencing is a placebo effect combined with circumstances that make it shorter for whatever reason.
But that has nothing to do with the NV shader cache believe me. That cache gets used by heavy modded Skyrim installations, but even that doesn’t need much space and like already mentioned by Steam for the tiny shader files for certain games that support it. That is why the loadscreens in CP2077 only takes like 2-3 seconds. I mean it loads an entire game world just like that in 2-3 seconds. Fast travelling takes longer in CP2077 than the initial loadscreen to get into the game.
The actual caches get saved there: C:\Users\YourUsername\AppData\Local\Microsoft.ForzaMotorsport
There are several folders in there like CarThumbsCache, CMSCache and other stuff. But i think it also has something to do with the files in the game folder itself, not just in the AppData folder. I am too lazy to go through all that stuff.
I’m just going by cause-&-effect.
As I mentioned, with shader cache at 100 GB, the game always does a brief shader optimization at start-up - but without shader cache at 100 GB, the game always takes much longer for shader optimization at start-up.
That’s what happens when I change nothing else except that shader cache size setting in Nvidia Control Panel.
Maybe that’s not how it goes for everyone, but that’s what it does for me.
I’m open to other ideas for getting around the long shader optimization at game start-up.
I am just wondering, do you still use Windows 10 or is it 11?
Windows 11 Pro.
Steam version of the game.
Game installed on a 2 TB M.2 SSD.
1 Like
It’s just weird i never had this happening with my RTX 3080, that it keeps compiling shaders over and over again. It’s the CPU that does the compiling and i got a R9 5950x.
I think I saw you recommend (on a different thread) enabling v-sync in the Nvidia Control Panel while setting the in-game performance target to unlocked without v-sync…
…I tried that & it made a noticeable improvement in the stuttering I keep seeing, so thanks for that tip.
2 Likes
The shaders compiling only happened twice yesterday as I was playing around with the size, today when I loaded it up it didn’t do the shaders so it only happens for me when I make a change
1 Like