DX11 games having black screen, audio and input still works

[desmvu]

I tried streaming Witcher 3 in DirectX 11 mode using Moonshine, audio works and input works but screen is black. I have tried restarting the streaming server, didn't work, tried DX12 mode and it works.

My streaming server:

• AMD Ryzen 7800x3D
• 32gb RAM DDR5
• RTX 3080 10gb
• cachyOS 7.0.9, KDE Plasma
• Moonshine 0.11.0

My streaming client:

• AMD Ryzen 5600x
• 24gb DDR4
• RTX 3060
• cachyOS 7.0.9, KDE Plasma
• Moonlight Flatpak

[hgaiser]

Thanks for the report! Luckily I have Witcher 3 so I can test this locally :).

[desmvu]

To clarify, DX12 mode now also doesn't work. Same issue, video is black but audio and input works. I think DX12 worked because I was on 0.10.0 and I just coincidentally switched to DX11 when I updated Moonshine to 0.11.0.

[mrhexzero]

Can confirm this is also an issue on CEMU

[hgaiser]

For me, Witcher 3 works both in DX11 and DX12 mode. Can you try with the latest moonshine-git build (or if you are running from source directly, make sure the moonshine-wsi layer is installed).

I also tried with moonshine v0.11.0, which also works =\

Note: there was an issue with Witcher 3 not receiving keyboard and mouse input, which should be resolved with #108

[hgaiser]

This bug has been driving me insane. I was testing #108 and got black screen with Witcher 3. I thought great, then I can debug this issue.

I was debugging it, found some potential causes but nothing worked. I tried "wrapping" Baldurs Gate 3 (which had the same issue) with gamescope by setting launch options. That worked (except for HDR, but that doesn't surprise me that much). I revert back to normal launch options and then that too works 😕 . No matter what I do I can't get it to break now. I tried rebooting, reverting to older versions, clearing caches.

This aligns vaguely with what you were seeing @desmvu , where you thought DX12 worked but then all of a sudden it too didn't work.

There's a really interesting but annoying bug here.. it could be some race condition that for some reason doesn't trigger for me anymore, but I can't really debug it further now. Plus it has drained me of my sanity, so I need to look at something else for a bit 🥲

[HighKing81]

I think I'm running into a similar issue. A lot of games work fine as long as I keep moving the mouse. After 3 seconds the screen goes black. Only mouse imput fixes it... for 3 seconds.

Black Mesa just stays on screen when I'm not moving. Both the native Linux version that uses ToGL and the Windows variant through DXVK have no issues.

Mouse P.I. for Hire defaults to dx11 and goes black after 3 seconds when I don't move the mouse.
When I use -force-d3d12 it's even worse, not even mouse movement (pun not intended) makes it appear.

Encodya, which uses OpenGL is no problem at all.

Initial Drift Online, dx11, goes black if I don't move the mouse every 2-3 seconds.

Down the Rabbit Hole flattened defaults to dx11 and goes black if I don't touch the mouse for 3 seconds.
Using -force-d3d12 this behaviour is the same.

I guess this comment is not much more than a basic 'me too!', and I'm not even sure it's the same issue. But I do wonder if mouse movement fixes it for 3 seconds on your end as well. :)

[guerra08]

I do have this issue in Hades 2 for example, will try to get some more details on it.

[schlegp]

I had this same issue when streaming Outward Definitive Edition.
When testing I realized this happens exactly when the cursor disappears.

Setup

• Host: Arch Linux, AMD Radeon RX 7900 XTX (RADV NAVI31)
• Moonshine latest
• H.264 encode (pixelforge), virtual output 1920x1080 @ 120Hz
• Client: Moonlight on macOS

I built and ran the current latest git version and realized this was then reduced to a flicker, instead of a full black screen.
Decided to use AI to help me diagnose and it seems to happen when the compositor switches between the GBM path (format ABGR8888 → InputFormat::RGBA) and the direct-scanout path (format ARGB8888 → InputFormat::BGRx).

Forcing the Compositor state to always use the GBM path removes the flickering, at the cost of the benefits of direct scanout.

Hope this additional info helps.

[schlegp]

Okay, dug a bit deeper and found a proper fix for the issue I was experiencing.
The bug is in pixelforges ColorConverter::convert() function. When importing a DMA-BUF for the first time the image is created with "VK_SHARING_MODE_EXCLUSIVE". According to Vulkan Spec this would then have to perform a "queue family acquire", transitioning the ownership from "VK_QUEUE_FAMILY_INTERNAL" to the importing queue family.
When this is not done the GPU cache is never invalidated and the shader reads zero data from the imported image.

Fix in pixelforge (src/converter/mod.rs): When src_layout is UNDEFINED (fresh import), set srcQueueFamilyIndex = VK_QUEUE_FAMILY_EXTERNAL and dstQueueFamilyIndex to the encoder's compute queue family. This performs the required acquire, making the external memory contents visible. Also fixes the srcAccessMask which must be 0 for UNDEFINED layout per spec.

I created a fork of pixelforge and will create a PR for this.
If you want to try it out beforehand, add this to your Cargo.toml before building:
[patch."https://github.com/hgaiser/pixelforge"]
pixelforge = { git = "https://github.com/schlegp/pixelforge", branch = "fix/queue-family-acquire" }

Hopefully this does not fix only my issue.

[hgaiser]

Merged pixelforge PR and updated the dependency in moonshine main. Could try it out and let me know if it fixes the issue for you?

[desmvu]

I found out that if I set my Moonlight client at 1080p, it works, but if I set it at 4K 60fps, Steam Big Picture works and game is a black screen. Hopefully we can get 4K working in the future. For me, the issue still persists on the latest 0.12.0 update.

[hgaiser]

I found out that if I set my Moonlight client at 1080p, it works, but if I set it at 4K 60fps, Steam Big Picture works and game is a black screen. Hopefully we can get 4K working in the future. For me, the issue still persists on the latest 0.12.0 update.

Do you mean the latest commit, or are you running v0.12.0?

[desmvu]

Do you mean the latest commit, or are you running v0.12.0?

I am running v0.12.0