You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you think it would be possible to support connecting just the controller input for NanoClient from a separate application instance? Possibly what I am thinking is having one application do the streaming of audio and video, then having a separate application instance for each controller input. The current code base appears to only be hard coded to support player 1 in the NanoClient.OpenInputChannelAsync function where controllerIndex is hard coded to zero.
Initial attempts I tried failed in apparently StartGameStreamAsync. It is a little difficult to tell exactly where it fails, because the async calls end up timing out, and a relatively generic timeout error is received.
The text was updated successfully, but these errors were encountered:
I dont plan to implement support for multiple controllers in the near future but would be happy to accept a PR for it.
For delivering input events "externally" something like a FIFO or Pipe could be used.
EDIT: Because the change was not trivial, I tried something in branch input_channel. However, looks like it needs a change still to correctly assign Channel in ChannelControl messages.
Do you think it would be possible to support connecting just the controller input for NanoClient from a separate application instance? Possibly what I am thinking is having one application do the streaming of audio and video, then having a separate application instance for each controller input. The current code base appears to only be hard coded to support player 1 in the NanoClient.OpenInputChannelAsync function where controllerIndex is hard coded to zero.
Initial attempts I tried failed in apparently StartGameStreamAsync. It is a little difficult to tell exactly where it fails, because the async calls end up timing out, and a relatively generic timeout error is received.
The text was updated successfully, but these errors were encountered: