Aw, missed opportunity for a winning thread title!
You should have gone with "Rage rage dooms Doom!"
That fully has win all over it

Aw, missed opportunity for a winning thread title!
You should have gone with "Rage rage dooms Doom!"
I dont see what the big deal is, i thought Rage was pretty good, mind you most of the people complaining still live with their parents and/or have no real job i.e Nerd Rage.
most of the (technical) issues are fair and squarely AMD driver fail but as usual the AMD camp would rather blame it on something else.
Really? last i checked on the hard ocp forums there were nvidia driver issues with the game, but as usual you would rather look through your nvidia sponsored glasses and blame only one vendor.
Do you ever tire of being a shill? Your rhetoric is getting incredibly old to say the least.
Who really knows eh?. Maybe this is a get out clause or an easy letdown for the pc gaming community from zenimax?. Carmack said it himself - console is the leading platform.
Recommended specification for Doom 4.
A gaming Console![]()
I think the evidence speaks for itself... so back down.
On release the game came completely apart for many mainstream AMD setups.
What "evidence"? Ever since i got the updated driver ive had no issues, yet you seem to assume that any issue people with an amd card has is down to the video drivers when its obvious theres tons of other factors that could come into play. Funny how that doesnt come into your mind though, when you see a chance to do a sad little amd "bash" you take it.The fact that the game couldn't even create its own cache directory should speak volumes to the fact that it had issues on launch that weren't video card specific.
Luckily i just bought it through steam, played and really enjoyed it, no tweaks, no driver updates, it just worked and i have an all AMD system ^^
- Implemented workaround for AMD driver crash right after intro cinematic
on Win 7 32-bit systems.
- Disabled UBOs because they are causing animation issues with AMD drivers.
- Don't allow swap-tear to be enabled on AMD while the extension is not
exposed because it may crash.
- Using a NVIDIA graphics card on Windows XP 32-bit or XP 64-bit, you
may experience a crash or hang when changing the screen resolution in
full screen mode or switching from windowed mode to full screen mode.
This has been identified as a graphics driver problem. We have spent
significant effort trying to work around this problem and were
successful in reducing the frequency of occurrence but a driver update
is necessary to completely fix the problem. We are actively working with
NVIDIA to make a solution to this problem available as soon as possible.
- Using an AMD graphics card, you may experience black flickering
artifacts on flags, banners and zip-lines if you run in full screen
mode. This has been identified as a graphics driver problem. We are
actively working with AMD on a solution to this problem.
- Using an AMD graphics card, you may experience black grid lines on
some graphical user interface (GUI) elements like the in-game mini-map.
This has been identified as a graphics driver problem. We are actively
working with AMD on a solution to this problem. If you find the grid
lines particularly distracting, you can add the following to the RAGE
launch options in Steam as a temporary workaround.
- If you have an AMD graphics card with a dual core CPU system you may
experience severe hitching and low frame rates. This has been
identified as a driver problem. We are actively working with AMD on
a solution to this problem. As a temporary workaround you may add the
following to the RAGE launch options in Steam:
We are actively working with AMD on
a solution to this problem.