SceneWindow is not cleared if Post Effects is null and Defaut Post Effects are disabled while in helper view

vvvv gamma bug
1

Hey there,

This bug does not occur on 6.6 stable.

When in helper view (F4), if no Post Effects are provided and Default Post Effects are disabled, content is not cleared anymore (or something like that).

Repro steps :

  • Open the Rings help patch
  • Disconnect the Post FX
  • Disable Enable Default Post FX
  • F4
  • Orbit

In 6.7-310

Doing the same in 6.6 stable

Thanks in advance!

1 Like
2

thanks for the report!

upcoming:

We removed complexity by getting rid of the “Enable Default Post Effects” pin.

How to adapt:
Disconnect your PostFX to get the default PostFX. or go to edit mode. There we also use our default look.

3

Thanks for the feedback!

Not too versed into design stuff myself so that might be a silly question, but what if I don’t want to provide custom PostFX and also don’t want the default ones in normal mode?

2 Likes
4

@sebescudie is right, disabling that pin is often required for various reasons. Adding an “empty” post fx node/region is way more work. Additionally, you will find many threads in the forums or chat with this instruction. It would be odd if it was gone.

2 Likes
5

why not the other way around:

default is no postfx.
once postfx is connected > use it.

the (what is now the) default PostFX could end in a node that a user can use, similar to the default imgui-style. and it’s used in edit mode (if you want).

4 Likes
6

That sounds good and simple, but the reason for the default post fx is that the material pipeline needs it. In particular, the ToneMap, so the default as it currently is is correct because a beginner/newcomer will not know that and the pipeline should be complete by default.

If there is no default, you are always forced to add a postfx node, which is another node you need to take care of when setting up a Scene quickly. And even if you know it, as a pro, you often won’t bother… RootScene is already a node that is annoying to add, so another one is not a good solution, I’d say.

7

from a user perspective, i would still argue:
default = no/minimum postfx (which is equal to a neutral tonemap).

and you’re right about the rootscene annoyance. but i recently had a case, where it was handy the way it is (render scene twice with different cams).

8

Yes, that is what we have at the moment. The default post fx is only a tone map. We could argue whether it is the right one. We just took the one Stride uses. If you have a better suggestion, let us know, it could be worth exploring.

9

I don’t have a better solution, because I’m happy with the existing one :)

1 Like
10

okay. Thanks for the prompt feedback. Reverted back to how it’s been.

1 Like