has anyone else found that your getting graphics problems ie error messages saying things like “low streaming error” or bits of the scenery just disappear ?
all i get with the new drivers is a headache if i use my main monitor for to long, and fps is locked at 80fps unless i go into windowmode. you can always DDU and go back to a driver that worked for you.
I can confirm his issues. It started right after I updated to version 440.97 and it disappeared when I rolled-back to previous version, 436.48.
Just like him, the game draws strange graphics errors such as missing elements of a scene (looks like a mirror or blank water surface) and then raises that “low streaming bandwidth” error. Races will halt (which ruins them, because the car stops immediately) – the problems come-up usually after 1.5-2 hours of playtime.
I am playing in WQHD at max settings using an i7-7700K and an RTX 2070 Super. I’ve been using these settings since I own this card without any problems. This definitely seem to be related to that specific driver version. I’ve talked to people on discord servers facing this issue also.
There are no critical values/events reported by hardware sensors (using hwinfo64) during game play or right after this happens.
I have reported the problem to the Forza and Nvidia Support units.
Didn’t encounter with GTX 1080 Ti, same WQHD (2560x1440) with every graphic setting maxed out except FXAA.
And “Antialiasing - Transparency” in the nvcpl is set to “4x (supersample)”.
While you didn’t mention your target frame rate… mine is set to 30 FPS. (which might be the cause)
Update:
Still cannot reproduce even had the game running for a whole night…
I dunno what’s going on at nvidia these days but different versions of their drivers have messed-up both FH4 and FH3 several times in the last year causing either major glitches or even the game to lock-up entirely. SMH.
You might be better off on 431.60 then, there are some users reporting rainbow colour issues in CODMW with this driver as well, though i have word from one player that they only occured with VRAM overclocked.
It does not tell if the issue is fixed and I don’t wan’t to lose time to update and check and rollback if it’s still there, I can live a few days with 436.48.