Hello, in my adventures with ReShade I have been frustrated. I documented the issue I have been having in a previous forum post, but none of the images worked and I've discovered more since then.
The Problem
In short, whenever I passed a certain altitude, when using ReShade, my aircraft would go translucent, DoF effects would stop working, and other depth-dependent effects would break in their own ways.
Depth Map Issues
These problems stem from a weird issue involving the game's Depth Map.
Depth Map
As you can see, the Depth Map is being cut off too far from the camera, resulting in the other effects' errors.
MainCamera and CameraPlane
My theory is that this problem stems from the way game objects MainCamera and CameraPlane behave.
I will demonstrate their behavior by changing their Fields of View.
The FOV difference is not part of the error.
For my demonstration, Main Camera has an FOV of 90 degrees, while CameraPlane has an FOV of 40 degrees.
While on the ground (note: I have determined that this behavior is relative to the camera's distance to terrain, not the aircraft's altitude.) the entire scene is rendered using MainCamera, and is entirely shown with a 90 degree FOV.
However, when the aircraft passes a certain altitude, the behavior changes. Objects close to the camera will be rendered by CameraPlane (40 FOV), while objects far from the camera are rendered by MainCamera (90 FOV).
If I zoom out, everything is rendered by MainCamera, and is in 90 FOV.
When I zoom in, more is rendered by CameraPlane, and is shown in 40 FOV.
This slicing is actually visible in-game, and it manifests itself as an odd shading error, on the exact same plane as the ReShade depth map clipping.
ReShade
I believe that ReShade is only reading data from MainCamera to create a depth map. However, if you check "CLEAR 2" (which only appears in situations where CameraPlane is rendering anything) in the Depth Buffers panel, the depth map will use data from CameraPlane only.
CLEAR 2 unchecked:
CLEAR 2 checked:
this tells me that MainCamera and CameraPlane are relevant to Reshade's depth map.
Conclusion
Reshade only reads data from MainCamera to create depth maps, when both MainCamera and CameraPlane produce data that is needed. This results in incorrect depth data and errors from effects that require depth data to function.
With this information, I would really appreciate it if someone who knows more about unity or SimplePlanes to create a workaround for this issue, if possible. Thank You
Please let me know if the images aren't working. Data subject to change.
me who doesn't even do fancy thumbnails:
understandable have a great day
@Kennneth
No problem. Let me know if you come up with a workaround.
@jamesPLANESii
My best guess is something called shadow cascading. Here.
My question is why does the game do this
Thanks for the investigation, it really saved me a lot of work to troubleshoot 👍
The images are visible on my phone, so you’re good. As for the reshade, idk how that stuff works so I can’t really help, sorry.
@NumbersNumbersTheMan
Just to clear things up for me, is the problem with the depth map clipping effecting everyone? Thanks.
@NumbersNumbersTheMan
Thanks. I modified the FOV manually to show the difference between CameraPlane and MainCamera, it's not an error. By camera control, do you just mean careful camera placement, or are there settings that I can change to fix the problem entirely?
The FOV error is wrong, if you are using the incorrect depth map it will change FOV like you said. Please make sure you are using the correct map. The other clipping issue where you can see with the shadows and clears is correct but can easily be fixed using some camera control. Source: ex pe ri ence.
@POTETOZ
Okay, thanks.
images work for me on my laptop