New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dosbox_pure_libretro.so keyboard mapping #363
Comments
not sure if this should be seperate issues or not but here goes (it's in the same vain as the main toppic) dosbox_pure_libretro does some fancy automapping which works quite ok if you use a controller. I tried with both an xbox style controller (logitech rumblepad 2) on a pc and an xbox controller on an xbox one x, this does seem to map quite ok in most cases (dos platformers work mostly ok) however there does not seem to be a way to switch to fullscreen mode in cloudretro with an xbox style controller (other then plugging in a keyboard to press the "F" key). I also noticed that the right stick is not mapped to anything nor are the push functions of both sticks. (usually L3 en R3) maybe these could be mapped to the function for the F key on controllers? I know that dosbox_pure_libretro is able to display an onscreen keyboard when playing games. cfr: https://github.com/schellingb/dosbox-pure#on-screen-keyboard but there is no way to call this onscreen keyboard with the current cloudretro controller mapping scheme. (if i'm not mistaken this is mapped to L3 by default in dosbox_pure_libretro) This onscreen keyboard is a nice way of allowing for additional keypresses without actually implementing all the seperate keypresess natively through the entire cloud-retro stack. could the L3 functionality be enabled? |
joystick.js adjusted mainly for dosbox_pure L3 mapping (virtual keyboard) and allowing dosbox_pure to do more efficient magic mapping.
|
maybe best to do a controller mapping scheme based on what core is loaded (if that is possible)? |
-testing on windows client with rumble pad 2 works great. |
There is no option for the client (browser) to know what core is running at the moment. |
|
Doesn't matter, it's not implemented on the client. We need to expose some IDs for cores and games and a UI to be able to tweak it which is the hardest part. Current cloud-retro options UI is far from perfect and, I think, won't work with controllers also (you can try (;).
Strange. Do both buttons (B and FullScreen) toggle it (or does B only exits)? |
|
is there a way to just run the app in fullscreen by default, and disabling fullscreen/windowed togling? appart from the cool handheld aesthetic, I don't see a good reason (at least for my intended purposes) to have it in a window anyway. |
Not possible, but it'll be not that hard to add. |
e.g. different configurable defaults depending on client device string (ios, windows, android, ...) |
my end goal is to get dosbox games running in the same way that the other cores work.
I successfully installed dosbox_pure_libretro.so as a new core and added a game to the games folder
adjusted config.yaml, started up the server and worker and got a game running.
however it seems the keyboard does not map to what the dosbox core expects.
imho I would expect that web/js/input/input.js and web/js/input/keyboard.js have a role to play in the client side of the controller support.
no clue about the server side though.
The text was updated successfully, but these errors were encountered: