are the Horizon 3 and other recent anomalies just poor optimization or will memory bandwidth soon become a non-meme issue for traditional PC users
>>58297888
>Horizon 3 runs near perfectly on my ancient six core Xeon and R9 Fury Nitro
>seeing people with 6700Ks and 1080s complain about performance
>mfw
That's what you baka-ass motherfuckers get for buying 4 cores and Nvidia in
>current year
Man I really wanted to fucking get this game on PC but it has so many issues.
>>58297888
>2. You will immediately cease and not continue to access the site if you are under the age of 18.
Horizon 3 runs buttery smooth on my PC. i5-4570S and R9 Fury on high settings/1080p. It sometimes dips below 60 FPS, but that's usually in the city area with lots of other cars on-screen.
>>58297888
Isn't that game only 30fps max on a xbone?
>>58298625
Yes but on my fx-6300/270x setup I can't even achieve that.
i5 4690k @ 4.4 with 16GB ram and r9 390 nitro
get about 40-50fps with auto optimization on high. it might dip below that in the city area but honestly the "auto optimization" is so random
outside of city areas i might go into 80 and 90 fps
the most vram i see it use is about 4.5GB and the game rarely crashes
pretty happy with it desu
>>58298714
Those specs are worse than an xbone
>>58297888
>Poor optimization
That shit runs perfectly on my 6700hq / gtx 1070 laptop on my TV @ 4k. The worst dip Ive seen is into the 40s in one section of the city.
How many thousands of dollars of hardware do I have to throw at Forza to get it to stop going below 60fps?
1080p, 1440p, minimum settings, maximum settings, I could adjust it to run at 120fps average and it would still stutter painfully
1070 and 6600K here
>>58299171
And 16GiB of 3000mhz ram, since that's fucking important for games apparently
>>58298414
>near perfectly
>near
Nobody is safe from microsofts shitty code