Possible issues with controller and exiting retroarch #24
-
|
Hey! Great project and I think this is a good start on something I've been looking for for a while. I've got a few questions / issues. First, I'm having trouble getting a controller to pass through to RetroArch. I had some initial trouble with uinput and getting mouse control, but I got that worked out. However, I still am not able to get a controller to pass through. Moonlight client responds to the controller, but once I launch the connection to the stream, controller no longer responds. If there are any logs you might need or if this should be an issue created, let me know. Second, I had grabbed the initial version that was just the retroarch container prior to you changing the account and repo and including those other containers. When using your initial image, Moonlight gave me an option to launch both a desktop, and retroarch (though the desktop was only black). Retroarch was working and I could even scan for games and launch them. However, since changing to running a dedicated xorg container, I only get the desktop option from Moonlight. It connects initially to retroarch, but when exiting the app it stops the retroarch container and dumps to the "desktop" instead of exiting back to the moonlight client itself. Again, if some of this is just things to be worked out or if these need to be issues, i can add whatever logs you need. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Hello @TheJenious0917, thanks for trying out this project!
Controller passthru doesn't work on our side too, I'll open an issue about it, thanks for reminding us about it!
We are in the middle of changing that, the idea is to always share the Desktop as you would do with a remote PC and then leave to users the option to run any GUI app that they wish to, we bundled RetroArch in the
That's intended and it will most likely stay this way in future. You can still override the
Yep that's how it works right now, I know it's counter intuitive, but it's just because we are in the middle of building it all.. restart: alwaysto the options of the RetroArch container so that exiting will just restart it instead of stopping the container, but I haven't tried it personally. I hope this answer your questions, I'm working on adding documentation (you can check it out in the Feel free to join our Discord server, we would love to hear more feedback from people that are using it! |
Beta Was this translation helpful? Give feedback.
-
|
ok, that all makes sense. Just wanted to make sure I wasn't missing anything! I know it's still early in the project, so just bringing things up as I find them. Cheers! |
Beta Was this translation helpful? Give feedback.
-
|
Heads up, latest |
Beta Was this translation helpful? Give feedback.
-
|
Hey, thanks for letting me know. I just was playing around with this and deployed the latest images. Unfortunately, controller still isn't working in my case. This might sound like a dumb question, but does the docker host have to have controller drivers installed or anything like that? Also, my setup is not a straight physical host with docker on it, my host is an ubuntu VM on a proxmox host. Not sure if that changes input drivers or anything since they're virtualized. |
Beta Was this translation helpful? Give feedback.
-
|
That's very close to the setup I'm using too, I have a Debian VM on Proxmox. The host shouldn't need any driver since we are managing everything from inside Docker. |
Beta Was this translation helpful? Give feedback.
Hello @TheJenious0917, thanks for trying out this project!
Controller passthru doesn't work on our side too, I'll open an issue about it, thanks for reminding us about it!
EDIT: opened, checkout progress at #25
We are in the middle of changing that, the idea is to always share the Desktop as you would do with a remote PC and then leave to users the option to run any GUI app that they wish to, we bundled RetroArch in the
docker-composefile but we can easily have other apps like Firefo…