Plex Arcade issue

I can only play Plex Arcade games on my devices, at home, if I am actively logged into my server. If I lock the Windows “server” (Windows 10), the games no longer work. Tested on iPhone and my laptop. As soon as I go back and either unlock the server locally, or through remote desktop, it again works on both my iPhone and laptop. It seems something may be blocked when there is not an active session on the server (Windows 10 Plex Media Server). I don’t recall this happening in the past. I’m not certain if it’s a known issue or something with my setup that changed (updates, etc.)

Thanks in advance for any assistance given.

I am able to still play games locally with my Windows 10 server locked. I would check your power settings and make sure your computer isn’t set to go to sleep. PMS does not work if your computer is sleeping.

Check power settings for graphics card. Might be to do with power saving stopping transcoding when screen is locked

Thanks for the suggestion. I am configured for Ulitmate Performance in power settings, with no sleep or hibernation by default. I also spot-checked them to ensure there wasn’t a glitch.

Thank you. I checked in the AMD Radeon Software, and see no power savings options. I am running AMD Radeon version 21.5.1.

Pretty sure the Radeon’s arent supported for Parsec. Would need a GTX card

They are supported.

“AMD Radeon HD 7750 or better” -The RX 560 I have is newer and better than this minimum required for Parsec.

Here is the error I get in Chrome, from my laptop, when I do not have an active session running on my server:

An unknown error occurred.

Error code: -1073741819 (Unknown)

If I RDP in, the error goes away and I can play in Chrome on my laptop.

Not sure if this helps.

I have found that it is not an issue with the server being locked, it is an issue with not having an open RDP session. Even If I lock the session, it still works. Since the RDP session makes the server supply a video signal, does that mean that my issue lies with the server not sensing a display when it’s idle? Odd one…

I don’t know since I am able to connect to my server even when locked. There must be some other associated feature that is preventing things from working.

Can you try playing a game without using RDP then grab the PMS logs after the failure? Then play a game with RDP and get me another log so I can compare.

are you logged in locally at the server? I found i needed am HDMI dongle plugged into my 1080ti as i was running on a server with dual graphics cards in and I always have my server logged in and locked as plex only starts upon login. If you log in using “mstsc.exe /console” then when you exit the rdp session it stays connected.

Is your server headless?

The server has a mouse and kb connected, and is run over HDMI to an LED TV presently. If I log into the server locally, then lock the session and power off the TV, Arcade works on my devices for a couple hours then stops. Maybe the TV goes from standby to a deeper power off state and the server no longer detects a display. I am going to order one of the HDMI “dummy” device dongles and see what happens. I think this may do the trick, I’ll update after. Thanks all.

So, I added the fitHeadlessGS and still have the same issue. Works great when I have an active session on the PMS, as discussed prior. When I close RDP out, I get this in the system log:

Faulting application name: Plex Game Transcoder.exe, version: 0.0.0.0, time stamp: 0x60a65932
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process id: 0x40f4
Faulting application start time: 0x01d766af6795a104
Faulting application path: E:\Program Files (x86)\Plex\Plex Media Server\Plex Game Transcoder\Plex Game Transcoder.exe
Faulting module path: unknown
Report Id: 65a0ba3e-43a5-4791-b055-8f914d1635f3
Faulting package full name:
Faulting package-relative application ID:

When I have an active RDP session on the PMS, the Transcoder does not crash.
What would make the transcoder crash when there is no active RDP or local session?

Thanks

This is in the Plex Game Transcoder.log at about the same instance…

Jun 21, 2021 11:09:17.417 [0x00002cd4] DEBUG - Starting up with core: C:\Users\admin\AppData\Local\Plex Media Server\Game Cores\fceumm_libretro.dll and game: E:\PLEX MEDIA\NES\1942\1942\1942.NES platform: Nintendo Entertainment System.
Jun 21, 2021 11:09:17.422 [0x00002cd4] DEBUG - Parsec: hostname = JEFF_MEDIA
Jun 21, 2021 11:09:17.422 [0x00002cd4] DEBUG - Parsec: ctrl_support = 0
Jun 21, 2021 11:09:17.423 [0x00002cd4] WARNING - Retro: Unhandled env #35
Jun 21, 2021 11:09:17.423 [0x00002cd4] DEBUG - Setting pixel format to RGB565.
Jun 21, 2021 11:09:17.423 [0x00002cd4] INFO - Frontend supports RGB565 - will use that instead of XRGB1555.
Jun 21, 2021 11:09:17.423 [0x00002cd4] WARNING - Retro: Unhandled env #8
Jun 21, 2021 11:09:17.423 [0x00002cd4] DEBUG - Retro: Asked for save directory.
Jun 21, 2021 11:09:17.423 [0x00002cd4] INFO - Loading E:\PLEX MEDIA\NES\1942\1942\1942.NES…

Jun 21, 2021 11:09:17.424 [0x00002cd4] INFO - PRG-ROM CRC32: 0xC4E8C04A
Jun 21, 2021 11:09:17.424 [0x00002cd4] INFO - PRG+CHR CRC32: 0x171251E3
Jun 21, 2021 11:09:17.424 [0x00002cd4] INFO - PRG+CHR MD5: 0x0b66fdf88964235c434daff62837af60
Jun 21, 2021 11:09:17.424 [0x00002cd4] INFO - PRG-ROM: 2 x 16KiB
Jun 21, 2021 11:09:17.424 [0x00002cd4] INFO - CHR-ROM: 1 x 8KiB
Jun 21, 2021 11:09:17.424 [0x00002cd4] INFO - Mapper #: 0
Jun 21, 2021 11:09:17.424 [0x00002cd4] INFO - Mapper name: NROM
Jun 21, 2021 11:09:17.424 [0x00002cd4] INFO - Mirroring: Horizontal
Jun 21, 2021 11:09:17.424 [0x00002cd4] INFO - Battery: No
Jun 21, 2021 11:09:17.424 [0x00002cd4] INFO - System: NTSC
Jun 21, 2021 11:09:17.424 [0x00002cd4] INFO - Trained: No
Jun 21, 2021 11:09:17.424 [0x00002cd4] INFO - FCEU_MakeFName: C:\Users\admin\AppData\Local\Plex Media Server\Game Saves\1\937af1326ff647b394bbac7047e1ea6af7de6d5\1\nes.pal
Jun 21, 2021 11:09:17.425 [0x00002cd4] WARNING - Retro: Unhandled env #52
Jun 21, 2021 11:09:17.426 [0x00002cd4] WARNING - Retro: Unhandled env #55
Jun 21, 2021 11:09:17.426 [0x00002cd4] WARNING - Retro: Unhandled env #55
Jun 21, 2021 11:09:17.426 [0x00002cd4] WARNING - Retro: Unhandled env #55
Jun 21, 2021 11:09:17.426 [0x00002cd4] WARNING - Retro: Unhandled env #55
Jun 21, 2021 11:09:17.426 [0x00002cd4] WARNING - Retro: Unhandled env #55
Jun 21, 2021 11:09:17.426 [0x00002cd4] WARNING - Retro: Unhandled env #55
Jun 21, 2021 11:09:17.426 [0x00002cd4] WARNING - Retro: Unhandled env #55
Jun 21, 2021 11:09:17.426 [0x00002cd4] WARNING - Retro: Unhandled env #55
Jun 21, 2021 11:09:17.426 [0x00002cd4] WARNING - Retro: Unhandled env #55
Jun 21, 2021 11:09:17.426 [0x00002cd4] WARNING - Retro: Unhandled env #55
Jun 21, 2021 11:09:17.426 [0x00002cd4] WARNING - Retro: Unhandled env #55
Jun 21, 2021 11:09:17.426 [0x00002cd4] WARNING - Retro: Unhandled env #55
Jun 21, 2021 11:09:17.426 [0x00002cd4] WARNING - Retro: Unhandled env #55
Jun 21, 2021 11:09:17.426 [0x00002cd4] INFO - FPS reported as 60.099827.
Jun 21, 2021 11:09:17.433 [0x00002cd4] DEBUG - OpenGL: Creating a context for OpenGL v3.

The issue appears to be resolved after rolling back my GPU driver. It has been working since late yesterday afternoon without any interaction needed on the PMS. Thanks all.

1 Like

what RDP session are you using? normal or console? need to use console so you are logging into the local session and then rather than logging off when exiting RDP you simply close it and it leaves the local session active.

I was using a normal RDP session, then locking the session. -Not logging off the session.
Would a console session have made a difference? Not a big deal now, as it has been working flawlessly for days since rolling back my GPU drivers. Thanks again.

a console session logs you into the active local session on the computer rather than a new remote session. i use console after restart as Plex is set up to run at login so when i log in after a reboot remotely and then exit RD then my session is a local active session on the server as if I had physically logged onto the server itself and then locked it

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.