moonlight-qt icon indicating copy to clipboard operation
moonlight-qt copied to clipboard

Steam Deck - Games / Steam Big Picture starting and exiting immediately

Open Kvoo opened this issue 2 years ago • 4 comments

Installed Moonlight on my Steam deck and enabled everything on my PC. When I go to start a game or Steam Big Picture via Moonlight, it does start and set the correct resolution on the Host PC, but instantly exits out on my steam deck, back to the games screen. I then have the option to resume or quit the game. When resuming, it instantly exits out again.

I've attached the NvStreamer log from my Host PC. Help would be greatly appreciated.

NvStreamerCurrent.log .

Kvoo avatar Aug 19 '22 19:08 Kvoo

Yeah, it looks like there is an internal error in the driver that is causing display capture to fail:

#3(W)[2022-08-19 19:02:39,738]=21:02:39={5608}<Fbc7FrameProvide> Capture failure, reported capture resolution is 0 x 0 pitch 0. Writing a black frame.
#4(I)[2022-08-19 19:02:39,738]=21:02:39={5608}<Fbc7FrameProvide> Capture resolution is now 1280 x 720 pitch 0.
#5(E)[2022-08-19 19:02:39,738]=21:02:39={5608}<Fbc7FrameProvide> Failed to grab frame: -19 (Unknown FBC result code).
#6(E)[2022-08-19 19:02:39,738]=21:02:39={5608}<CaptureThread>    Failed to capture frame 2.
#7(I)[2022-08-19 19:02:39,738]=21:02:39={5608}<CaptureThread>    Finished with status STATUS_GRAB_ERROR after capturing 2 frames
#8(I)[2022-08-19 19:02:39,738]=21:02:39={5608}<CaptureThread>    Dropped 0 frames (0.000%)
#9(I)[2022-08-19 19:02:39,738]=21:02:39={5608}<CaptureThread>    Capture ended abnormally
#0(D)[2022-08-19 19:02:39,738]=21:02:39={5608}<NvThread>         Completed thread function for native thread: CaptureThread (thread id: 00000000000015E8)
#1(I)[2022-08-19 19:02:39,738]=21:02:39={17276}<Server>           Server has been asked to stop.
#2(I)[2022-08-19 19:02:39,738]=21:02:39={17276}<Server>           Server is now in state 1004
#3(I)[2022-08-19 19:02:39,738]=21:02:39={17276}<Server>           Server has been asked to end the current streaming session.
#4(D)[2022-08-19 19:02:39,738]=21:02:39={17276}<Server>           Closing the streaming session...

I noticed in the logs that you're not running a normal production Nvidia driver. It seems like you're running one of Nvidia's preview drivers and running the Windows 11 Insider Preview Dev ring. I suspect that the driver installation may be the reason NvFBC doesn't work.

#1(I)[2022-08-19 19:02:25,004]=21:02:25={17276}<GPUInfo>          Windows 10.0.25179.1000, DD version 525.26: using NvAPI_Coproc_GetCoprocInfo workaround.
...
#7(I)[2022-08-19 19:02:25,060]=21:02:25={17276}<AdapterContext>   Driver version is 525.26, branch is bugfix_main.

Try installing the latest official production Nvidia driver and see if that fixes it.

cgutman avatar Aug 20 '22 00:08 cgutman

Are you sure about the driver? I‘m running a normal driver installed via GeForce Experience, nothing special

Kvoo avatar Aug 20 '22 08:08 Kvoo

Yes, pretty sure. Remember that Windows Update (especially in Insider Preview) can update your driver without you knowing.

What does GeForce Experience say your driver version is?

cgutman avatar Aug 20 '22 16:08 cgutman

Yeah I noticed, the gpu driver was a preview version. I tried removing it and installing the newest production version, but that makes my PC just crash every few minutes (A problem I had before with the dev channel)

I guess I‘ll do a clean install so I can move out of the dev channel.

Kvoo avatar Aug 20 '22 16:08 Kvoo

Did moving out of the dev channel fix this? I just updated to the beta channel to get tabs on explorer and now experience this issue.

reyqn avatar Sep 30 '22 20:09 reyqn

Same problem with windows 11 stable

legendcodermartino1245 avatar Feb 10 '23 09:02 legendcodermartino1245

Same problem with windows 11 stable

legendcodermartino1245 avatar Feb 10 '23 09:02 legendcodermartino1245