set r_mapoverbrightbits higher (3+) and play around with r_mapoverbrightcap which was added with this update

This.

Someone in another thread mentioned the following:
r_mapoverbrightbits "5"
r_Mapoverbrightcap "50"
r_gamma "2"

That seems to be the way to go, at least for the moment.

lightmap

what noctis said

Why do so many people use vertexlight 1 ?

fps :<

Stable 125fps without vertex in q3.
80-125 with vertex in ql.

W T F

T..T

F ... F

yep, the worst part is that i didn't find out until very recently. i haven't used drawfps 1 in years... go figure.

welcooome to quaaaaake liiiiiiiive.

lol ye, i never noticed until i played Asylum for the first time. I mean, i knew something was "off" when fucking around dm6 in ca, just didn't know exactly what. Thanks to id doing such a bad job at optimizing it, i noticed the huge fps drops/fluctuations almost immediately (Asylum and Quarantine rape my fps the most, in some areas it goes as low as 50, rofl).

This has to be more than the bloody browser wrapper... what happened to the id that always made very efficient engines? :-|

wasn't always the case, used to be rock solid before release.
There's no point using vertex 1 postprocess 0 on my comp, I get the exact same drops than with vertex 0 postprocess 1 ( and as it looks better... )

You're right, during the early-to-mid beta i've never felt like there was something wrong, and i didn't even use vertex back then. Seemed like it got progressively worse towards the release. This seriously pisses me off. They had it working good enough, i wonder what did they do to fuck it to hell. Shit, even people with rigs worlds apart in power from mine are getting fps drops here and there. How the hell can a modern day pc struggle with an eleven year old engine?

just wondering, do you drop more frames with bloom on ? I don't seem to ( with lugia's settings iirc, I don't play with it on, just watched a few demos. )

The difference is marginal, at best. Was fiddling around with various gfx settings, trying to squeeze out as much fps as i could, and IIRC turning bloom off, for me, was 2-3 extra fps. Of all the settings, only finish, postprocess and vertex made any real dent in the drops i had.

with my current cfg ( and I don't think I can tweak anything relevant anymore ) I just get the same shit fpsdrops and constant 12x jittering at best from 640 to 13xx*whatever. Didn't bother to check further.
fps capped to 60 and 30 still give me the same kind of drops in terms of ratio.

I still prefer fullbright even after the update.. vertex is terrible in ql.

vertex looks much cleaner, and u get the look brighter, using mapoverbrightbits 1 too.

If you are using vertexlight, don't use mapoverbrightbits 1.

but then it looks like shit

everything was fine before the last update. then the retards at id had to go and ruin it. typical.

Its going to look like shit regardless if you use vertexlight, don't see how mapoverbrightbits 1 fixes that.

some people like the vertex + mapobb 1 look. is that so hard to understand?

the fact that now I have to exec a different cfg just to make some maps playable is not a welcome change

It might be late, but here's a pic that shows the effect mapoverbrightcap has and why it was introduced. This is with r_vertexlight 0, but same applies with it at 1.

http://img573.imageshack.us/img573/401/mapoverbrightcap.jpg