Bloom reflection effect

[fromhell]

look what I hacked up


Obviously too distracting for a default option, it's actually quite a simple tr_bloom.c edit

[Cacatoes]

Looks sunny and warming, though a bit imperfect and overdistracting as you said. Liz would love it.

[Udi]

Can you filter it by source? The reflection coming from the skybox is neat, but the flag and explosions seem unrealistic.

[Gig]

Very nice, it looks better than classic lens flare... but maybe it is distracting (more items cause bloom than lens flare).

[Graion Dilach]

I love that effect.

Distracting but nice.

[WingedPanther]

Looks cool, but I would immediately turn it off, just like rocket smoke

[dbX]

The effect is cool, but it should be only limited to sky boxes and some other light sources, not rockets and grenades and such because it's really weird and distracting.

[fromhell]

This is the new bloom function (combined with tcpp's cascaded bloom)

http://openarena.ws/crap/tr_bloom.c

it's a bit of a mess. What i'd like to do is use one more bloom texture with only the skybox and flares, with some depthwrite/read magic

[fromhell]

is oa too dark?

[Gig]

is oa too dark?

Unlplayable, but nice "trip"...

[dbX]

is oa too dark?

Look at all those pretty colors With this oa goes from "too dark" to too colorful, but unplayable.

[Cacatoes]

Ehe, that's experimental, I like it. The railgun hum is sweet, saturation gives analogic warmth.

Consider making the videos public.

[WingedPanther]

reflection bloom would give me a headache.  Ouchies.

[Gig]

Talking about Bloom ("classic" bloom, not the new effect Fromhell proposed above!)... I just tried with latest executable (22) and OAX (B50), and two bugs are still there.
One is the effect that, when it "exits" from the screens, appears for some pixels on the opposite side of the screen.
http://openarena.ws/board/index.php?topic=3578.msg33455#msg33455
The other is: if "bloom" is enabled (r_bloom 1) and the texture quality is set to 16 bits (r_texturebits 16), some sort of semi-transparent square appears on the bottom left corner of the screen. (first said here).

[rambokalle]

...
One is the effect that, when it "exits" from the screens, appears for some pixels on the opposite side of the screen.
http://openarena.ws/board/index.php?topic=3578.msg33455#msg33455
...[/url]).

There seems to be some bloom texture clamping issues in tr_bloom.c, so occasional bleeding on the screen edges can appear. This is really easy to fix, for example:

Code:

data = ri.Hunk_AllocateTempMemory( bloom.screen.width * bloom.screen.height * 4 );
Com_Memset( data, 0, bloom.screen.width * bloom.screen.height * 4 );
#ifdef GL_CLAMP_TO_EDGE
bloom.screen.texture = R_CreateImage( "***bloom screen texture***", data, bloom.screen.width, bloom.screen.height, qfalse, qfalse, GL_CLAMP_TO_EDGE );
#else
bloom.screen.texture = R_CreateImage( "***bloom screen texture***", data, bloom.screen.width, bloom.screen.height, qfalse, qfalse, GL_CLAMP );
#endif
ri.Hunk_FreeTempMemory( data );

data = ri.Hunk_AllocateTempMemory( bloom.effect.width * bloom.effect.height * 4 );
Com_Memset( data, 0, bloom.effect.width * bloom.effect.height * 4 );
#ifdef GL_CLAMP_TO_EDGE
bloom.effect.texture = R_CreateImage( "***bloom effect texture***", data, bloom.effect.width, bloom.effect.height, qfalse, qfalse, GL_CLAMP_TO_EDGE );
#else
bloom.effect.texture = R_CreateImage( "***bloom effect texture***", data, bloom.effect.width, bloom.effect.height, qfalse, qfalse, GL_CLAMP );
#endif
ri.Hunk_FreeTempMemory( data );
bloom.started = qtrue;

Now the bleeding should be gone. 

[Gig]

From what I know, Fromhell already fixed that "bleeding" problem in version 25 executables (see). Maybe (s)he may compare the two solutions, maybe one is more efficient than the other one?

Anyway, if you are comfortable with bloom source code, maybe you may fix and resolve the other bloom problem that affected 0.8.5 executables: if texture quality was set to 16 bit, a strange semi-transparent "square" appeared in the lower left corner of the screen. Fromhell "worked around" that (again, from version 25 executables) by forcing bloom to shutdown itself unless the user had previously forced 32 bit textures (FH said that bloom was never designed to work with 16 bit textures): for me it's not a problem to do have bloom with 16 bit textures, but it's a problem to have people need to manually force another option -leaving default texture quality disables bloom, too- with no clear instructions in menu nor console to help users to understand what they have to do! Maybe you may find a fix for that 16 bit problem, and then that auto-disabling check may be removed?

OpenArena 0.8.8 executables will also introduce a new bloom version, called "Cascaded blur" or "Cascaded bloom". This should have been the new default, but we found a problem with it (something that may resemble the "bleeding" bug, but not exactly the same, see this screenshot) and its author said he will not be able to work on it before march or similar... so for the moment the new kind of bloom has been disabled by default.

[GrosBedo]

Great visual effect! And it seems to be not take too much cpu cycles. I like it!

Will it ever be implemented in OA? Please write it down on the TODO list, the effect is very cool!

[Neon_Knight]

IICR, it's already present in 0.8.8.

[GrosBedo]

IICR, it's already present in 0.8.8.

Really? I thought it was the other version of the bloom effect. Great!

[Gig]

Then, how to enable it? Are you sure you are not confusing this with cascaded blur/cascaded bloom?

[Neon_Knight]

It's r_bloom_reflection we're talking about?

[Gig]

Sounds likely. You are the first that mentions that variable. I'll have to check this...