Volitions Advocate on 27/1/2011 at 20:29
Back in the day every joe schmo knew how to edit his autoexec.bat and config.sys file to make a boot disk so that he could move his extended memory into expanded memory simply so the executable for Tie Figher or Kings Quest would actually run......
We're PC gamers.. it's what we do.
Sulphur on 27/1/2011 at 20:51
There are two ways of looking at this.
A) I'm PC savvy, and the bug arguably doesn't make a difference to me. I find out what the fix is, force Vsync via my control panel. Many PC gamers do this stuff day in and day out. Big deal. People who can't deal can quit, the rest -- play on.
B) I'm PC savvy and found out how to fix this issue and I'm irate that I have to do this for a game that should work right as soon as I double click on the damn icon, or I'm not PC savvy, don't know what the hell 'forcing Vsync' even means, and I'm irate because my game's unplayable.
Problem with side A? Dead Space 1's bug was a bug -- it should have been fixed. It wasn't a trivial issue that was merely incidental or only affected a small portion of your playthrough; a mouse sensitivity bug is pervasive throughout the entire game.
It's not about how many hoops you had to jump through, even if it was only one. There was something fundamentally borked in the game on some people's PCs. It was a huge slip-up and it was something that needed to be looked at and mended.
If DS2 has the exact same bug and it affects the same amount of people again, someone somewhere wasn't doing their job right yet again, whether it's EA's customer support, programming, or QA teams, or all of them together.
Having said that, I never faced the bug, and probably never will. That's not the point. It's about the principle of the thing.
Digital Nightfall on 27/1/2011 at 21:13
Bioshock 1 and 2 did this as well. Remember the widescreen issue? Major facepalmage.
It's too bad I never knew about this problem/fix when playing Dead Space for the first time.
Bjossi on 27/1/2011 at 23:13
Quote Posted by gunsmoke
ATI Catalyst Control Center does the same thing Bjossi...
Forcing vsync there did squat for me and judging by Dominic White's comment in that RPS article I linked to, it wouldn't have worked/sticked any ways. But of course it is possible that I did something wrong, the CCC is some horrible piece of software to wade through.
EvaUnit02 on 28/1/2011 at 00:58
CCC is garbage. Do yourself a favour and switch to ATI Tray Tools already.
Bjossi on 28/1/2011 at 01:10
Sounds like a plan, ATT seems to be the popular replacement. I already downloaded the latest beta but now I'm wondering if it matters whether I install ATT before uninstalling CCC or vice versa. I really don't want to screw things up as I'm not quite as savvy as some of you guys.
Phatose on 28/1/2011 at 01:30
Ati tray tools just replaces the CCC. Neither it nor CCC have any effect on this game.
The problem is more substantial then just a google search and a checkbox check for Ati users.
The fix requires downloading and installing Rivatuner as a driver. However, rivatuner's driver is not signed - or at least wasn't when I had this trouble. That meant on Win 7 you couldn't install at all unless you completely disabled UAC.
That isn't really an acceptable workaround.
Bjossi on 28/1/2011 at 01:56
What worked for me was to install RivaTuner (Not sure how I would have installed it as a driver, didn't see that option in the setup.) and use the D3D Override tool that comes with it. I added a Dead Space.exe profile to it, set up the profile to force vsync and triple buffering, and voila; very responsive and stable mouse movement in-game, the difference is just staggering. I don't even seem to need RivaTuner, only the Override tool runs in the background doing its thing.
As for switching to ATT, after doing some reading this seems to be a lot more complicated than I thought, perhaps it would be best to start my own thread about that in the right forum.
Volitions Advocate on 28/1/2011 at 03:48
I dont' know what the trouble is. I'm using CCC and forcing Vsync works fine. I can't use any unofficial drivers anyway because I doubt they support grouping.
Phatose on 28/1/2011 at 04:52
That's odd. It's not working for me. Turn on vsync in game, 30 fps, no tearing. Turn it off in game, like 90 fps and tearing. Force it in CCC, and I still get tearing.
Bjossi, what OS are you running?
