Patch did not fix OpenGL issue

(Thatgingerkid) #1

Sad to report that this patch did not solve the issue with the OpenGL crash arising on Nvidia 4xx/5xx cards.
I am disappoint :(.
Not game breaking though, as I only get it every 3-4 hours of game play.

(Nail) #2

it wasn’t meant to fix that, that fix has to come from nVidia

(Thatgingerkid) #3

Huh. I figured it was on SD’s end cause I don’t have the problems in other games but now that I think about it I guess that makes sense.

(wuhlei) #4

Have you tried using the beta drivers?

(Ceej) #5

It didn’t help the AO issue either. Literally no change in framerate and same corrupted text. Literally NOTHING changed. I had to check and make sure steam actually downloaded the patch.

(Instant_Soldier) #6

Regardless of whether the patch was meant to fix the code 8 error (the changelog simply made no mention of it), this is pretty sad. SD lists 270.61 WHQL, the LATEST, as the driver to use. Which if you think about it is pretty strange. The latest driver, with a blaring hole in it for the latest nV cards, and no one at SD noticed? And NOW it’s nV’s problem?

Jesus! This is starting to feel like $50 down the tubes.

(Nail) #7

it’s both their problems, but nVidia is the only one that can issue official drivers,

(Ino) #8

You don’t have problems in other games because games rarely use OpenGL, most games run on directX :wink:

(Instant_Soldier) #9

What you say implies that the only possible fix can come from a new driver. How do you know this? Why can’t Brink be made to conform the latest driver and the latest cards instead? As near as I can tell there’s nothing graphically revolutionary about the game. SD didn’t test and that’s obvious.

270.61 is practically new, and I doubt nV is going to produce a new WHQL anytime soon for a single game. So this means I’m stuck with a beta, perhaps for a couple of months, to play a SINGLE game? :smiley: Right!

(McAfee) #10

[QUOTE=Instant_Soldier;321626]What you say implies that the only possible fix can come from a new driver. How do you know this? Why can’t Brink be made to conform the latest driver and the latest cards instead? As near as I can tell there’s nothing graphically revolutionary about the game. SD didn’t test and that’s obvious.

270.61 is practically new, and I doubt nV is going to produce a new WHQL anytime soon for a single game. So this means I’m stuck with a beta, perhaps for a couple of months, to play a SINGLE game? :smiley: Right![/QUOTE]

You do realize both ATI and NVIDIA release more driver revisions than video card models? They release drivers every time a new card is released (or series of cards). And they release drivers to fix bugs and optimize.

Typically, every time there is a new game, ATI and NVIDIA release drivers that claim fixes or say “improved performance of XY cards on this game by %%”. They come in at least BETA form, which pretty much means non-WHQL. WHQL certification takes longer cause it has to go thru Microsoft.

Every new software makes use of different calls on the driver and hardware, and there may be something that the driver developers overlooked. Sometimes, even old stuff that was working fine breaks.

You shouldn’t be able to crash the driver, or even worse the kernel, by just using API calls. The host of the api (driver/kernel) should be robust enough to stay running.

(Crispy) #11

Please use the following thread for discussion of this issue:
http://www.splashdamage.com/forums/showthread.php?t=24899