VirtualDisplay/Virtual-Display-Driver

[Bug]: Failed to initialize Direct3D error when launching certain games

Opened this issue · 4 comments

Which OS?

Win11 Home

Which release?

24H2

Describe the bug

When launching the game Judgment on Steam, with the VDD as the primary display, I get the error message below:
image

A debug log of the game launch is attached.

Steps to reproduce

No response

Expected behavior

No response

Log File (Beta Only)

DEBUG_Judgmen.txt

Contact Details

No response

Bare with me, just testing, may have fixed it :)

I also just realised, this works completely fine for me.

Do me a favour, do the experiment again but this time, restart the driver first and provide a full debug log from driver start to when the issue occurred.

Edit: I have to say, fun game though

I also just realised, this works completely fine for me.

Do me a favour, do the experiment again but this time, restart the driver first and provide a full debug log from driver start to when the issue occurred.

Edit: I have to say, fun game though

The debug log that I attached contains exactly that-

  1. I enabled debug logging, and then disabled VDD in device manager
  2. I deleted the existing .log file
  3. Enabled VDD
  4. Ran Sunshine and then connect my Moonlight Client (my IPhone at 1600x828)
  5. Started Judgment via Steam

Yes it is super fun, i absolutely love the whole Yakuza franchise :)

The debug log you attached doesn't show it from start-up. if it did you'd be able to see "driver starting" in it. Instead the log you provided starts with abandoning swap chain

Yeh, i must've bought it a while back and not even realised, I went to see if i had it and turned out I did, not a game to play on a 60% keyboard though, I'll tell you that