Had the same issue. Got a fix, but most of you won’t like it. You have to:
- Build the engine from source yourself.
- Have access to Epic’s P4 Main branch (tricky, most indies don’t have Epic’s P4 at all afaik, non-devs definitely not) OR access to Epic’s github (this is easier, requires just creating several accounts and linking them).
P4: Check the latest commits in the Engine/Source/Runtime/Windows/D3D11RHI folder. The fix was made before this thread even started, on 2nd of June. There are 2 separate commits that when both merged and built resolve the issue.
Github: Here are the links (they will work only if you are logged in and have properly set up the accounts, otherwise you will see error 404):
https://github.com/EpicGames/UnrealEngine/commit/108d0d50f4c394cb2f8a2bf0e9f2052dde4c42e3
https://github.com/EpicGames/UnrealEngine/commit/31d7cf99c275e5c13761542fe459f5db7a91f2f9
You can merge them, or just do the same thing in the source if it’s hard for you to merge from github.
If you have blueprint project - you’re not fixing this.
If you do not build from source and use launcher only - you’re not fixing this.
As far as I can see, those fixes are not merged from Master (or Main in P4 naming convention) into 4.25 or 4.25Plus, so there is no hotfix coming with this change. Especially considering that the fix is on the master for 21 days without a merge.
Hope this helps at least somebody.