Unresponsive, glitched, or black screen when loading new projects

[Infomanic]

Tested versions

Reproduced in 4.6 Forward+ and Mobile.
Not reproduced in 4.6 Compatibility.
Not reproduced in 4.5.

System information

Windows 10, AMD PRO A10-8700B R6, 4 core, AMD Radeon R6, 64 bit system, D3D12 (i think).

Issue description

Loading up new projects with Forward+ or Mobile on 4.6 causes either permanent unresponsiveness (white screen), or loading a complete black screen when loading.
Issue not reproduceable on compatibility or 4.5's Forward+.
Running ported projects from 4.5 gives this in 3D view, no issues in 2D.

Attempted to run with verbose, got a strange glitched screen and the following errors.

Loading in mobile gives this sometimes, and a similar error to the one above some other times.

Probably related to DX12, unsure of why and why turning off fallback to DX12 doesn't affect the issue.

To summarize, Forward+ and Mobile keep choosing D3D12 forcibly regardless of any settings or even startup commands, as visible in the cmd panel + verbose setting, it subsequently fails at running D3D12 correctly.

To be clear, D3D12 and related dlls are installed on the system (version 10.0.19041.5794), and D3D12 using games run perfectly okay.
To be clear 2, the projects run fine in compatibility and run fine in 4.5, 4.6 seems to have changed priority to D3D12 while also not being able to run D3D12 perfectly on all devices (somehow?), I was able to change different renderers by loading into an old, ported project from 4.5 which still ran even with the bug above.

To be clear 3, Not to be confused with the other major D3D12 rendering issue here, which causes the popups to glitch weirdly, here it causes a crash when booting.

Steps to reproduce

Boot up an entirely new project with 4.6, toggling off DX12 fallback does nothing, unsure of other factors that cause the problem.
You can boot up an old ported project with a visual bug in the 3D view.
This is not reproducible on all devices, but some other devices have had this issue.

Minimal reproduction project (MRP)

N/A

[blueskythlikesclouds]

Does the windows-editor CI build from here work? Keep the D3D12 related DLLs.

https://github.com/godotengine/godot/actions/runs/21489672608

[Infomanic]

Does the windows-editor CI build from here work? Keep the D3D12 related DLLs.

It doesn't.
To summarize, for anybody fixing, since I didn't know this yesterday, Forward+ and Mobile keep choosing D3D12 forcibly regardless of any settings or even startup commands, as visible in the cmd panel + verbose setting.
As a tip for anybody with this issue stumbling upon this page, I heavily recommend either regressing to 4.5 or porting a project from 4.5, running it in Forward+ and changing to compatibility.

[AThousandShips]

How are you forcing Vulkan? I can't replicate it always choosing D3D12

[blueskythlikesclouds]

Can you try these steps?

Open an Administrator PowerShell window and run the following command:

Add-WindowsCapability -Online -Name "Tools.Graphics.DirectX~~~~0.0.1.0"

This'll install D3D12 debug layers so we can figure out what's going on. It might take a while to complete.

Then download and run dbgview64.exe:

https://learn.microsoft.com/en-us/sysinternals/downloads/debugview

Afterwards, run Godot in the command line with the following arguments:

--rendering-driver d3d12 --gpu-validation

When you see CreatePipelineState errors, DbgView should print details about what went wrong. Please show these here.

[Infomanic]

@blueskythlikesclouds

It seems it can't find D3D12's SDK, D3D12Core.dll is in system32, which is where it should be.
As for 'forcing' Vulkan, I meant setting all the driver settings in the project to use Vulkan and disabling the D3D12 fallback, I'm 'forcing' it to not use D3D12.

APPEND: Ran console exe, got following.

Sorry if I did this wrong, I've never used dbgview64.

[blueskythlikesclouds]

Hmm, it doesn't look like the debug layers got enabled. Otherwise, you should have seen D3D12 related messages. Did you open your project from the project manager? Maybe the command line options don't get transferred to it.

If you did that, could you point at your project's folder with --path option to open it without going through the project manager first? Include --rendering-driver d3d12 --gpu-validation options too, of course.

---

It seems it can't find D3D12's SDK, D3D12Core.dll is in system32, which is where it should be.

These errors are for the Agility SDK specifically. It's looking for D3D12Core.dll placed next to the Godot executable, which is included in CI builds but not the official releases.