• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Fallout 4 hindered on AMD cards by Gameworks > FIX

Soldato
Joined
12 Mar 2006
Posts
23,007
Location
N.E England
Just incase you AMD guys haven't seen this,

I have Fallout 4 and running on Ultra on my 7970's it was being crippled at times, yes we know crossfire isn't working yet but neither is SLI!

A profile for that will come..BUT there is a way to dramatically increase your performance and almost double your FPS, by disabling those silly Gameworks features..

Volumetric Lighting set to 0 and God Rays set to 0.

Fallout4.ini -> God Rays
Fallout4Prefs.ini -> volumetric lighting

Set your tesselation to 8x aswell in CCC

Hope this helps until AMD figure out how they can render those effects properly (if at all)
 
Guys if you lower those effects in the Menu it doesn't seem to completely disable them and still hinders performance, change them in the ini to a 0 value. It definitely feels these features were pushed by NV to cripple our cards!
 
Poorly optimised / not at all for AMD. Quick fix to make it playable until AMD pull their finger out. How many times have we had this with various titles

How do you know they're not optimised? Maybe the effects just are just hard to do and the performance hit is what you'd expect?

It looks like upping the 'grid' value/count seems to have a big impact too and I doubt that's GameWorks. Some things will just cost performance and it's not a massive conspiracy!
 
These effects aren't exactly ground breaking they have been round for a long long time

but if they're not in the engine how do we know how hard they are to do in this engine using another method?
What are you comparing the performance hit to? Not doing the effect? Hardly seems fair.
Surely you need to compare it to the effect being done in the same engine using another method before you can claim that it's GameWork's implementation causing it. Unless you're just looking for a reason to throw **** at Nvidia?
 
Back
Top Bottom