LWRP/HDRP FPS Weapon Camera Fix: How to Post-Process?

[Xander-Davis]

Hi, I’ve switched my game to the LWRP for a FPS using this tutorial:

UFPS + LWRP: Weapon Camera Issue

Hi! I'm experimenting with converting my UFPS game from the regular Core RP to the Lightweight Render Pipeline (LWRP). This seems to work very well so far except the Weapon Camera doesn't merge with the main FPS Camera. If I turn the Weapon Camera's Camera component off, then it looks fine but obviously the weapon isn't there. [image] ^^^ Weapon Cam's camera component on. [image] ^^^ Weapon Cam's Camera component off. Any ideas? I've poked every toggle on these cameras I could find…

FPS Game Rendering and Graphics in Unity! (Tutorial)

The only problem with the above video is it doesn’t solve for preventing the FPS weapon from going through objects and walls.

Then I was shown this video which demonstrates a fix from Unity and a third-party free Asset Store asset ( https://assetstore.unity.com/packages/tools/particles-effects/post-processing-texture-overlay-147951 ) for a Texture post-process layer, specifically to work with the alternate render pipelines:

Render Weapons always on top - Unity FPS Weapon Render Layer - SRP

And I got that implemented easily enough:

However, I’m currently stuck trying to figure out how to implement post-processing on the Weapon Camera.

If I turn on Post-Processing on the Weapon Camera, there’s obviously a problem with this because firstly we would be rendering the WeaponCam Texture over the WeaponCam itself recursively. While this is true, there’s secondly a bizarre effect where it ‘ghosts’ the actual game object and only shows highlights or the post-process of the object (I think?)

So how could we apply post-processing on the Weapon Cam?

This is especially confusing under the new Post-Processing Volumetric system. We apparently no longer can just tag on a Post-Process profile to the WeaponCam like we used to be able to, because now we have to marry that with a volume with a profile on that in the level itself. We have an infinitely-sized post-process volume for the entire level. So how would you have a second Post-Process volume for just the WeaponCam only and have the MainCam ignore this? Further, I’m not even exactly sure this is the right way to go-- I don’t yet really even know if applying post-process to the WeaponCam and then rendering that to texture to render into a Post-Processing stack on another Camera is even possible at all.

Is there another way to go about this?

I’m sure this will be an issue for many developers doing FPS games so any replies here to find a fix would undoubtedly be appreciated by myself and others.

Thanks!

[Xander-Davis]

I created a macOS build and was treated to the texture not masking itself as it does in-editor.

Behold, a black screen:

Any ideas on how to ensure the texture isn’t rendering the camera background in builds (even if it passes through in-editor) as well?

This might have something to do with how the weapon looked ‘ghosted’ with Post-Processing turned on, as all darker shadowed areas of the gun became transparent in editor. My WeaponCam’s background is set to black, which made it transparent when applied to the texture for the Post Processing stack… but, again, only in editor (not in a build).

I also emailed the developer of the Texture Overlay asset, Daniel Erdmann, to see if he has any insight ( xxxditzelxxx@gmail.com )

[mat108]

Unity in the year of our lord 2021. You spend weeks looking for a solution to problem C only to discover once you found it that it introduces problem A again. And by the tim you found the solution to problem A you realise it reintroduces problem B. And the only possible solution to problem B brings problem C back. So now we’ve spent 3x the amount of weeks and have gone absolutely nowhere.

I wish I could help you.

[radiantboy]

I think ive just noticed HDRP messed with my UFPS weapon camera stuff, is there a problem using 2 cameras in HDRP?