There are some regression in the latest patch because sound is off in specific maps and there are invisible players again.
At least the performance is still nice like since 7 days ago.
Configuration: Q6600, GTX280 - 275.27 Beta drivers.
Friday 27 Patch - Regressions
Spectre-7
(Spectre-7)
#3
I’m running non-beta video drivers (Nvidia’s 270.61 WHQLs), and have seen the exact same bug regressions. I had sound cut-out a few seconds into Refuel, and had invisible players in 2 out of 3 rounds today, which are problems I haven’t seen since the release of the patch before this one.
Windows 7 64-bit
Athlon II X3 455 (Rana)
4GB DDR3 1333MHz RAM
XFX Nvidia 9800 GT 512MB
dlux
(dlux)
#6
Anyone else thinks Nail should just stop posting?
You post in every topic to change drivers, it’s the game thats bugged.
Crashes happen with every single driver.
I have tried every driver from 260.99 to 275.27 beta.
It is a fact that none of the drivers currently released fix any of the Brink issues.
Nail
(Nail)
#7
sorry, my mistake, I was reading the nvidia blog and posting on both forums and got the numbers mixed
Nail
(Nail)
#8
[QUOTE=dlux;326470]Anyone else thinks Nail should just stop posting?
You post in every topic to change drivers, it’s the game thats bugged.
Crashes happen with every single driver.
I have tried every driver from 260.99 to 275.27 beta.
It is a fact that none of the drivers currently released fix any of the Brink issues.[/QUOTE]
the patch today was to correct the bug using the latest drivers, not previous drivers, if you have anything constructive to say, please carry on
dlux
(dlux)
#9
Don’t make me laugh, a patch that only should work with specific drivers? Come on, where do you get your info.
I’m running 270.81 currently, and I still crash.
I crash with 270.61, 275.27, 270.80, 260.99.
You’re trying to be a techie, but from your postings its too obvious you have no idea what you are talking about.
Jekt
(Jekt)
#10
the patch today was to correct the bug on the latest drivers, not previous drivers, if you have anything constructive to say, please carry on
You’re the most useless contributor here.
Instant_Soldier
(Instant_Soldier)
#12
So, this leaves us hoping for a another patch, to correct the last patch, and still waiting for a hotfix from nV. I just played solo for about an hour with no code 8’s using 270.61. Is there a particular time to play before some of you guys crash, or is it random?
McAfee
(McAfee)
#13
[QUOTE=marakaid;326195]There are some regression in the latest patch because sound is off in specific maps and there are invisible players again.
At least the performance is still nice like since 7 days ago.
Configuration: Q6600, GTX280 - 275.27 Beta drivers.[/QUOTE]
I see this topic slowly deviating. Let’s get back on topic.
The regressions you talk about, were not addressed on the February 27 patch. And some people were already reporting the issues still existing right after the patch that was supposed to fix it.
So it’s not really a regression of the latest patch, it was just never 100% fixed.
As for drivers, crispy keeps the stickies updated with the latest suggest drivers, at the time of this writting the 270.61 WHQL (April 18)
The 275.27 BETA (May 17) don’t really address Brink specifically. Judging by the release notes.
marakaid
(marakaid)
#14
[QUOTE=McAfee;326513]I see this topic slowly deviating. Let’s get back on topic.
The regressions you talk about, were not addressed on the February 27 patch. And some people were already reporting the issues still existing right after the patch that was supposed to fix it.
So it’s not really a regression of the latest patch, it was just never 100% fixed.
As for drivers, crispy keeps the stickies updated with the latest suggest drivers, at the time of this writting the 270.61 WHQL (April 18)
The 275.27 BETA (May 17) don’t really address Brink specifically. Judging by the release notes.[/QUOTE]
Ten days ago I was just trying to play the game and those were the latest drivers my card was using when the “great patch” came. With 270.61 WHQL problems were the same.
“Great patch”: three steps forward: sound, performance, invisible players.
“Friday 27”: two steps back: sound, invisible players.
Still waiting for: garbled text.
Until yesterday, this has been a nice week playing Brink with that configuration.
Instant_Soldier
(Instant_Soldier)
#16
Nope. I see it too and Brink is running great for me now. Did the OpenGL patch correct the Code 8 error for many of you guys?
marakaid
(marakaid)
#17
Forgot to add this:
sometimes I can see partial grids, a small version of the horrible effect ATI cards used to display in the first day of the game.
Crispy
(Crispy)
#18
There are two invisibility issues that were reported. One was that your entire team can become invisible. The other is that select players can become invisible but only to certain players. Both issues are currently being investigated.
There are two specifically-multiplayer audio issues that were reported. One was typified by voice audio looping over and over for 30 seconds after which only the ambient sounds could be heard. This is the one that should be fixed (if not, let us know). The other is a case where the user gets a pop (like plugging in a speaker) and then absolutely no sound can be heard at all. That issue is still being investigated.
There are separate audio issues reported that are not specific to multiplayer. These are being tracked elsewhere in their own threads.
marakaid, please report your grid issue with screenshots and a DxDiag in a new thread.
You can read the patch notes from Steam > Brink > News > Product Updates. If there is a regression (i…e. something claimed fixed that is not) based on previous patch notes, let us know in the main thread for that issue, or failing that start a new one.
I’m closing this thread because I see no evidence of actual regressions and regardless of the good-natured intentions, it seems to be creating some misinformation.