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 errors and black rectangle appearing over editor viewport. #39620

Closed
ghost opened this issue Jun 17, 2020 · 3 comments
Closed

Vulkan errors and black rectangle appearing over editor viewport. #39620

ghost opened this issue Jun 17, 2020 · 3 comments

Comments

@ghost
Copy link

ghost commented Jun 17, 2020

Godot version:

66b0b0c

OS/device including version:

Win10 64-bit NVIDIA GeForce GTX 1660 SUPER

Issue description:

Made a build of the master, and have the following errors and some rendering oddities.


ERROR: Cant find layer: VK_LAYER_KHRONOS_validation
   at: VulkanContext::_check_layers (drivers\vulkan\vulkan_context.cpp:158)
ERROR: Cant find layer: VK_LAYER_LUNARG_standard_validation
   at: VulkanContext::_check_layers (drivers\vulkan\vulkan_context.cpp:158)
ERROR: Cant find layer: VK_LAYER_GOOGLE_threading
   at: VulkanContext::_check_layers (drivers\vulkan\vulkan_context.cpp:158)
WARNING: GENERAL - Message Id Number: 0 | Message Id Name: Loader Message
        ReadDataFilesInRegistry: Registry lookup failed to get layer manifest files.
        Objects - 1
                Object[0] - VK_OBJECT_TYPE_INSTANCE, Handle 1898400848544
     at: VulkanContext::_debug_messenger_callback (drivers\vulkan\vulkan_context.cpp:134)


Godot Engine v4.0.dev.custom_build.66b0b0c15 - https://godotengine.org
ERROR: Cant find layer: VK_LAYER_KHRONOS_validation
   at: ERRVulkanConORtext::_check_layers (drivers\vulkan\vulkan_context.cpp:158)
: Some texture bindings were not properly freed (leaked canvasitemsERROR:?
 Cant find layer: VK_LAYER_LUNARG_standard_validation
   at:    at: RasterizerCanvasRD::~RasterizerCanvasRD (servers\rendering\rasterizer_rd\rasterizer_canvas_rd.cpp:2564)
VulkanContext::_check_layers (drivers\vulkan\vulkan_context.cpp:158)
ERROR: Cant find layer: VK_LAYER_GOOGLE_threading
WARNING:   at:  2 RIDs of type 'StorageBuffVulkanContext::_check_layers (drivers\vulkan\vulkan_context.cpp:158)
er' were leaked.
     at: RenderingDeviceVulkan::_free_rids (drivers\vulkan\rendering_device_vulkan.cpp:7185)
ERROR: Condition "!windows.has(p_window_id)" is true.
   at: VulkanContext::window_destroy (drivers\vulkan\vulkan_context.cpp:762)
WARNING: GENERAL - Message Id Number: 0 | Message Id Name: Loader Message
        ReadDataFilesInRegistry: Registry lookup failed to get layer manifest files.
        Objects - 1
                Object[0] - VK_OBJECT_TYPE_INSTANCE, Handle 2006505139504
     at: VulkanContext::_debug_messenger_callback (drivers\vulkan\vulkan_context.cpp:134)

C:\Source\bin>ERROR: Condition "!windows.has(p_window)" is true.
   at: VulkanContext::window_resize (drivers\vulkan\vulkan_context.cpp:730)

ERROR: Condition "!windows.has(p_window)" is true.
   at: VulkanContext::window_resize (drivers\vulkan\vulkan_context.cpp:730)
ERROR: Condition "!tp" is true.
   at: ThreadWindows::wait_to_finish_func_windows (drivers\windows\thread_windows.cpp:80)

After running a project it returned had this black rectangle stuck over the viewport.

image

Steps to reproduce:
Uncertain if it can be replicated by steps.

Minimal reproduction project:

N/A

@akien-mga
Copy link
Member

The EditorFileSystem crash is reproducible in any new project when doing the first import, yeah. It would be good to move to a dedicated report as it's not related to the Vulkan issues you're having.

@ghost
Copy link
Author

ghost commented Jun 17, 2020

Alright, I will trim that part out.

@ghost ghost changed the title Editor crash on startup, and black rectangle over editor viewport. Vulkan errors and black rectangle appearing over editor viewport. Jun 17, 2020
@Calinou
Copy link
Member

Calinou commented Aug 21, 2022

Closing, as the issue may not be reproducible anymore and OP has removed their account (so they can't reply).

Please open a new issue if you can still reproduce this on 4.0.alpha14 or newer.

@Calinou Calinou closed this as not planned Won't fix, can't repro, duplicate, stale Aug 21, 2022
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

3 participants