Direct3D 11 and two graphics cards

[MattD]

Hello,

First post, long time WinUAE user. It just keeps bringing joy to my life.

I have two displays. Display 1 is an LCD connected to Intel UHD Graphics 630. Display 2 is a CRT connected to an AMD Radeon 200 Series. I use the LCD for RTG and the CRT for native graphics.

This works fine when using Direct3D 9. But when I select Direct3D 11 the native graphics is shown on display 1 instead of on display 2.

I have attached a couple of log files, one for d3d11 and one for d3d9. Also a couple of screenshots from dxdiag, just in case. All WinUAE settings default except for the display on the AMD Radeon being selected for native graphics, fullscreen. And for testing purposes it just boots to the Kickstart 1.3 hand.

Windows 10. WinUAE 4.9.1 (also tried 4.9.2 beta 5).

[Toni Wilen]

Logs look fine.

Are you sure correct display is selected in display panel? There is also no guarantee displays have same ordering in D3D9 vs D3D11 modes.

[MattD]

Thanks for your reply, Toni.

I have double checked that the correct display is selected in the display panel.

In fact, just after clicking start the correct display goes black for a second, but then the output is moved to the other display (in a window that has the same size as the full-screen resolution specified for the other display).

When looking in the log file I notice two "D3D11 Device" entries, first for the AMD Radeon (the correct display), but then further down for the Intel UHD Graphics. Could the first entry be when the correct display goes black for a brief moment and the second entry be when the output appears on the other display?

Thanks again.

[rutra80]

Does it happen in full-window mode?
Also I'd connect both monitors to Radeon and disable Intel UHD in BIOS, not much point using it...

[MattD]

Hi rutra80,

Good question. No, full-window mode does not have the same problem.

I have an elegant setup, If I may say so myself. A single USB-C cable from the computer gives me everything (lcd monitor, keyboard, mouse, speakers, lan) and when I want to connect a Commodore 1084 for beautiful 1:1 native chipset display I use analogue out from a Radeon R7. And it works perfectly with Direct3D 9.

Btw, I was browsing through WinUAE version history and noticed this for 4.0.0: "Direct3D11 fullscreen mode didn’t open if monitor was connected to non-default GPU." Could that be similar to the issue here?

[Toni Wilen]

SetFullscreenState(TRUE) failed 887A0001

887A0001 means invalid call (usually means bad parameters). Driver probably not accepting "something". Possibly some later Windows version introduced "swap effect" parameters (how buffers are swapped)

You can try changing buffering to double buffer but it probably won't help.

AMD Radeon R7 200 Series (CRT Emudriver)

Is that some official driver? Sounds suspicious

[MattD]

Hi Toni,

No, changing buffer didn't make a difference.

Yes, you got me. CRT Emudriver is a patched AMD driver that (re-)enables the ability to output 15kHz modes. It is widely used in the retro arcade business. But no, it's not official and I realise if I'm on my own here.

I will continue to try different resolutions, refresh rates, etc. and report back if I get it to work with Direct3D 11. Otherwise I just stay with Direct3D 9, which serves me pretty well.

Thanks for your time.

[MattD]

Follow up. I can get Direct3D 11 fullscreen to work on my CRT by setting it to the "main display" in Windows' display settings. As long as my LCD is the main display there's a "SetFullscreenState(TRUE) failed 887A0001" when WinUAE tries to open in fullscreen mode on the CRT.