No shit. One look at the screenshots that went up in that thread yesterday told me it was a driver issue.
Game isn't broken. While this is unfortunate, it just is not uncommon at all for a game to have driver issues on release.
Omitting graphics options is incredibly lame but, again, it isn't new and there are workarounds.
After initial interest I won't be picking this up, mostly due to the long development cycle and waning interest over time. Also that dodgy used sales business and general bad vibes leading up to release.
There are mixed reviews out there but damn, these problems are temporary and are out of id's hands.
Before you get all sky is falling, lazy console ports blah blah blah... I'm actually one of you.
But driver issues? Really? I know it sucks, I've been there, but it IS only temporary.
Bioware still gets my 2011 award for biggest kick in the nuts to a legacy.
Edit: Wondering who Blizzard's competition will be for next year's award.
*Disclaimer* Written in jest.
kiri2tsubasa said:
This is what I see every time they try to play it on PC.
Rage.1683.2 win-x86 Release Oct 3 2011 11:22:59
---------------------------
1 CPU package, 4 cores, 8 total logical processors
2 MHz Intel CPU with MMX & SSE & SSE2 & SSE3 & HTT & EM64T
32768 kB L1, 262144 kB L2 cache, 6291456 kB L3 cache
6080 MB System Memory
0 MB Video Memory
What is this I don't even.....
Driver issues. Quick google search shows that Nvidia's latest help a bit but the issue isn't solved yet.
Hang in there guys. Hoping to see some honest, unbiased, user reviews appear soon! If anyone has done or is planning one then feel free to quote me here.