how do i set the keyrah joystick ports on VICE emulator????
if i set keyrah joysick port 1 the joystick gets stuck in the directions, it seems crazy and is unusable!
is there any other setting?
Caution: Non registered users only see threads and messages in the currently selected language, which is determined by their browser. Please create an account and log in to see all content by default. This is a limitation of the forum software.
Please understand that you need to create an account to be able to post, guest posting was disabled as an anti spam measure.
how do i set the keyrah joystick ports on VICE emulator????
if i set keyrah joysick port 1 the joystick gets stuck in the directions, it seems crazy and is unusable!
is there any other setting?
Use the development build: https://github.com/VICE-Team/svn-mirror/releases - that should work out of the Box. (And if you really need the 2nd/3rd Button, or the Paddles, there is a mapping file that will assign these correctly)
The problem here is, that Keyrah provides both an analog and a digital axis for the joystick directions - and depending on what version of VICE you use, it assumes by default that you have a controller with the axis assigned like an XBOX controller, which then maps them in a way that doesn't really work with Keyrah. This was fixed since 3.8.
I don't need the 2nd/3rd button or the paddles, the vice version is 3.8 and I would like to use the original joysticks of the c64/128...
o o o o o
_o o o o
so to speak.....
Actually i was wrong - it works out of the box in 3.8 (just tried in x64sc on Windows)
Please tell exactly what you are doing, starting from a clean config ("reset configuration" in VICE). Do NOT use the "keyrah" keyboard mapping file - this is for Keyrah-v2. In x128 use the keyrah-v3 keyboard mapping file and disable "allow keymap joysticks", else the numpad will not work.
That said, please use the "Gamecontroller" dialog of your OS first and check of the joysticks work with this - so we aren't hunting ghosts
I calibrated the joy from windows, and it actually wasn't calibrated...
now in vice mode it works better, but sometimes it gets stuck up making it unusable on some games.
I'm using ver.3.8
I attach the photos, in the last one you can see the joy panel of the vice that even though I don't touch the joy, vice perceives it in up
Quotesometimes it gets stuck up making it unusable
Unfortunately that is a VICE bug - it should behave better (hopefully) in the upcoming 3.9 (You can try a development build from here: https://github.com/VICE-Team/svn-mirror/releases )
The two extra analog axis you are seeing there (which Windows calls "Rotation") are the paddle values, they should be both 100% (max. value) when no paddle is connected, so your screenshot is still a bit weird - however, they are unrelated to joystick input. Could you try what happens when you disconnect the joystick from Keyrah? If one of them changes, then perhaps the cable or connector of the joystick is a bit broken.
Really interesting that for you Windows shows both ports as "Port 1" - here both are shown as "Port 2". That's a genuine Windows bug
I made another commodore 64 machine with keyrah v2 connected directly to a raspberry pi3 (BMC64) and it works perfectly!
among other things, the kernel and all the files to make it work are those of VICE 3.8.
however the joystick cable is not broken because I tried to change the joystick and it gives me the usual BUG.
I also tried to set the paddle values x and y to 100%, but nothing... and always the same.
QuoteI made another commodore 64 machine with keyrah v2 connected directly to a raspberry pi3 (BMC64) and it works perfectly!
among other things, the kernel and all the files to make it work are those of VICE 3.8.
I'm not sure what you are trying to say... BMC64 is based on a much older VICE (3.3 i believe), and keyrah v2 works fundamentally different to v3. Apple and Oranges
Quotehowever the joystick cable is not broken because I tried to change the joystick and it gives me the usual BUG.
As said, the joystick direction being "stuck" at startup is a VICE bug - it happens with other controllers as well. (And unfortunately it only happens on some systems - so it is very hard to debug and fix).
Did you try the development build?
QuoteI also tried to set the paddle values x and y to 100%, but nothing... and always the same.
You must have misunderstood me (and i wonder where/how you did "set the paddle values").
What i was trying to explain is: if no paddle is connected, those two extra axis should usually be read as "fully right" (or 100%) - just like when no paddle is connected to a C64, they always read as 255. So that is totally expected and is unrelated to the joystick input.