Moderators: Mug UK, Zorro 2, spiny, Greenious, Sorgelig, Moderator Team
RabidWookie wrote:The MC Cthulhu stick, on the other hand, seemed to double jump around on the menu screens.
Lightwave wrote:RabidWookie wrote:The MC Cthulhu stick, on the other hand, seemed to double jump around on the menu screens.
Hmm, I was planning on installing the MC Cthulhu into a Mad Catz TE-S...
Anyone using a stick with Brook Retro Board?
normal19 wrote:Brook Ultimate Fighting Board works with MiSTer, best to use Xbox 360 or PS3 modes because some of the buttons on default mode don't get recognized
alex1 wrote:I have tested a Logitech Precision pad (it has only the D-Pad and buttons) and it's not working correctly. During the calibration in MiSTer it seems that is generating analog stick events (it's asking for pressing DOWN). The Joystick ID is: 046d:c21a.
The serial console messages for axis are:
Input event: type=EV_ABS, Axis=0, Offset=1, jnum=1, ID:046d:c21a:00, abs_min = 0, abs_max = 255
Input event: type=EV_ABS, Axis=0, Offset=128, jnum=1, ID:046d:c21a:00, abs_min = 0, abs_max = 255
Input event: type=EV_ABS, Axis=0, Offset=255, jnum=1, ID:046d:c21a:00, abs_min = 0, abs_max = 255
Input event: type=EV_ABS, Axis=1, Offset=1, jnum=1, ID:046d:c21a:00, abs_min = 0, abs_max = 255
Input event: type=EV_ABS, Axis=1, Offset=128, jnum=1, ID:046d:c21a:00, abs_min = 0, abs_max = 255
Input event: type=EV_ABS, Axis=1, Offset=255, jnum=1, ID:046d:c21a:00, abs_min = 0, abs_max = 255
The pad in the menu can move UP, but not DOWN. A similar behavior is experienced in games. The buttons seems to work correctly. I tested it using the last core (20191117), but has the same problem also with previous cores. Of course the pad was tested in Windows and is working correctly.
Any suggestion? Many thanks.
Sorgelig wrote:alex1 wrote:I have tested a Logitech Precision pad (it has only the D-Pad and buttons) and it's not working correctly. During the calibration in MiSTer it seems that is generating analog stick events (it's asking for pressing DOWN). The Joystick ID is: 046d:c21a.
The serial console messages for axis are:
Input event: type=EV_ABS, Axis=0, Offset=1, jnum=1, ID:046d:c21a:00, abs_min = 0, abs_max = 255
Input event: type=EV_ABS, Axis=0, Offset=128, jnum=1, ID:046d:c21a:00, abs_min = 0, abs_max = 255
Input event: type=EV_ABS, Axis=0, Offset=255, jnum=1, ID:046d:c21a:00, abs_min = 0, abs_max = 255
Input event: type=EV_ABS, Axis=1, Offset=1, jnum=1, ID:046d:c21a:00, abs_min = 0, abs_max = 255
Input event: type=EV_ABS, Axis=1, Offset=128, jnum=1, ID:046d:c21a:00, abs_min = 0, abs_max = 255
Input event: type=EV_ABS, Axis=1, Offset=255, jnum=1, ID:046d:c21a:00, abs_min = 0, abs_max = 255
The pad in the menu can move UP, but not DOWN. A similar behavior is experienced in games. The buttons seems to work correctly. I tested it using the last core (20191117), but has the same problem also with previous cores. Of course the pad was tested in Windows and is working correctly.
Any suggestion? Many thanks.
I don't see problem from log. Many gamepads generate analog events from dpad. That's why MiSTer asks to press the right on DPAD at first to see if it generates analog event.
255 is for right and down?
alex1 wrote:DOWN:
Input event: type=EV_ABS, Axis=1, Offset=128, jnum=1, ID:046d:c21a:00, abs_min = 0, abs_max = 255
NEUTRAL:
Input event: type=EV_ABS, Axis=1, Offset=128, jnum=1, ID:046d:c21a:00, abs_min = 0, abs_max = 255
alex1 wrote:It seems that only if you move down-left it gets the correct down movement (255):
Input event: type=EV_ABS, Axis=1, Offset=255, jnum=1, ID:046d:c21a:00, abs_min = 0, abs_max = 255
Sorgelig wrote:alex1 wrote:DOWN:
Input event: type=EV_ABS, Axis=1, Offset=128, jnum=1, ID:046d:c21a:00, abs_min = 0, abs_max = 255
NEUTRAL:
Input event: type=EV_ABS, Axis=1, Offset=128, jnum=1, ID:046d:c21a:00, abs_min = 0, abs_max = 255
so DOWN and NEUTRAL are the same?
Sorgelig wrote:alex1 wrote:It seems that only if you move down-left it gets the correct down movement (255):
Input event: type=EV_ABS, Axis=1, Offset=255, jnum=1, ID:046d:c21a:00, abs_min = 0, abs_max = 255
Then it's a problem with gamepad or it's driver.
warham wrote:I also updated the 8bitdo orange brick firmware almost the same day so maybe its that. Once i get them to connect they are fine but the initial connection is a mess. The controllers say they connect but i get no movement out of mister. Ill see if i can downgrade the firmware and see if that fixes it.
ewok wrote:warham wrote:I also updated the 8bitdo orange brick firmware almost the same day so maybe its that. Once i get them to connect they are fine but the initial connection is a mess. The controllers say they connect but i get no movement out of mister. Ill see if i can downgrade the firmware and see if that fixes it.
Same here, definitely different then in the past. Switching to another orange brick and another controller does the trick.
Frobozzz wrote:Sorgelig wrote:8bitdo controllers may work in different modes. Change the mode to DInput or XInput - then it should work fine.
Thank you! I changed to Xinput (Press and hold POWER + X for 1 second to power on the controller, LEDs will blink twice per cycle) and everything seems to be working fine now.
dragonet80 wrote:@Sorgelig: As others commented before, I tried with core 20190408 and the gamepad works nice witout any change in mode of operation. Is there any option to recover that way of working in the new core?
Retr80s wrote:Hi! Just wanted to report that the Retro-Bit Official SEGA Saturn 2.4Ghz Wireless Arcade Pad has some problems on the Mister FPGA.
After a while the direction pad stops working and you need to plug and unplug the USB wifi receiver.
Users browsing this forum: GallopGhost and 10 guests