Duplicate mappings about sdl_gamecontrollerdb HOT 5 CLOSED

FWIW... here's the list of duplicates (Windows)...

03000000341a00003608000000000000
03000000ffff00000000000000000000
030000006d04000016c2000000000000
030000006d04000019c2000000000000
03000000888800000803000000000000
030000004c0500006802000000000000
03000000250900000500000000000000
030000004c050000c405000000000000
030000004c050000cc09000000000000
030000004c050000a00b000000000000
030000006d04000018c2000000000000
03000000362800000100000000000000
03000000102800000900000000000000
03000000ff1100003133000000000000
03000000790000000600000000000000

from sdl_gamecontrollerdb.

It was me, who tested and added JPD-DualForce.
As you can seem both devices with the same GUID has different mappings.

from sdl_gamecontrollerdb.

I tried out my new "Data Frog" snes-style controller, and the GUID from SDL2 Gamepad Tool already exists, but the mapping is not correct, for this controller! Is there any way to handle these collisions other than removing one of the controllers? My mapping looks like this:

100801e5000000000000504944564944,DATA FROG snes style,a:b2,b:b1,x:b3,y:b0,back:b8,start:b9,leftshoulder:b4,rightshoulder:b6,leftx:a0,lefty:a1,platform:Windows,

from sdl_gamecontrollerdb.

Duplicate mappings have been removed. Furthermore, by converting to the unified GUIDs, old vs. new GUID duplicates have also been removed. Checks are also automatically run on new PRs to verify duplicates :)

from sdl_gamecontrollerdb.

@sandos Please open a specific issue for your problem.

from sdl_gamecontrollerdb.