Open dzil123 opened 1 year ago
Were you able to run any of the alphas or betas on this hardware?
I tested alpha1 and beta1, both open a white window without the Godot icon in the title bar. Alpha1 closes by itself without any notable logs, but beta1 freezes and has this log: out.txt
ERROR: Condition "err" is true. Returning: ERR_CANT_CREATE
at: _update_swap_chain (drivers/vulkan/vulkan_context.cpp:1864)
ERROR: Condition "err != OK" is true. Returning: ERR_CANT_CREATE
at: _window_create (drivers/vulkan/vulkan_context.cpp:1479)
ERROR: vkCreateRenderPass2KHR failed with error -7.
at: (drivers/vulkan/rendering_device_vulkan.cpp:3969)
@dzil123 Have you tried updating your drivers?
Also, can you please check that your GPU supports Vulkan by downloading the Vulkan SDK and running the vkcube example?
Ideally Godot would be able to detect if Vulkan is supported or not and give you an appropriate warning message while it falls back to OpenGL
When I try to update drivers from the Intel website, I get this error message:
A customized computer manufacturer driver is installed on your computer. The Intel Driver & Support Assistant is not able to update the driver. Installing a generic Intel driver instead of the customized computer manufacturer driver may cause technical issues. Contact Hewlett-Packard (HP) for the latest driver for your computer.
When I try to update drivers from the HP, it says that the driver version installed is already the latest version.
vkcube:
Exported json from the Vulkan Capability Viewer: IntelR_UHD_Graphics_620.json.txt
Trying to run the Godot v4.0.beta6 editor from the Vulkan Configurator with validation layers and debug logging shows the Godot window opening and closing by itself, with this output: Godot_v4.txt
Is it possible that the drivers only support Vulkan 1.1 but Godot requires Vulkan 1.2? If that's the case, Godot should detect this and show an error message.
Can you pull master and rerun with verbose? My PR for changing the extension handling just got merged and at the very least it will dump out all supported extensions now.
When I try to update drivers from the Intel website, I get this error message:
A customized computer manufacturer driver is installed on your computer. The Intel Driver & Support Assistant is not able to update the driver. Installing a generic Intel driver instead of the customized computer manufacturer driver may cause technical issues. Contact Hewlett-Packard (HP) for the latest driver for your computer.
When I try to update drivers from the HP, it says that the driver version installed is already the latest version.
Yeah this is very poor support from HP's side. This "customized" driver is BS, it just means that it's the version that HP tested on this hardware and confirmed that it works... back in 2018... https://www.intel.com/content/www/us/en/developer/articles/news/new-1006025-intel-graphics-driver-for-windows-10-64-bit-6th-7th-8th-generation.html
Then HP just stopped caring about this specific product and they never validated any further official Intel driver pack. But Intel still fully supports UHD Graphics 620 and you can install the latest Intel drivers, you just need to remove this needless roadblock that HP is putting in your way.
The latest for your hardware is: https://www.intel.com/content/www/us/en/download/19344/intel-graphics-windows-dch-drivers.html
Intel themselves mention the problem I outlined above in the fine print:
Installing this Intel generic graphics driver will overwrite your computer manufacturer (OEM) customized driver. OEM drivers are handpicked and include customized features and solutions to platform-specific issues. The generic Intel driver provides users the latest and greatest feature enhancements and bug fixes that OEMs may not have customized yet to address platform-specific needs. Users can check for matching OEM versions at OEM websites.
Are you still experiencing an error preventing the driver update? Look here for why and a solution.
That being said, we definitely want things to fail explicitly when the drivers do not support what we need, so indeed if you can test the latest master
to see if it's better before upgrading drivers, that would be useful. You can get artifacts from master from the CI e.g. here: https://github.com/godotengine/godot/actions/runs/3544388277
Can you pull master and rerun with verbose?
Here's the output log from 3 back-to-back runs from the cdfef0c85 windows-editor CI artifact: message.txt. Now there's a handled crash, but no real backtrace. The log is different for each run.
https://www.intel.com/content/www/us/en/download/19344/intel-graphics-windows-dch-drivers.html
Yes, gfx_win_101.3790_101.2114.exe
is what I tried the first time and what gave the "customized OEM driver" message and would not let me proceed. I will try a manual install with the zip.
When I try to update drivers from the HP, it says that the driver version installed is already the latest version.
So something weird happened with the drivers. As I said earlier, the installed driver version matched the version on HP's website, 24.20.100.6025. I decided to download HP's drivers anyway. When I installed them, Vulkan was completely removed from the system. There was no Vulkan loader, and everything from the Vulkan SDK and Godot gave a proper 'vulkan not found' error message (even though the listed driver version was the same!). I was able to restore the old drivers by going to Device Manager -> Update Drivers -> Browse my computer for drivers -> Let me pick from a list of available drivers on my computer. The above 3 tests are from after restoring the 24.20.100.6025 drivers with Vulkan.
After installing 31.0.101.2114 from the 'Update Drivers -> Browse my computer for drivers' on the extracted gfx_win_101.3790_101.2114.zip
, Godot Vulkan works flawlessly. working.txt
Not solution yet, I tried all, but godot 4 beta 6 (and 1, 2, 3, 4, 5) dont´t work with vulkan 1.1
same problem in beta 7, dont´t work with vulkan 1.1
@papatv Which GPU model do you have, and which driver version are you using?
Hi, I using a laptop Lenovo Edge 2 in this case... has Windows 10, Intel(R) HD Graphics 520 and Vulkan API 1.1.0
same problem in beta 8
Godot Engine v4.0.beta8.official.45cac42c0 - https://godotengine.org OpenGL Renderer: Intel(R) HD Graphics 520
Editing project: C:/Users/arqsa/Desktop/eje2godo4 Godot Engine v4.0.beta8.official.45cac42c0 - https://godotengine.org Vulkan API 1.1.70 - Using Vulkan Device #0: Intel - Intel(R) HD Graphics 520
Godot version
v4.0.beta5.official.89a33d28f
System information
Windows 10, Vulkan, Intel UHD Graphics 620, 24.20.100.6025
Issue description
When running the editor or project manager with the Vulkan renderer, the window opens but is blank. It behaves as if everything is working correctly, including changing cursor when mousing over appropriate ui elements and responding to button presses with new windows. Sometimes, the editor will close on its own after a delay, with no interaction.
There are no relevant errors reported, even with
--verbose
. The drivers are updated to the latest version from the laptop manufacturer's website.Everything is working as normal under the OpenGL renderer, this only happens with Vulkan.
Screenshot of the blank window, after blindly clicking the Import Project button: (The windows actually have the Godot-themed dark gray background color, but the screenshot tool failed to capture this)
Video of the blank editor closing by itself after a delay with no interaction: (run on a default empty project)
https://user-images.githubusercontent.com/5725958/203510805-5cc8c169-c732-498e-a3bd-bcad360e7274.mp4
Output of
vulkaninfo
: vulkaninfo.txtExpand output log:
Note: theC:\ProgramData\obs-studio-hook\.\graphics-hook64.dll
error is unrelated since this issue has occurred even before I installed OBS.Steps to reproduce
Project manager:
godot.exe --rendering-driver vulkan -p
Editor:
godot.exe --rendering-driver vulkan --path ... -e
Command line used in video:
Godot_v4.0-beta5_win64_console.exe --verbose --rendering-driver vulkan --path D:\godotproject1 -e
Minimal reproduction project
N/A