search

m4dEngi / RemotePlayWhatever

Tiny application that lets you force remote play together any game you have in your steam library including non-steam ones.
MIT License
1.02k stars 37 forks source link

Workaround for Input Issues #129

Open PatMillman opened 8 months ago

PatMillman commented 8 months ago

I believe that many have come to the conclusion that inputs not being detected is stemming from using Spacewar as a Donor Title, I have changed the ID to that of Polyrunners. Supposedly this acts as a fix for this issue.

m4dEngi commented 8 months ago

You can already set AppID for non-steam games to any value using --appid command line argument.

I don't think we can safely rely on a hardcoded third party appid that is not included in the base subscription for accounts.

moraroy commented 1 month ago

@m4dEngi this is interesting as I was also having input issues I didn't know there was a command line! Could this be ran everytime the RPW.exe is ran? RPW.exe --123456789 ? This is for the steam deck btw

m4dEngi commented 1 month ago

@m4dEngi this is interesting as I was also having input issues I didn't know there was a command line! Could this be ran everytime the RPW.exe is ran? RPW.exe --123456789 ? This is for the steam deck btw

You can create a desktop shortcut and pass the appid you want as the startup argument, `RemotePlayWhatever --appid '. For non-Steam games, however, the input is a bit more complicated.

moraroy commented 1 month ago

@m4dEngi interesting ok, I will test that, I may be actually to fix the main problem as I have access to the steamclient api through my plugin in the decky loader. The issue is the api correct? From what I've been reading.

m4dEngi commented 1 month ago

@m4dEngi interesting ok, I will test that, I may be actually to fix the main problem as I have access to the steamclient api through my plugin in the decky loader. The issue is the api correct? From what I've been reading.

My guess is that to fix the input/guest input issue, we need to find a way to correctly initialize the steam api from within a non-steam process.

moraroy commented 1 month ago

@m4dEngi I was doing some testing... on both a windows PC and the steam deck and an android phone. It seems using that command in the launch options of the RemotePlayWhatver works for the majority of things. I used apid 0 instead of a random game app I'd to avoid relying on the game. It seems to work fine. --appid 0

m4dEngi commented 1 month ago

@m4dEngi I was doing some testing... on both a windows PC and the steam deck and an android phone. It seems using that command in the launch options of the RemotePlayWhatver works for the majority of things. I used apid 0 instead of a random game app I'd to avoid relying on the game. It seems to work fine. --appid 0

What about controller profiles?

moraroy commented 1 month ago

20240514165059_1.jpg

20240514165039_1.jpg

I'm not sure if this is what you mean by controller profiles. But this test here was done on the Steam Deck as host, with only the Android Phone connected using Touch Screen Controls. The "RemotePlayWhatever" shortcut was used in the background with "--appid 0" in the launch options. And the game I'm playing is a Non-Steam version of Overcooked. It seems I was able to control the profiles of each connected device? @m4dEngi

crudyy commented 1 month ago

@moraroy I applied the --appid 0 as the launch option, and everything is working smoothly. But whenever I try to use emulators like PCSX2 for remote play, the sound doesn't pass on to my clients. Did you find a fix for that? Other non-steam games just work fine.