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: Setting a PanoramaSky makes console spam error #45746

Closed
nonunknown opened this issue Feb 5, 2021 · 1 comment
Closed

Vulkan: Setting a PanoramaSky makes console spam error #45746

nonunknown opened this issue Feb 5, 2021 · 1 comment

Comments

@nonunknown
Copy link
Contributor

nonunknown commented Feb 5, 2021

Godot version:
Godot Engine v4.0.dev.calinou.779dc7613

OS/device including version:
Windows 10 x64
Using Vulkan Device #0: AMD - AMD Radeon R7 200 Series

Issue description:
Console spams INFINITELY the following message:

ERROR: Condition "!uniform_set" is true.
   at: draw_list_bind_uniform_set (drivers/vulkan/rendering_device_vulkan.cpp:6452)
ERROR: Uniforms were never supplied for set (1) at the time of drawing, which are required by the pipeline
   at: (drivers/vulkan/rendering_device_vulkan.cpp:6607)

This happens when you set the sky to .HDR file and also the sky goes black:
image

Steps to reproduce:

  • Create a new WordEnvironment node
  • use the following config:
    image

Minimal reproduction project:

WorldBug.zip

PS: When you click worldenvironment node, mode will be clearcolor, change it to Sky
image

Update

Closing godot and opening the project again, things works nice
edit: Just closing the scene and opening it works as well.

image

@Calinou Calinou added this to the 4.0 milestone Feb 5, 2021
@Calinou Calinou changed the title [Godot 4] Setting .Hdr sky makes console spam error Vulkan: Setting a PanoramaSky makes console spam error Feb 5, 2021
@akien-mga
Copy link
Member

Thanks for the detailed bug report.

I tested in a recent master build and I can't reproduce the issue, it must have been fixed recently (before #54489 as the build I'm testing didn't include this PR yet).

I also couldn't reproduce it in v4.0.dev.20210811.official (7188cb6). You might want to double check yourself as maybe this was system specific or needs slightly different steps to reproduce.

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.

4 participants