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

Vulkan: SpotLight3D's Projector doesn't work (regression from 4.0.alpha5 and later) #59488

Closed
Tracked by #57284
macryc opened this issue Mar 24, 2022 · 11 comments · Fixed by #66065
Closed
Tracked by #57284

Vulkan: SpotLight3D's Projector doesn't work (regression from 4.0.alpha5 and later) #59488

macryc opened this issue Mar 24, 2022 · 11 comments · Fixed by #66065

Comments

@macryc
Copy link

macryc commented Mar 24, 2022

Godot version

4.0 alpha 5

System information

Win10, GLES3, RTX 2070 mobile

Issue description

SpotLight3D's Projector doesn't work. Worked fine in alpha 4, stopped in alpha 5.

Steps to reproduce

Create a 3d scene
add spotlight3d
add texture2d to projector slot
enable shadows on spotlight
put in a 3d mesh to cast spotlight on

Minimal reproduction project

No response

@Calinou Calinou changed the title Spotlight3D's Projector doesn't work in Godot 4 alpha 5 Vulkan: SpotLight3D's Projector doesn't work in Godot 4 alpha 5 Mar 24, 2022
@Calinou
Copy link
Member

Calinou commented Mar 24, 2022

@macryc Please upload a minimal reproduction project to make this easier to troubleshoot.

@Calinou Calinou added this to the 4.0 milestone Mar 24, 2022
@macryc
Copy link
Author

macryc commented Mar 24, 2022

spotlight3d.zip

@Calinou
Copy link
Member

Calinou commented May 20, 2022

I can confirm this on 9923179 (Linux, NVIDIA 510.68.02). OmniLight3D projectors also don't work. This bug occurs in both Vulkan Clustered and Vulkan Mobile backends.

An interesting thing is that the decal atlas appears broken after you reload the project:

image

Testing project: https://0x0.st/oaSJ.zip

@Calinou
Copy link
Member

Calinou commented May 20, 2022

I bisected the regression to 57e5a33. cc @BastiaanOlij

@BastiaanOlij BastiaanOlij self-assigned this May 21, 2022
@BastiaanOlij
Copy link
Contributor

Hmm, I must have messed something up when moving all the code related to this into the new TextureStorage class. I'll have a closer look as soon as I've finished with the GI changes.

@Calinou Calinou changed the title Vulkan: SpotLight3D's Projector doesn't work in Godot 4 alpha 5 Vulkan: SpotLight3D's Projector doesn't work (regression from 4.0.alpha5 and later) Jun 14, 2022
@fire
Copy link
Member

fire commented Aug 24, 2022

Add initial ies lights #63835 is dependent on this.

@kidinashell
Copy link
Contributor

Currently still no change (in 4.0 beta1) when using projector textures (plain lighting as per default) @BastiaanOlij Would this be something you could want some help with? I've never contributed to the project myself so I would have to look into the structure of things and regulations but I would like to fix this if possible.

@fire
Copy link
Member

fire commented Sep 16, 2022

@clayjohn May be able to assist @kidinashell

@clayjohn
Copy link
Member

Currently still no change (in 4.0 beta1) when using projector textures (plain lighting as per default) @BastiaanOlij Would this be something you could want some help with? I've never contributed to the project myself so I would have to look into the structure of things and regulations but I would like to fix this if possible.

@kidinashell Feel free to work on this, Bastiaan is quite busy with some other work right now.

To help you get started, projector textures were added in #37887. This should give you an idea about how they should work.

Calinou bisected the regression to 57e5a33 so the bug was introduced by something that Bastiaan changed in 57e5a33. Looking between Juan's PR and Bastiaan's commit you should be able to find out what went wrong.

As for contributing, we have a whole section of the docs dedicated to documenting helpful things to know as you get started contributing.

Also feel free to ask questions. You can reach both Bastiaan and I quite easily on the rendering channel on Godot's contributor chat.

@BastiaanOlij
Copy link
Contributor

Sorry guys, totally lost track of this one. Yeah I'm heads down bum up in further reorg stuff so I could definitely use an extra set of eyes on this one. As the commit that seems to have broken this mostly moves stuff into new classes it's likely a simple issue with a RID getting mixed up or a setting getting reversed.

@kidinashell
Copy link
Contributor

@BastiaanOlij Did a PR #66065 for this after looking around the renderer section and it's ready for review. Hope it helps.

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

Successfully merging a pull request may close this issue.

6 participants