@EA_Illium You really aren't getting the message here or listening to your customers. I've worked in the helpdesk field and software engineering and repeatedly asking for our information is not helpful nor will it be helpful in resolving the issue because this is not a crash or an issue with our machines. Also asking for the DxDiag again really means you weren't listening, as @cj_art said this is not a hardware or diver issue because it involves the interaction of your software and Steam Remote Play most notably to the a Steam Deck which does not have DxDiag.
This is widely reported and easy to replicate anyone at EA should be able to do it. Here are the steps
1. Have a PC with Steam and Jedi Survivor
2. Have another device like a Steam Deck, another PC, an Nvidia Shield with Steam Remote Play app, anything that can stream a game from Steam
3. Tell the other device, like the Steam Deck to stream Survivor from your PC
4. Watch the Steam Deck start loading the game, hear the audio from the game but never get past the loading window on the Steam Deck.
5. See that Survivor as successfully launched on the PC and is optimizing files, again why can't that be cached?
Since you insist on the useless information rather than reporting the issue to your team for them to replicate here
- Platform (or client): Steam
- EA ID (PSN ID/Gamertag): evilhamsterdad
- Are you getting an error message? No see above
- If possible, share a Screenshot or Clip... Here's a link to a video of the issue https://photos.app.goo.gl/9CJKigG8XgJAca5B9
- If on PC, please share a DxDiag file and an EA app Error ID Number Attached DxDiag.txt