try messing with

r_overBrightBits
and
r_mapoverBrightBits

tnx i'll give it a shot.

r_mapoverbrightbits "1" is the only value which allows you to see properly on every map.

i use r_mapoverbrightbits "3" and now i tried r_mapoverbrightbits "2" on t4 and t9 looks perfect.:) tnx boyzz:D

not really.

lowering "r_mapoverbrightcap" can also help.

r_forceambient 0.3!

0.15! <3

0.1 and gamma 1.75 (or was it 2?)! fojji style!

gfx

that's not q4!

t6 is black with r_mapoverbrightbits 1 :x

since most maps became broken after they changed vertexlight stuff few updates ago.
with the last update some maps like ironworks have been fixed and reuploaded, but while they've fixed all maps id software are delaying some of them like t6, dm7, ospdm6 and others till the next update being afraid of a sudden bandtwidth overload :S
im just using vertexlight 0 on them with the same bits/cap/intensity/etc as on other maps and it looks fine

yes I know, its ridiculous.

yup, once this one's fixed (and whichever others) i'll be switching from mapoverbrightbits 12 to 1/2. if it's true that they're just withholding the updated maps they really should just release them..

12 is same as 3..i use 10 just cuz i copied it from sm cfg

be a man and use picmip 0/vertex 0

._.

LOL afkors...

be a man and stop playing t9

i just gave it as an example.. also the map is fine. u got assbanged to many times on it or...??

its a boring tele and rl/pg +back spamfest, designed for insecure quake fanboys who think annoying your opponent for ten minutes constitutes brain

although I don't see why he doesn't like it since he doesn't like aerowalk either

i'm a newb so.....4 newbs every map is fine..it's not like i'm going pro or smth.

be a man and stop playing t9 t4

fixed that for you

r_mapoverbrightbits 10
r_mapoverbrightcap 100
gg

r_mapoverbrightcap??? what does this do exactly?

http://www.esreality.com/index.php?a=post&...pid2011462

In quakelive, high mapoverbrightbits value + high picmip value = possible disaster.

i couldn't open the pic before..hmm..nice. i'll just keep on using default r_mapoverbrightcap and i'll just use r_mapoverbrightbits 2. + for u sir

heard of google? ;)

* Added r_mapOverbrightCap (Default 255, <0-255>): Allows you to cap the brightness of surfaces brightened by r_mapOverbrightBits (Most useful when using high values of r_mapOverBrightBits; vid_restart required after a value change).

this tells alot lol...

huh? it tells you exactly what it does?
what mroe do you want to know? or what of it dont you understand?

it keeps surfaces from being too bright

u have r_mapoverbrightbits for that,. why would you need smth like this?

no, not at all

different parts of the map are differently bright

it tells exactly what it does. if it's not completely clear see the difference between 255-155-55 ingame.

tried it.tnx guys

r_mapoverbrightcap 145
r_mapoverbrightbits 8

Stop using vertex, it's never been close to q3 anyway.
Problem solved

but the framedrops

2011.
I'm pretty sure most people who drop frames wouldn't drop more using vertex 0 ( there would be no difference at all for me )

Not true.

I have a Q6600, 4GB DDR2 RAM and a 4870X2 and I get frame drops on quarantine/asylum when using vertexlight 0; as in 125fps to 20fps...

vertexlight 1 gets rid of these framedrops.

well, even sens doesn't make any in this game anyway.

...

Yes, I did dare.

r_mapoverbrightbits 5
r_mapoverbrightcap 160
r_gamma 1.3