[SOLVED] Screen space effects and Tone mapper

[Amerio.Stephane]

Hello,

We are using our IG with multiple adjacent slaves, without any blending between adjacent images (direct-LED walls). I was careful enough to disable all effects that could impact differently the channels (screen space based effects), but the end result is it also disable the tone mapper, giving a final very dull image.

If I don't disable ScreenSpaceEffects (while still disabling bloom, white balance, dynamic exposure, environment haze, vignette, sss), then a seem is sometimes very visible between channels:

(left and right part of the image are from different PC channels).

Increasing BorderX & BorderY does not change the seam appearance.

Again, if I disable ScreenSpaceEffects, then the seam disappear, but the image is too dull because it also disable the tone mapper.

Is there a way to keep the tone mapper enabled? Would there be any other screen space based effect I forgot to disable?

[silent]

Hi Stephane,

Probably some other screen-space effects are still enabled. Try to disable these as well:

• render_environment_haze_screen_space_global_illumination 0

• render_white_balance 0

If this will not produce better results could you please send us your current render settings (either as a preset or cut and paste from .world file)?

Thanks!

[Amerio.Stephane]

Yeah found it, it was SSR and DirtScale. I'm still probably missing a few others (that's why I wanted to simply use render_screen_space_effects).

My initial point holds, though. The toggle render_screen_space_effects shouldn't toggle the global tonemapper in my opinion, because as I understand it the tonemapper effect is just a LUT, so two different PC with adjacent images should always result in a coherent image (unlike the LOCAL tonemapper, which I agree have to be disabled because it IS a screen space effect)

[silent]

Hi Stephane,

While technically it's correct (although you can in theory have a situation when you have different tonemapper settings set), command behavior will not be changed.

Maybe some new command is required for that specific task (to configure screen-space effects for multi-window / multi-viewport configurations), we don't know yet 🙂

Anyways, thank you for the feedback!