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

Crash on editor startup when choosing forward or mobile rendering - 4.0.3-stable onward #80760

Closed
Alireza-Ta opened this issue Aug 18, 2023 · 4 comments

Comments

@Alireza-Ta
Copy link

Godot version

v4.0.3.stable.official.5222a99f5

System information

Windows 10.0.19045 - Radeon RX 560 Series (Advanced Micro Devices, Inc.; 31.0.21023.2010) - AMD FX-9830P RADEON R7, 12 COMPUTE CORES 4C+8G (4 Threads)

Issue description

Hi there!
I can't create new projects with forward or mobile rendering with versions after 4.0.3-stable onward(tested 4.0.4-stable, 4.1-stable, and 4.1.1-stable).
When I hit the create button it only shows a blank editor screen and crashes.

Actually Godot 4.1-stable shows the wrong Vulkan API version. The 1.2.170 below is for my integrated GPU, however, Godot 4.0.3-stable console output is correct.

Godot Engine v4.1.stable.official.970459615 - https://godotengine.org
Vulkan API 1.2.170 - Forward+ - Using Vulkan Device #0: AMD - Radeon RX 560 Series
Godot Engine v4.0.3.stable.official.5222a99f5 - https://godotengine.org
Vulkan API 1.3.250 - Forward Mobile - Using Vulkan Device #0: AMD - Radeon RX 560 Series

I also updated my GPU driver and nothing changed!
Maybe this #73450 is the culprit!

Thanks!

Steps to reproduce

Crash if I choose forward or mobile rendering at the project creation.

Minimal reproduction project

Crash if I choose forward or mobile rendering at the project creation.

@Calinou
Copy link
Member

Calinou commented Aug 18, 2023

The workaround in #73450 likely needs to be made optional, so that you can set the value to 0 explicitly to disable it on problematic hardware/software combinations. There are still a lot of people who use AMD + NVIDIA setups with old graphics drivers, so we can't disable this workaround by default just yet.

Are your drivers for the integrated graphics and the dedicated GPU fully up-to-date (from the AMD website, not your OEM, not Windows Update)?

You can also try running Godot with the --verbose command line argument, and use --gpu-index N to force a specific GPU to be used.

@Alireza-Ta
Copy link
Author

Are your drivers for the integrated graphics and the dedicated GPU fully up-to-date (from the AMD website, not your OEM, not Windows Update)?

Yes. I updated through AMD Sofware: Adrenalin Edition. (Version 23.7.2, July 20th, 2023)

You can also try running Godot with the --verbose command line argument, and use --gpu-index N to force a specific GPU to be used.

Actually tried it before and still crashes with different indices (0,1,2)!

@Calinou
Copy link
Member

Calinou commented Oct 23, 2023

If you can still reproduce this on 4.1.2 or 4.2.beta2, see this comment: #82840 (comment)

@Alireza-Ta
Copy link
Author

4.2.beta2 seems solved the issue! No need to reinstall GPU drivers.

Thanks!

@AThousandShips AThousandShips added this to the 4.2 milestone Oct 24, 2023
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