That’s weird. I have a 6700K and 1080ti running on a Gsync monitor with no issues. I mean, the Demo isn’t perfect; it starts off windowed and I have to ALT+Enter to fullscreen it, but it’s usually fine after that. I have everything set to maximum, but I have motion blur and lens flare disabled. I can run the windows game bar recording software while racing, and it runs fine. Here is a video I recorded.
Edit: Make sure in Nvidia Control Panel under Manage 3D settings, that you have the following settings:
I don’t usually post here, but hopefully this will get some developer attention.
The game is not limited to only using one thread, it just puts most of the CPU load on a single thread.
It also seems that once you have enough cores/threads available, it starts putting that load on two threads instead of one - though I’m not sure that’s actually doing anything to improve performance.
I get extremely bad stuttering, frametimes, and low GPU usage when running the demo in its default state on my PC.
- Ryzen 7 1700X at 3.9GHz
- 32GB DDR4-2666
- 8GB GTX 1070 Strix OC
- 1TB Samsung 960 Evo NVMe SSD
This system should have no trouble running the game when it manages to stay locked to 60 FPS on an Xbox One with its low-power Jaguar CPU.
Windows 10 is fully updated (Creators Update, not insider builds), and all drivers are the latest available - including the latest NVIDIA driver with a profile for the game.
The game has basically the same problem as Apex, and Horizon 3 before “threaded optimization” was patched in.
- With an 8c/16t CPU, I see two threads almost fully loaded rather than one, with a small amount of work being placed on other threads.
- Enabling Game Mode in Windows 10 CU doesn’t seem to work correctly as it moves most of the work onto the first four cores. This makes the stuttering problem significantly worse.
- But if I enable Game Mode and then set Forza’s process affinity so that it does not have access to the first 25% of the available cores, it forces the workload to be more spread out. This makes the game run much better than before.
2 Likes
Ok guys, I think I have found the source of all our issues.
It’s GAME MODE - because the game utilises one core @ 100% and GAME MODE elevates the game exe priority as well as other things it is basically like running a HIGH PRIORITY stress test on one core while you game.
Turn off GAME MODE for this game and it’s back to being smooth for me.
Hope it works for you guys as well.
I tried this because of LTT video where they saw a real performance impact when game mode was on in some games.
Remember to restart the game after you disable game mode in the settings bar.
Win.
I wouldn’t be surprised if the majority of people who have issues is because of the Windows 10 creators update that Microsoft has acknowledged does make games stutter.
I’ve run it on 2 PCs now and I get no issues. Guess I got lucky.
i5-4690K@4800MHz
16GB DDR3@2400MHz
GTX 980
SSD 256GB (game here)
Resolution 1920x1080@60Hz, Settings Recommended - High…
Windows 10 Pro ver.1703 (15063.608)
GeForce Game Ready Driver 385.69 WHQL
load core #0 - 100%, stuttering pictures in the menu, and sometimes in the race.
Hi all,
Just following up here, regarding the “one core” issue that made the rounds yesterday. There’s been an update to that WCCFTech story with some further clarification from our chief software architect, Chris Tector. Here’s the quote:
"Forza Motorsport 7 is not limited to running on one core. There seems to have been a miscommunication along the way. Forza Motorsport 7 uses as many cores as are available on whatever system it runs on, whether that is a 4- to 16-core PC or the 7 cores available on Xbox One.”
Thanks,
Brian
2 Likes
Ha ha ha, what a PR blunder of note!
From people’s experience of the demo, it doesn’t seem to use that many cores. This implies that the retail version is different. Why not just say that? Why not just say that it is an issue that affects the demo only?
EDIT:
From the wcctech article:
2 Likes
That is a great relief, if the final game does indeed use all cores like FH3 does (aka ‘‘Threaded Optimization’’ option). There’s no logical reason for this not to be the case, yet I’m still a bit skeptical…
Thanks for the clarification.
EDIT: Also, I got to wonder, why don’t you confirm that demo is a different build that the full game, where the issue isn’t prevalent. IF that is the case ofcourse, if not then you should do the same as you did with Horizon 3 to fix it.
1 Like
Hi Brian, that update does not help the situation. This has been an issue with Forza on PC since the beginning. This was not fully fixed in Apex, but was fixed in FH3. There needs to be collaboration with the Playground Games team to get the stuttering issue resolved for FM7. This is extremely important. Forza has always been known for its quality frame rate and frame pacing on console. This stuttering on PC is not quality… it’s garbage. PC is a superior platform and these optimization issues are unacceptable.
5 Likes
But this Chris guy is arguing semantics and not fixing the issue. To clarify, the issue is HOW these cores are being used. CPU usage is not optimized as Horizon 3 was. I would like more clarity regarding this issue. It’s hard to trust in Turn 10 after so many disappointments on the PC platform. So I remain skeptical until the issue is fixed. We would like Turn 10 to share with us the following info:
- Is the demo based in the final build of the game?
- Will we encounter the same CPU performance issues in a couple of days when the final version of the game is released?
- If the final version of the game has the same issues, are they going to take action and fix them?
- If so, how long would it take?
3 Likes
If it does utilize more than one core it should run very smooth on my pc at 1080p.
i7 4770k
GTX 780
16GB ram
Game stutters like crazy. Regardless of the settings. Pretty much unplayable. However on my Xbox one the game runs very smooth. Which is funny because the Xbox has half the procks sing and GPU power of the PC. Core 0 stuck at 100% the rest at 15 to 30%.
I’m really hoping final release is better. Just sharing my experience.
I don’t understand… This demo is the only version of the game who suffers from one thread issue ??
1 Like
I’ve decided to check how’s things, and apparently this single core thing kicks in after i did the benchmark, and it remains throughout the menu, but in racing it actually runs just fine. I don’t remember if the single core thing happened in racing back when i posted this thread.
After the benchmark
While racing
Because you have i3. 2 Core, 4 Threads.
The game in the race loads on i5 really 4-core
Core # 0 - 100%
Core # 1 - 26%
Core # 2 - 70%
Core # 3 - 15%
But stuttering is still going on, albeit rarely. In the menu of stuttering more.
dynamic render set to ultra, res: 3840x2160 (1680x1050 monitor) , dynamic opt: custom
6800k underclocked to 2.2ghz
32gb ddr 3000
gtx 1070
1tb 950 evo
I do not have a Highend PC by any means, but it is above average I guess:
AMD 5350 @ 4ghz
16 G or DDR3
R9 290X
EVO 850 SSD
3840x2160
Other than some slight stutters in the menus, the demo runs flawlessly while racing. I think the secret to that is Game Mode is disabled and the DVR is turned off. Those were the tricks we used in Horizon 3 and I turned them off before I even tried the demo.
Comparison.
1 Like
Holy crap. Game mode destroys the performance. I never tried it, as soon as I got the update I disabled every thing and all dvr/Xbox options on my pcs.
DVR - OFF, Game Mode - OFF, V-sync in NVIDIA Control Panel - OFF.
i5-4690K@4600MHz
16GB DDR3@2400MHz
GTX 980@1400\7000MHz
SSD 256GB (game here)
Resolution 1920x1080@60Hz, Settings Recommended - High…
Windows 10 Pro ver.1703 (15063.608)
GeForce Game Ready Driver 385.69 WHQL
‘Built from the ground up for PC’… yet stutters on the best CPUs money can buy. This is hilarious.
3 Likes