Crash on Screen.MoveMainWindowTo | Official Unity Discord | Page 1

median rose Jul 31, 2025, 1:37 AM

#

I am getting this error message in the logs: "D3D12Fence::Wait(2190) error: got 2189. May cause crash or visual artifacts"

Anyone have any ideas as to why I might be seeing this? This is on Unity 6.1.10

forest knoll Jul 31, 2025, 1:50 AM

#

DX12 is just in its infancy with Unity and there's a lot of crashes

#

Try DX11 until the issues are fixed

median rose Jul 31, 2025, 2:40 AM

#

Don't most games use DX12 these days? Or am I mistaken?

forest knoll Jul 31, 2025, 2:47 AM

#

DX12 is the default graphics backend in Unity as of 6.1 and was introduced in 2023.1
As far as graphics APIs go it's not all that old in Unity

sick leaf Jul 31, 2025, 3:37 AM

#

It's likely an issue unique to the editor too.

median rose Jul 31, 2025, 3:49 AM

#

sick leaf It's likely an issue unique to the editor too.

Ah, I should clarify that this crash only happens when the game is built

sick leaf Jul 31, 2025, 3:56 AM

#

Are you doing some custom rendering, using graphics command lists or anything else that could be related in the project? Or using third party assets/pluging that could be doing that?

#

Maybe using custom compute or other shaders?

median rose Jul 31, 2025, 4:29 AM

#

No. It's crashing when using Screen.moveMainWindowTo repetitively

sick leaf Jul 31, 2025, 4:45 AM

#

median rose No. It's crashing when using Screen.moveMainWindowTo repetitively

Are you making sure the previous async operation is complete before calling it again?

median rose Jul 31, 2025, 4:46 AM

#

sick leaf Are you making sure the previous async operation is complete before calling it a...

I am not, that could be it!

sick leaf Jul 31, 2025, 4:47 AM

#

Yeah, that might be the cause. Though, I'd expect unity to provide some kind of feedback mechanism if that was the cause.
https://docs.unity3d.com/6000.1/Documentation/ScriptReference/Screen.MoveMainWindowTo.html

#

Maybe fill a bug report regardless of wether that fixes the issue or not

median rose Jul 31, 2025, 3:20 PM

#

Switching to DX11 seems to have fixed the issue. I was reading somewhere that exclusive fullscreen support is not the same with DX12 as it is with DX11, could that be my issue?

#

I would like to use DX12 if possible

sick leaf Jul 31, 2025, 11:44 PM

#

Yep. D3d12 is typically stricter and will crash sooner if you do something fishy. D3D11 is a bit lore forgiving in that sense.
Did you try making sure you're not calling that move method before the previous move is complete?

median rose Aug 1, 2025, 3:38 AM

#

I need to test that tomorrow to see. I need to add more logs and isolate my test some more since I have other stuff running as well. Will report back

#Crash on Screen.MoveMainWindowTo