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

Screen Space Reflections disappear from any moving object in 4.3 #97998

Closed
jamesdkay opened this issue Oct 9, 2024 · 3 comments
Closed

Screen Space Reflections disappear from any moving object in 4.3 #97998

jamesdkay opened this issue Oct 9, 2024 · 3 comments
Labels

Comments

@jamesdkay
Copy link

jamesdkay commented Oct 9, 2024

Tested versions

  • Reproducible in v4.3.stable.mono.official [77dcf97]
  • Not reproducible v4.2.stable.mono.official [46dc277]

System information

Godot v4.3.stable.mono - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1660 Ti (NVIDIA; 31.0.15.1640) - AMD Ryzen 7 4800H with Radeon Graphics (16 Threads)

Issue description

Any time an object is moving it loses its screen space reflections until it stops moving. This is new in 4.3 and did not happen in 4.2. Issue occurs both in the editor and in game.

Compare a moving object in 4.2:

_.ssr.test.tscn.-.SSR.Artifacts.-.Godot.Engine.2024-10-08.19-12-33.mp4

...with the same scene in 4.3:

_.ssr.test.tscn.-.SSR.Artifacts.-.Godot.Engine.2024-10-08.19-13-34.mp4

This happens both in the editor and in game.

Steps to reproduce

Create a scene, add a few objects, add a WorldEnvironment and enable SSR. Move on object and the reflection effect disappears from the object when it is moving.

Minimal reproduction project (MRP)

Simply move any object that you can see screen space reflections on and watch them disappear.

ssr.disappears.zip

@tetrapod00
Copy link
Contributor

Probably a duplicate of #95814, which was fixed in #95438.

Try one of the 4.4dev versions and see if you can reproduce the problem?

@jamesdkay
Copy link
Author

Oops, sorry for the duplicate. Somehow I missed the other one.

@jamesdkay jamesdkay closed this as not planned Won't fix, can't repro, duplicate, stale Oct 9, 2024
@tetrapod00
Copy link
Contributor

It's easy to miss when the issue was already closed. Thank you for reporting, anyway!

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

No branches or pull requests

3 participants