Bloom + Wireframe Issue

[FlorianGeorge]

There seems to be an issue with Ogre when rendering a Scene with Bloom and Wireframe activated at the same time. This is happening since I can remember, including 1.7.2 and 1.8.0 unstable.

Steps to reproduce:

Start SampleBrowser, load up Compositor Sample. It should look like this:


Activate Bloom, it should look like this:


Deactivate Bloom, press R once to activate Wireframe, it should look like this:


Press R twice to go back to Solid mode, activate Bloom, then press R to activate Wireframe, it will look like this:


Deactivate Bloom, activate it again, it will look like this:


As you can see, depending on the order of activating Bloom and Wireframe, you can get two broken ways of displaying the scene, both will not update the screen anymore except for that diagonal line from the bottom left to the upper right.

Is this a bug, or working as intended aka don't do it?

[so0os]

haha, compositor renders to quad and renders the quad on screen. diagonal line divides it into triangles. Why do you need a wireframe bloom anyways?

[jonim8or]

Sounds like a bug. THe diagonal line actually is the wireframe. It is the polygon that is being used for the post-processing effects. All compositor effects are drawn on a full-screen quad, which is two triangles (one top-left and one bottom-right apparently)
apparently the wireframe is not applied to all rendering passes of the compositor chain.

[so0os]

It's been like this forever, is it really a bug?. Also, the reason you're seeing stuff behind the wireframe quad is that scene is not cleared every frame.

[FlorianGeorge]

Why do you need a wireframe bloom anyways?

I don't need to have bloom activated during wireframe mode, but a year ago this issue forced me to make my framework check each time Bloom or Wireframe was activated and deactivate Bloom while Wireframe was active. I never gave it much thought again, but a few days ago I accidentally ran into the same issue again, re-implemented the Wireframe vs Bloom check, but thought that this just doesn't seem right.

I think it's a bug. It's easy to work around, but it's an annoyance. Papercut? I don't know how deep into the Compositor/Wireframe code you'd have to dig to fix this.

[so0os]

uhm, no need to check, you can disable/enable compositors that doesn't even exist, try/catch if something.

[FlorianGeorge]

uhm, no need to check, you can disable/enable compositors that doesn't even exist, try/catch if something.

of course i have to check, if bloom was enabled before and I just disable bloom blindly on wireframe activation I would "forget" to turn it back on after wireframe is deactivated
same thing when user tries to activate bloom while wireframe is active