There's definitely a problem as some noticed 80% underutilization on their 1070's.

Loophole35:

Just testing the game out. Core0 bug is still there. FPS locked at 60. I'm calling all kind of BS on this "article".

On my Desktop with Titan X (Pascal) and laptop GTX 1080, my framerates do exceed the monitor's refresh rate, no matter if at native resolution or DSR. I have Performance Target set to Unlocked in Forza Motorsport 7 (full version Ver. 1.106.2356.2, not the demo, so perhaps the Demo is based on an older build). I'm on Windows 10 1703 with the latest updates and using the 387.78 Nvidia drivers (not the game ready ones). The only problems I have is that the framerate tanks during some pre-race menus and victory celebrations (there seems to be a 30 FPS limit in place for some of those). Then again, I'm not using the latest "Game Ready" drivers and have no driver profile for the game, so perhaps those would solve these issues (Update: Tried the 385.69 Game Ready driver, made a little bit of a difference in menus if any at all, so I went back to 387.78 after yanking the updated profiles from the Game Ready driver on the way). I'm not sure about the Core0 bug, I can get several Cores running at close to 100%, depending on the resolution and traffic, but it's mostly less. Core 0 isn't locked at 100% either. The GPU usage is high, too. The game feels smooth (especially when enabling GSync on my laptop, but also without GSync on the desktop although it's slightly worse), framerates are pretty consistent and I haven't observed any stuttering except when the framerates tank in some of the menus. Except for the menus, the game performs roughly the same as Forza Horizon 3 (latest version) on both systems for me (using maxed out custom settings except Anti-Aliasing set to 4x at UHD resolution).

How are you playing on windows 7? Latest drivers are 385.69. You have a driver from 5 months in the future?

Denial:

I mean the Ti is only running 25% faster than a 1070 in FHD, there is clearly some kind of CPU issue. Vega is performing nicely though compared to the rest of AMD's stack, so it seems like the game is well optimized for it. The article states there is a CPU comparison benchmark but I don't see it?

I wouldn't read too much into this early benchmark. There are so many issues with the PC version of this game and this benchmark is a proof of that. It took them nearly a year to fix Forza Horizon 3 so hopefully it won't take as long with FM7.

Loophole35:

How are you playing on windows 7? Latest drivers are 385.69. You have a driver from 5 months in the future?

Heh, the 7 was a Freudian slip, playing on Windows 10 1703, obviously. Sorry Forza Motorsport 7, Windows 10. Fixed the post. 😛 The driver is the Nvidia 387.78 driver from the latest Windows 10 1709 Insider Preview Windows Update. The driver works just fine in 1703 (actually, best driver I have used on 1703 so far). You can download it in a nice installer package courtesy of @Cyris here on the forums. Good to see the game perform so nicely on AMD hardware, by the way. Looks like there is still a lot of untapped potential under the hood of the Vega chips, if games are optimized properly for them. I expect Nvidia performance will go up a bit eventually, but still, it's good to see AMD perform strongly.

I think I have a good explanation to what it is happening.. And I'm not sure if I'm the only one. But I tried the demo, and I didn't had any Core 0 at 100% (I do use AMD GPU), altough I've been noticing many youtube benchmarks with nvidia GPUs with MSI AB overlay, and most of them if not all, shows a core with 100%. Can this be a problem specific to nvidia only? Are AMD free from this bug or lack of optimization? I've made a benchmark video with my system, and you can see that I don't have a Core locked to 100% [youtube=cyfBRl0SdSY] Cheers

More playing around with the game. I don't know what I did but framerates unlocked for me. The Core0 bug is really maxing 2 threads out one main thread on core 1 and one HT on core 2. They both pretty much stay at 100%. Not sure it this is driver or game. My bet is game.

Cave Waverider:

Heh, the 7 was a Freudian slip, playing on Windows 10 1703, obviously. Sorry. Fixed the post. 😛 The driver is the Nvidia 387.78 driver from the latest Windows 10 1709 Insider Preview Windows Update. The driver works just fine in 1703 (actually, best driver I have used on 1703 so far). You can download it in a nice installer package courtesy of @Cyris here on the forums.

Could you monitor what core 1 and core 4 are doing on your end also what is your GPU usage?

Loophole35:

More playing around with the game. I don't know what I did but framerates unlocked for me. The Core0 bug is really maxing 2 threads out one main thread on core 1 and one HT on core 2. They both pretty much stay at 100%. Not sure it this is driver or game. My bet is game. Could you monitor what core 1 and core 4 are doing on your end also what is your GPU usage?

Seems drivers issue. TWW2 at DX11 with GTX1080ti and 6800K at 4.3 (with uncore at 3.75) is using core 6 and 5 at 100% and 75-100% respectively, while cores 1,2,3,4 are between 25-60% usage. The HT threads are at 0-3%. At DX12 the core 6 still is at 100%, core 5 hovering between 40-50, other cores between 20-30% and fps tank by 35% compared to DX11. That at 2560x1440, with everything on Ultra, and 2x AA.

It's not often you see Vega 64 at the top of the graphs.

Wooow...Performance is par for AMD...Seeing first time ever...i think driver problem for Nvidia

sunnyp_343:

Wooow...Performance is par for AMD...Seeing first time ever...i think driver problem for Nvidia

Its Dx12, maxwell being.. ass and pascal slightly less ass - expected, could 've told you that before the game/demo was out.

Alex13:

Its Dx12, maxwell being.. ass and pascal slightly less ass - expected, could 've told you that before the game/demo was out.

A little more to it than that. This game uses Fozatech engine under DX12 same as Forza Horizon 3. Performance should honestly be better on this game compared to FH3 as it's not sandbox and less cars (I.E. no traffic). T10 will get it fixed FH3 plays great. I can hold 90FPS currently maxed out res scale at 100% In race is not bad and I have yet to notice any hitching but the menus are a different story. Just worried about seeing two threads pegged at 100% while the other 6 threads hover around 35-40%. Hope it won't adversely affect online.

I think its a driver or game problem . RX 580 and a fury faster then a GTX 1080 Ti. And the performance between some GPU's are so close with so much difference in CU's and cores. There is someting wrong. Also i can not play the game.

zero_cool:

not bs this.. Software vs. hardware schedulers in DX12. AMD can actually send commands to the GPU hardware schedulers on any thread in DX12 where they were limited to only the main driver thread in DX11. Starting to see the benefits of the hardware schedulers AMD uses. here you go

This only explains AMD's higher than normal performance, it removes the bottleneck specific to their architecture. On the Nvidia side, the cards are clearly not being utilized at 100%. A 1080Ti is not 25% faster then a 1070 - it's significantly more. And that limitation isn't something in Nvidia's hardware. The hardware might require a separate render path for Nvidia, maybe even one that's potentially is harder to manage than AMD's, but it's not impossible because other developers have done it and Nvidia does it in every DX11 game. To me this is an example of AMD's console presence paying dividends across their product lines. What sucks is in the past Nvidia could do something to fix the implementation for the game dev - with DX12 it's all on them.

Denial:

To me this is an example of AMD's console presence paying dividends across their product lines. What sucks is in the past Nvidia could do something to fix the implementation for the game dev - with DX12 it's all on them.

So nothing fixable on the driver or game level? Then seems we have to wait for Volta for more capable DX12 performance.

It's very rare I even consider playing a game with V-Sync off. The tearing is unbearable in some games and also, V-Sync on always feels smoother overall. But I don't play competitive shooters so I don't care about the small amount of input lag either.

RzrTrek:

It's not often you see Vega 64 at the top of the graphs.

Its the instruction prefetching.

Loophole35:

Latest driver claims game ready but I was able to start it with 385.41 which is the one that G-sync works on. If the game is freezing when it goes full screen at the start try alt+enter when the window first comes up to fullscreen then hit enter to start the game.

I don't think game ready means you can only run the game with that driver or drivers following that. Interesting results, but the next Geforce driver should see some tunes, or maybe a patch for the game. Anyway, nice to see the Vegas doing so well.

BReal85:

I don't think game ready means you can only run the game with that driver or drivers following that. Interesting results, but the next Geforce driver should see some tunes, or maybe a patch for the game. Anyway, nice to see the Vegas doing so well.

Last time around Forza Horizon 3 didn't want to start with an older driver.

sounds like a poorly optimized game.