Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Volumetric Fog texture oddly fills with pitch black when Decal is present in camera frustrum #54496

Closed
Tracked by #57284 ...
Phobos001 opened this issue Nov 2, 2021 · 5 comments

Comments

@Phobos001
Copy link

Godot version

v4.0.dev.20211027.official [157cba3]

System information

Linux Mint 20.2, AMD Radeon VII, Mesa 21.1.8 - kisak-mesa PPA, Vulkan Clustered

Issue description

godot_github_issue_decal_fog-2021-11-01_20.12.49.mp4

When a Decal is present on screen, and Volumetric Fog is active in the WorldEnvironment node, its very easy to generate strange black squares across the entire screen by moving the camera around. The decal does not need to be projecting on a mesh. It happens regardless, but only when the Decal is in the frustrum of the camera. The decal needs to have a texture assigned to it to recreate the effect.

Steps to reproduce

  1. Create a Decal
  2. Assign a texture to the albedo, icon.png will do just fine.
  3. Create a WorldEnvironment
  4. Activate the VolumetricFog effect
  5. Wiggle the editor window when the Decal is in the view. A series of black squares will consume all light. The squares will go away if the decal is out of the frustrum and new VolumetricFog data fills the spaces in.

Minimal reproduction project

DecalVolumetricFogError.zip

@briansemrau
Copy link
Contributor

briansemrau commented Nov 2, 2021

I'm unable to reproduce using the min rep on the listed commit using W10, RTX2060 (driver v472.12), vulkan clustered.

Also, note that since that commit, there has been a large PR merged making significant changes to volumetric fog. It's worth trying out a version since then to make sure the problem still exists. #53353

@Calinou
Copy link
Member

Calinou commented Nov 2, 2021

This bug may be AMDGPU driver-specific: #53528

@Ansraer
Copy link
Contributor

Ansraer commented Jan 26, 2022

Unable to confirm this bug on Windows + AMD 6900XT running Driver Version
21.40.11.03-211201a-374383E-RadeonSoftware.

Created the scene as described and panned around for a good minute. Never got any artifacts at all.

Will be able to test on linux with the same hardware in a few days once I can reboot my PC.

@clayjohn
Copy link
Member

No one could reproduce and OP never responded. So assuming this is a driver bug and has been resolved. If anyone runs into this bug we can reopen

@clayjohn clayjohn closed this as not planned Won't fix, can't repro, duplicate, stale Feb 23, 2023
@clayjohn clayjohn removed this from the 4.0 milestone Feb 23, 2023
@clayjohn clayjohn added archived and removed bug labels Feb 23, 2023
@Calinou
Copy link
Member

Calinou commented Feb 23, 2023

For future reference, I couldn't reproduce this on 4.0.rc3 with the linked MRP (Linux, GeForce RTX 4090 with NVIDIA 525.89.02):

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants