OP
OP
-
Ever wanted an RSS feed of all your favorite gaming news sites? Go check out our new Gaming Headlines feed! Read more about it here.
Forza Horizon 4 PC Performance Thread
- Thread starter SmartWaffles
- Start date
Dunno how MFAA looks but seeing that Transparency AA picture I would say the latter.
Also what kind of % performance hit does the Trans AA give about?
Last edited:
I can only comment on the demo and I also don't have the game ready driver installed yet. At ultra settings the actual bits where I'm driving the car or in a race are staying smooth at 60fps. The bits in between where the characters are out of the car and talking run at about 45-50fps and I'm really not sure what is going on there that makes it run that bad. I'm installing the new drivers now but I won't be able to test the demo out again until later today.
I've noticed that in the retail release during those scenes. Gameplay is stable 60fps @ 4K ultra but those 'cut scenes' occasionally drop fps
Oh, ok. I knew that the movies were locked at 30 so I really didn't know what was happening but if it's happening in the full game it could potentially be a bug or something.
This is true. However, Windows tends to only output HDR properly when also set to a native 4K output.
MFAA is a modification or override of how MSAA is rendered, not a seperate additional method.
I haven't used MFAA much, I'm curious to give it a try, but it seems to have some shortcomings.
I usually don't like these weird AA methods and like to stick with time-tested antialiasing techniques that provide reliable results.
I usually don't like these weird AA methods and like to stick with time-tested antialiasing techniques that provide reliable results.
I would love to get through the intro but I keep crashing in summer. Game freezes and then just closes....c'mon.
I'm getting less FPS compared to demo + game stutters for me. 11 stutters in the benchmark compared to 0 or 1 in the demo (noticable in the regular gameplay). What's even more weird, is that I had demo installed to 7200RPM HDD and full game is on brand new SSD. So, not a great start for me.
LOD is still bugged and textures are a blurry mess in the (relatively short) distance.
Gonna try new 18.9.3 AMD drivers. Currently on 18.9.2.
LOD is still bugged and textures are a blurry mess in the (relatively short) distance.
Gonna try new 18.9.3 AMD drivers. Currently on 18.9.2.
Are you forcing AF on driver level? Somebody in this thread reported that doing so on Nvidia caused the LOD bug, haven't verified it myself though.
No, it's set to application controlled. However, If I remember correctly from the demo, forcing 16x AF in the driver actually helped in my case.
Anyone using OBS and experiencing an issue with capturing the game and having it crash? I encountered this yesterday and I had thought it was due to upgrading the Nvidia drivers. But it seems that there's a conflict with OBS as another person also mentioned this.
https://forums.forzamotorsport.net/turn10_postsm963052_OBS-crashes-game.aspx#post_963052
https://forums.forzamotorsport.net/turn10_postst132878_Streamlabs-obs-crashes-game--PC.aspx
Which is odd as I had zero issues using OBS with the demo.
*Edit*. Now that I think about it more. I was fine when I was on the Nvidia 399 drivers. The new drivers caused issues, so I downgraded to 411.63 from 411.70. I'm going to go back to 399 and see if that helps.
https://forums.forzamotorsport.net/turn10_postsm963052_OBS-crashes-game.aspx#post_963052
https://forums.forzamotorsport.net/turn10_postst132878_Streamlabs-obs-crashes-game--PC.aspx
Which is odd as I had zero issues using OBS with the demo.
*Edit*. Now that I think about it more. I was fine when I was on the Nvidia 399 drivers. The new drivers caused issues, so I downgraded to 411.63 from 411.70. I'm going to go back to 399 and see if that helps.
Last edited:
Neat that you say this. I had the expereience were 399 drivers could load up the game with RTSS, then the drivers of 411-fame caused the game to crash with RTSS :/
Odd.
lol that is interesting - 399 is the shadow of the tombraider driver, right? that is what I used when it worked!So I rolled back to 399 and look what I get now.
Yep. Wondering if there was a patch that was slipped in. Because OBS still causes crashes on 399. It didn't before.
Going to test some other apps now. This blows as I'd use OBS -> NDI to my streaming PC. I mean I could use NDI's native tools, but still.
Game is unplayable at 30fps, input lag becomes horrible. The image is smooth but I can't control anything
OK, what the hell. SteamOBS and XSplit Broadcast also crash the game. I've tested this on two different PCs with two different Nvidia drivers. What the heck. This stuff was working on the demo and the first day I had access to the full game.
If someone is interested in performance @ 1080p on a meh GPU, then on i7 8750h, 16GB DDR4 (2x8 2400mhz) and GTX 1050ti, I'm getting an average of 59FPS in the benchmark on High, auto-scaling disabled. FPS is hovering around 80 later on in the race, but it's under 60 for a brief moment when the race starts.
Just like FH3 30FPS mode on PC. Try setting "Maximum pre-rendered frames" to 1 in Nvidia CP for FH4 profile. It might reduce some input lag.
That was it.
I upgraded to the new Nvidia drivers as they were released. Nothing else. But this is happening on two different PCs that were fine before. The most i can do now is install it on my kids PC (Ryzen 1300 + GTX 1060) and see if I can capture with OBS / XSplit.
Did you try to remove drivers with DDU just to be sure nothing stays with the new drivers?
OK, doing more testing it seems that PG/MS had to have patched the game and broke it. I fired up the demo on both PCs and OBS / XSplit work fine. The full game crashes when doing the same thing.
The streaming PC has the 411.70 drivers and it runs the demo with OBS without issue. I'm not going to downgrade the drivers on that. I'll give DDU a shot on the main PC to see if it's a driver conflict there. But I'm at a loss as to why the demo works but the full game does not.
The streaming PC has the 411.70 drivers and it runs the demo with OBS without issue. I'm not going to downgrade the drivers on that. I'll give DDU a shot on the main PC to see if it's a driver conflict there. But I'm at a loss as to why the demo works but the full game does not.
List of know issues : https://forums.forzamotorsport.net/...wn-Issues--Updated--September-27th--2018.aspx
So they know about the Nvidia AF bug and overlays crashing the game.
So they know about the Nvidia AF bug and overlays crashing the game.
Odd that Shadowplay, which is an overlay, does not crash the game.
Shadowplay runs at driver level I think, it does not get injected in the executable (which can cause instability), that's why it can appear in some apps too.
BTW it works really well in Store games to monitor FPS, take screenshots and record clips.
DDU'd the PC and it still happens. FH4 crashes as soon as OBS starts.Eh. Means I can't easily stream it on PC, I'll have to go through my capture card for now.
Don't force AF in the driver for this game, clear the game data cache in the Windows settings, Apps, select Forza Horizon 4, advanced options, clear data (or something like that).
It will clear the user files so it will redownload your save from the cloud and more importantly, it should rebuild the shader cache (tbh I did not try clearing this way, I deleted the files manually, but they are hidden so trying this is quicker).
Finally got home, super excited to play.
Game won't launch.
E: applied OC, closed Afterburner and RTSS, now it launches.
So in the end, is the best IQ with MFAA and transparency AA in addition to MSAA, or should I not bother with MFAA?
Game won't launch.
E: applied OC, closed Afterburner and RTSS, now it launches.
So in the end, is the best IQ with MFAA and transparency AA in addition to MSAA, or should I not bother with MFAA?
Last edited:
I wouldn't bother with MFAA, especially if you're not above 40fps at all times, in which case it'd actually make the image worse (ghosting).
I'm never under 40 fps ;)
Dunno if it's the new drivers, but it's running better than the demo so far.
Everything maxed except MSAA at 4x, 4x TrAA and MFAA. Only one frame rate drop (56) in the intro race, where it used to be 3-4 drops in the spring forest section.
That's at 1440p on a lightly OC'd 1080, 6700k stock 16Gb RAM and running off an SSD.
LOD still seems to be messed up though.
Need to add green screen when using HDR on game re-start. When I turn on HDR in OS first time and play the game, it's fine. If I exit the game and start again I get a green screen. The only solution is to turn the OS HDR off then on again. Probably an issue with the OS then the game but who knows. It's annoying all the same.
It's weird, AF looks screwed up even though I deactivated it in NVCP before ever starting the game.
Yeah, it's completely broken. This + LOD + VRAM memory leak and I'm close to giving up and going to my fat Xbone.
Just had my first crash after 3 hours of play. Great experience over wise, haven't had a single stutter.
Oh god that bug is still in? Same thing happened to me. I had to switch from my on-board sound to a wireless headphone device in my windows sound settings to get it to not crash.
I had never had any other game crash when using on my on board chipset.
Lots of other people having this issue as well. Crazy it wasn't fixed for release.
Copying this from the OT:
Just experienced an error about streaming, the track stopped loading in and the game gave a "low cpu bandwidth or memory bandwidth"..... I clicked okay and the game continued, wtf?
On a Ryzen 1700 3.9ghz, gtx 1070, 16gb of ram and an nvme samsung 970.
Memory leak?
Just experienced an error about streaming, the track stopped loading in and the game gave a "low cpu bandwidth or memory bandwidth"..... I clicked okay and the game continued, wtf?
On a Ryzen 1700 3.9ghz, gtx 1070, 16gb of ram and an nvme samsung 970.
Memory leak?
