MISTer (Main Core)

https://github.com/MiSTer-devel/Main_MiSTer/wiki

Moderators: Mug UK, Zorro 2, spiny, Greenious, Sorgelig, Moderator Team

Locked
Sorgelig
Ultimate Atarian
Ultimate Atarian
Posts: 6348
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: MISTer (Main Core)

Post by Sorgelig »

terminator2k2 wrote:ive gone into each cores menu and re-mapped the directional buttons to my dpad, which works ok but sometimes if im pressing left then press right , it doesnt respond, also happens right then left....
In which core for example?
May be game you're playing doesn't expect quick change to opposite direction? Analog stick has longer time between opposite directions.
terminator2k2
Atariator
Atariator
Posts: 27
Joined: Sat Dec 22, 2018 10:23 pm

Re: MISTer (Main Core)

Post by terminator2k2 »

in all cores ive tried, 1942, 1943 , snes playing smw , genesis playing sonic

its as if it stops reading d pad, if i repress d-pad direction again it works again
User avatar
kitrinx
Captain Atari
Captain Atari
Posts: 192
Joined: Wed Sep 26, 2018 6:03 am

Re: MISTer (Main Core)

Post by kitrinx »

On some controllers, like 8bitdo M30 by default, DPAD counts as an analog stick. I noticed trying to map such a controller that LEFT is not counted properly in remapping.
Sorgelig
Ultimate Atarian
Ultimate Atarian
Posts: 6348
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: MISTer (Main Core)

Post by Sorgelig »

kitrinx wrote:On some controllers, like 8bitdo M30 by default, DPAD counts as an analog stick. I noticed trying to map such a controller that LEFT is not counted properly in remapping.
Common! I've told above several times for M30: press RIGHT and DOWN for Stick 1 map.
Sorgelig
Ultimate Atarian
Ultimate Atarian
Posts: 6348
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: MISTer (Main Core)

Post by Sorgelig »

terminator2k2 wrote:in all cores ive tried, 1942, 1943 , snes playing smw , genesis playing sonic

its as if it stops reading d pad, if i repress d-pad direction again it works again
I see some events not converted to joystick bits. I will investigate it.
fille1976
Retro freak
Retro freak
Posts: 16
Joined: Sat Nov 17, 2018 4:33 pm

Re: MISTer (Main Core)

Post by fille1976 »

Here also,snes-genesis ect...,8bitdo snes and genesis controller doesn't react anymore.
If i want to assign it back,also doesn't work.
I reverted back to earlyer version and controller is working.
So something is wrong.
Sorgelig
Ultimate Atarian
Ultimate Atarian
Posts: 6348
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: MISTer (Main Core)

Post by Sorgelig »

terminator2k2 wrote:its as if it stops reading d pad, if i repress d-pad direction again it works again
new release fixes it.
terminator2k2
Atariator
Atariator
Posts: 27
Joined: Sat Dec 22, 2018 10:23 pm

Re: MISTer (Main Core)

Post by terminator2k2 »

nice one , ill test it when i get back

can confirm it fixed my issue
fille1976
Retro freak
Retro freak
Posts: 16
Joined: Sat Nov 17, 2018 4:33 pm

Re: MISTer (Main Core)

Post by fille1976 »

Here still not working,after updated the mister main core i rebooted.
In genesis core i go to define genesis buttons.
Can't put left dpad in,strange for termeinator2k2 it works,here not.
Threepwood
Captain Atari
Captain Atari
Posts: 154
Joined: Thu Jan 10, 2019 10:06 am

USB Gamepad axis mapping issue

Post by Threepwood »

After today's updates via script I ran into the issue that I can no longer get my 8bitdo N30 Bluetooth with 8bitdo USB Adapter to map D-Pad Up and D-Pad Left. The D-Pad registers as X/Y Axis according to to Window 10 game controller options (I also confirmed the gamepad to be working there).

I tried mapping it in the menu core and according to the manual here https://github.com/MiSTer-devel/Main_Mi ... ut-devices the d-pad should be registered as axis for stick 1 (right and down). MiSTer definitely registers the d-pad presses as it shows the controller ID no matter what direction I press first, but the axis mapping won't proceed to the next step after pressing RIGHT on the first step of mapping (or any other direction).

No matter what I do I can't get Up and Left to map, everything else works fine.

Does anybody have a hint for me or an idea how to get it working?
2x MiSTer FPGA: [Official Stormtrooper Case, USB Hub 2.1 with Bridge Board, 128MB SDRAM, ADC, RTC 1.3, I/O v5.5] + [3D printed MiSTer XS Case v2, 128MB SDRAM, I/O v5.6 XL]
Sorgelig
Ultimate Atarian
Ultimate Atarian
Posts: 6348
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: USB Gamepad axis mapping issue

Post by Sorgelig »

Threepwood wrote: I tried mapping it in the menu core and according to the manual here https://github.com/MiSTer-devel/Main_Mi ... ut-devices the d-pad should be registered as axis for stick 1 (right and down). MiSTer definitely registers the d-pad presses as it shows the controller ID no matter what direction I press first, but the axis mapping won't proceed to the next step after pressing RIGHT on the first step of mapping (or any other direction).
press the space to skip Stick 1 and 2 map.
Sorgelig
Ultimate Atarian
Ultimate Atarian
Posts: 6348
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: MISTer (Main Core)

Post by Sorgelig »

fille1976 wrote:Here still not working,after updated the mister main core i rebooted.
In genesis core i go to define genesis buttons.
Can't put left dpad in,strange for termeinator2k2 it works,here not.
Because you didn't read my note:
Note: You need re-assign system-wide buttons/axes in Menu core for proper work.
fille1976
Retro freak
Retro freak
Posts: 16
Joined: Sat Nov 17, 2018 4:33 pm

Re: MISTer (Main Core)

Post by fille1976 »

I just updated the main mister core again and now its working.
And i did nothing,just reboot.
Threepwood
Captain Atari
Captain Atari
Posts: 154
Joined: Thu Jan 10, 2019 10:06 am

Re: USB Gamepad axis mapping issue

Post by Threepwood »

Sorgelig wrote:press the space to skip Stick 1 and 2 map.
I Already did so. The mapping dialog does not react to Up or Left on any of the input queries. My 8bitdo SN30 works and the axis-queries continue to the next step with this one while they do not do so with the N30.

It's weird as I cannot find a difference between the SN30 and the N30 and I even looked at button press plots with a Titan 2. Both gamepads use STICK_2_X and STICK_2_Y for the D-Pad and the N30 worked fine before. I also made sure I have the latest version for the main core.

I attached the two plots of D-Pad presses, because I might as well. I wiggled the D-Pads around on them.
You do not have the required permissions to view the files attached to this post.
2x MiSTer FPGA: [Official Stormtrooper Case, USB Hub 2.1 with Bridge Board, 128MB SDRAM, ADC, RTC 1.3, I/O v5.5] + [3D printed MiSTer XS Case v2, 128MB SDRAM, I/O v5.6 XL]
Sorgelig
Ultimate Atarian
Ultimate Atarian
Posts: 6348
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: USB Gamepad axis mapping issue

Post by Sorgelig »

Threepwood wrote: I attached the two plots of D-Pad presses, because I might as well. I wiggled the D-Pads around on them.
these pictures show zero information.
You need to show USB console log of key presses.

Basically there are 2 possible ways for dpad:
1) dpad produces analog events: in this case you simply press RIGHT and DOWN for Stick 1 and skip Stick 2. If pressing RIGHT/DOWN advances the Stick 1 map, then it's really this kind of dpad. And if you won't press RIGHT/DOWN for Stick 1, then you won't be able to define UP and LEFT directions.
2) dpad produces original dpad events (or even just simple button events): in this case Stick 1 map won't advance by dpad presses. So simply skip it by SPACE key. You will be able to assign the directions as usual.
Threepwood
Captain Atari
Captain Atari
Posts: 154
Joined: Thu Jan 10, 2019 10:06 am

Re: USB Gamepad axis mapping issue

Post by Threepwood »

Sorgelig wrote:You need to show USB console log of key presses.

Basically there are 2 possible ways for dpad:
1) dpad produces analog events: in this case you simply press RIGHT and DOWN for Stick 1 and skip Stick 2. If pressing RIGHT/DOWN advances the Stick 1 map, then it's really this kind of dpad. And if you won't press RIGHT/DOWN for Stick 1, then you won't be able to define UP and LEFT directions.
2) dpad produces original dpad events (or even just simple button events): in this case Stick 1 map won't advance by dpad presses. So simply skip it by SPACE key. You will be able to assign the directions as usual.
I tried the N30 on all of the possible ways to map input and I cannot get it to work. Up and Left do not register. I tried finding how to capture a USB console log and hope these screenshots provide you with more information, because I only found a tool called USBlyzer. The Raw Data of key presses looks way different between the N30 and SN30, as you suspected.
You do not have the required permissions to view the files attached to this post.
2x MiSTer FPGA: [Official Stormtrooper Case, USB Hub 2.1 with Bridge Board, 128MB SDRAM, ADC, RTC 1.3, I/O v5.5] + [3D printed MiSTer XS Case v2, 128MB SDRAM, I/O v5.6 XL]
Sorgelig
Ultimate Atarian
Ultimate Atarian
Posts: 6348
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: MISTer (Main Core)

Post by Sorgelig »

Threepwood wrote:I tried finding how to capture a USB console log and hope these screenshots provide you with more information
https://github.com/MiSTer-devel/Main_Mi ... connection
Sorgelig
Ultimate Atarian
Ultimate Atarian
Posts: 6348
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: MISTer (Main Core)

Post by Sorgelig »

I will add dpad test phase. It should solve the analog dpad setting.
vanfanel
Obsessive compulsive Atari behavior
Obsessive compulsive Atari behavior
Posts: 129
Joined: Tue Oct 09, 2018 10:19 pm
Location: Salamanca, España

Re: MISTer (Main Core)

Post by vanfanel »

I use a PSX pad with USB adapter and I am also seeing the same problems as with the SN30 with latest MiSTer: no way to map all directions on the digital pad (it's a PSX pad so it only has a digital pad).
Previous versions worked perfectly well.
Milongero
Atari User
Atari User
Posts: 41
Joined: Sun Nov 25, 2018 2:24 pm
Location: Germany

Re: MISTer (Main Core)

Post by Milongero »

Hello,

I have a game pad from Retroflag that communicates via d-input. It could not be set up with the new main core. After I switched it to X-Input it worked

Lutz
Sorgelig
Ultimate Atarian
Ultimate Atarian
Posts: 6348
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: MISTer (Main Core)

Post by Sorgelig »

It's as simple as 1 cent: press the RIGHT on dpad when it asks for Stick 1 Tilt RIGHT, and press the dpad DOWN when it asks for Stick 1 Tilt DOWN.
Threepwood
Captain Atari
Captain Atari
Posts: 154
Joined: Thu Jan 10, 2019 10:06 am

Re: MISTer (Main Core)

Post by Threepwood »

Sorgelig wrote:
Threepwood wrote:I tried finding how to capture a USB console log and hope these screenshots provide you with more information
https://github.com/MiSTer-devel/Main_Mi ... connection
Here the log for the N30 connected via bluetooth to a USB adapter. I deleted all map files prior to this and plugged the receiver directly into the OTG port not using a hub:

Plugged in 8bitdo USB Adapter (PS Classic Edition, Firmware v1.22):
The file js0 was created.
Close all devices.
Open up to 10 input devices.
The file event0 was created.
Close all devices.
Open up to 10 input devices.
opened /dev/input/event0 (054c:0cda)
opened /dev/input/event1 (054c:0cda)
opened /dev/input/event2 (054c:0cda)
The file event1 was created.
The file event2 was created.
The directory by-id was created.
The directory by-path was created.
Close all devices.
Open up to 10 input devices.
opened /dev/input/event0 (054c:0cda)
opened /dev/input/event1 (054c:0cda)
opened /dev/input/event2 (054c:0cda)

Turned on 8bitdo N30 Bluetooth (Firmware v6.10):
Input event: type=EV_ABS, Axis=0, Offset:=1, jnum=0, ID:054c:0cda. ABS_INFO: min = 0 max = 2
FileLoad(open) File:/media/fat/config/input_054c_0cda.map, error: -1.
FileLoad(open) File:/media/fat/config/input_054c_0cda.map, error: -1.
Input event: type=EV_ABS, Axis=1, Offset:=1, jnum=0, ID:054c:0cda. ABS_INFO: min = 0 max = 2

D-Pad Up:
Input event: type=EV_ABS, Axis=1, Offset:=0, jnum=0, ID:054c:0cda. ABS_INFO: min = 0 max = 2
Input event: type=EV_ABS, Axis=1, Offset:=1, jnum=0, ID:054c:0cda. ABS_INFO: min = 0 max = 2

D-Pad Down:
Input event: type=EV_ABS, Axis=1, Offset:=2, jnum=0, ID:054c:0cda. ABS_INFO: min = 0 max = 2
Input event: type=EV_ABS, Axis=1, Offset:=1, jnum=1, ID:054c:0cda. ABS_INFO: min = 0 max = 2

D-Pad Left:
Input event: type=EV_ABS, Axis=0, Offset:=0, jnum=1, ID:054c:0cda. ABS_INFO: min = 0 max = 2
Input event: type=EV_ABS, Axis=0, Offset:=1, jnum=1, ID:054c:0cda. ABS_INFO: min = 0 max = 2

D-Pad Right:
Input event: type=EV_ABS, Axis=0, Offset:=2, jnum=1, ID:054c:0cda. ABS_INFO: min = 0 max = 2
Input event: type=EV_ABS, Axis=0, Offset:=1, jnum=1, ID:054c:0cda. ABS_INFO: min = 0 max = 2


If you need more logs I have the following gamepads here that I can test for you:
8bitdo: SFC30, NES30 (gamepad), M30 Bluetooth, SN30 Pro, SF30 Pro
Others: Nintendo Switch Pro Controller, XBox One Gamepad, Hori: Pokken Pro Pad, Sony PS3 Dualshock 3, Qanba Q4 RAF Arcade Stick, Speedlink Competition Pro Extra USB 20 years Anniversary Edition
2x MiSTer FPGA: [Official Stormtrooper Case, USB Hub 2.1 with Bridge Board, 128MB SDRAM, ADC, RTC 1.3, I/O v5.5] + [3D printed MiSTer XS Case v2, 128MB SDRAM, I/O v5.6 XL]
Sorgelig
Ultimate Atarian
Ultimate Atarian
Posts: 6348
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: MISTer (Main Core)

Post by Sorgelig »

Threepwood wrote:Here the log for the N30 connected via bluetooth to a USB adapter. I deleted all map files prior to this and plugged the receiver directly into the OTG port not using a hub:
OMG! More and more awkwardier gamepads detected...
i need to think about it.
Thanks for info!
Threepwood
Captain Atari
Captain Atari
Posts: 154
Joined: Thu Jan 10, 2019 10:06 am

Re: MISTer (Main Core)

Post by Threepwood »

Sorgelig wrote:
Threepwood wrote:Here the log for the N30 connected via bluetooth to a USB adapter. I deleted all map files prior to this and plugged the receiver directly into the OTG port not using a hub:
OMG! More and more awkwardier gamepads detected...
i need to think about it.
Thanks for info!
You are very welcome. Maybe min = 0 is Nintendo Switch related, as the SFC30 that works in X-Input mode (min = -32768 max = 32767 fuzz = 16) has a range of min = 0 max = 255 in Switch mode.
2x MiSTer FPGA: [Official Stormtrooper Case, USB Hub 2.1 with Bridge Board, 128MB SDRAM, ADC, RTC 1.3, I/O v5.5] + [3D printed MiSTer XS Case v2, 128MB SDRAM, I/O v5.6 XL]
Sorgelig
Ultimate Atarian
Ultimate Atarian
Posts: 6348
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: MISTer (Main Core)

Post by Sorgelig »

Test version:
<removed> - i found the bug. Will re-upload soon.
Locked

Return to “MiSTer”