how to add post processing to second camera(fps setup)

DJM

there is an option to asign a saved environment to the second camera, however that doesnt seem to have any effect on the rendering

TwistedTwigleg

Is the second camera marked as current in the properties? I think only the Camera marked as current will render with it's environment. Also, and I'm not totally sure, but if you are using the second Camera in a Viewport, you may need to set the environment in the Viewport/World settings for it to take effect on rendered ViewportTexture.

DJM

@TwistedTwigleg said: Is the second camera marked as current in the properties? I think only the Camera marked as current will render with it's environment. Also, and I'm not totally sure, but if you are using the second Camera in a Viewport, you may need to set the environment in the Viewport/World settings for it to take effect on rendered ViewportTexture.

the second camera isnt marked as current. im using a second camera in a viewport yes. if i set the viewport/world my fps objects dissapear

if there is a better solution for no clipping and seperate field of view, that would be great cause the viewport renderer makes my fps objects un antialiased and they dont get environment effects

TwistedTwigleg

Ah okay. I'm not sure right off, but I'll do some tests and see if I can get it working with two Cameras working (one in a Viewport) with their own separate environments.

I'm not sure on a solution for no-clipping or separate FOV. I think you might be able to avoid using a separate Viewport and just modify the FOV of the camera, but I don't think there is a way to modify it, get a render/texture, and then set it back, so modifying the FOV would affect the main render as well without using a separate Viewport.

DJM

@TwistedTwigleg said: Ah okay. I'm not sure right off, but I'll do some tests and see if I can get it working with two Cameras working (one in a Viewport) with their own separate environments.

I'm not sure on a solution for no-clipping or separate FOV. I think you might be able to avoid using a separate Viewport and just modify the FOV of the camera, but I don't think there is a way to modify it, get a render/texture, and then set it back, so modifying the FOV would affect the main render as well without using a separate Viewport.

avoiding a viewport would be great, different FOVs is a must tho

TwistedTwigleg

Okay, I got it working! I added probably a tad more than is needed just as an example, but I wanted to make sure it worked with any FOV and with a moving camera. Here's the project and a screenshot of how it looks when running:

I ended up needing to use two Viewport nodes, as I was getting all sorts of glitches trying to get it working with a single Camera without an additional Viewport.

Also, I got the same issue when setting the World, it just makes everything disappear. I'm guessing when you set a World it stops rendering the current scene and only renders whatever children nodes are in the Viewport, but that is totally not what I would expect unless you toggle the own world property. I thought only if own world was on that it would actively ignore the current scene. Ultimately I just assigned the environment to the Camera directly and used a WorldEnvironment node for the main view and it seems to work fine. Both environments can have different values, the cameras can have different FOVs, and the effects seem to work on both. I'm not sure if anti-alising works on the second Viewport though, I forgot to check, but everything else seems to work.

cybereality

Viewports would work, but I find them really hard to work with. Once you put your 3D models into a Viewport, you can long longer select them in the editor, which makes it almost impossible to work on your game.

DJM

@TwistedTwigleg said: Okay, I got it working! I added probably a tad more than is needed just as an example, but I wanted to make sure it worked with any FOV and with a moving camera. Here's the project and a screenshot of how it looks when running:

I ended up needing to use two Viewport nodes, as I was getting all sorts of glitches trying to get it working with a single Camera without an additional Viewport.

Also, I got the same issue when setting the World, it just makes everything disappear. I'm guessing when you set a World it stops rendering the current scene and only renders whatever children nodes are in the Viewport, but that is totally not what I would expect unless you toggle the own world property. I thought only if own world was on that it would actively ignore the current scene. Ultimately I just assigned the environment to the Camera directly and used a WorldEnvironment node for the main view and it seems to work fine. Both environments can have different values, the cameras can have different FOVs, and the effects seem to work on both. I'm not sure if anti-alising works on the second Viewport though, I forgot to check, but everything else seems to work.

im not sure how u did it im using culling masks, and then it stops working i tried your scene and set camera 2 to cull on layer 2 and main to render everything but 2 and then the environment effects stop working

DJM

ignore my post im trying to figure out how to implement this in my setup

DJM

could u post a setup without the splitscreen function and with camera2 with a culling mask?

TwistedTwigleg

Sure! Just a second

TwistedTwigleg

Okay, I added another scene (Test_Scene_Two.tscn) and script that does not have the split-screen effect, the adjustable FOV, and it uses culling masks so the spheres are only visible in the second viewport and not the first.

DJM

@TwistedTwigleg said: Okay, I added another scene (Test_Scene_Two.tscn) and script that does not have the split-screen effect, the adjustable FOV, and it uses culling masks so the spheres are only visible in the second viewport and not the first.

ah yes

i found the problem,

if u turn on transparent background(wich i need) the post processing is gone. dont know why tho

DJM

could a custom shader do the trick? not just simply disabling depth test, that doesnt work with multiple meshes

TwistedTwigleg

Yeah, I can confirm that using a transparent background is the issue, which is strange because it seems what happens is that it turns off the environment completely. Even setting the world doesn't change anything at all, where it used to act like own world was enabled. It seems that turning the transparent background on sets it to a preset environment. I want to say this is a bug, or at very least there should be a warning or something that using transparent backgrounds disables the set environment completely.

DJM

@TwistedTwigleg said: Yeah, I can confirm that using a transparent background is the issue, which is strange because it seems what happens is that it turns off the environment completely. Even setting the world doesn't change anything at all, where it used to act like own world was enabled. It seems that turning the transparent background on sets it to a preset environment. I want to say this is a bug, or at very least there should be a warning or something that using transparent backgrounds disables the set environment completely.

yeah shame, would look so much better. not only does the environment stop working, also the msaa, fxaa, sharpening etc.

cybereality

Looks like this is a bug (or strange design decision). See here: https://github.com/godotengine/godot/issues/45208

However, you might be able to do it by using a full-screen shader that takes both viewport textures as uniforms and does the compositing itself. However, there is a performance cost to doing this, as you have to read the texture data, convert it to an image on the CPU, and then send it back to the shader. I'm fairly sure it would work, but you should test it to see if the performance hit is acceptable.

DJM

@cybereality said: Looks like this is a bug (or strange design decision). See here: https://github.com/godotengine/godot/issues/45208

However, you might be able to do it by using a full-screen shader that takes both viewport textures as uniforms and does the compositing itself. However, there is a performance cost to doing this, as you have to read the texture data, convert it to an image on the CPU, and then send it back to the shader. I'm fairly sure it would work, but you should test it to see if the performance hit is acceptable.

i have no idea how to do that. ill wait for a fix (hopefully)

cybereality

Well, posting your issue and use case in that Github link might be a good start. If they see more people with the problem there may be more progress. But I wouldn't wait for a fix, as that can be an indeterminate amount of time. For example, the issue was first reported on January 15th and we are almost at the end of the year. The two viewport compositing shader is not very hard, but you will need to know how to write shader code. I can do an example, but I have some other stuff I'm working on right now.

cybereality

One thing though, if you composite, then you end up with a full screen flat quad. So some effects (like those that are based on 3D depth) won't work (e.g. SSAO, DOF, etc.). But 2D effects like tone-mapping and glow should still work.