SSF blank input redefine

[draen]

Hello.
I'm opening this thread out of desperation. I have the latest avaiable build  of  the SSF emulator (SSF_012_beta_R4) and it seems to work fine, except for one thing: the controls.
Basically, when I click on the "Redefine" option under the "Input" tab, SSF opens up the small input configuration window, but it's completely blank, without text. The only way to close the tiny window is through Alt+f4.

If I try to open it again, I get this message: 

"ResumeThread() error.
File : ./MainWindows.cpp
Line : 2837
Function : _ControllerDialogProc"

And then blank window again.

I'm using a Dualshock 4 controller which works perfectly with any other emulator.

I tried older versions and I discovered that some of them allows me to bind the keys. However, they're way too obsolete, and they lack some basic screen/sound configuration options.

I downloaded Xinput in order to "trick" SSF into believing I was using a X360 controller (which I heard worked better) but it didn't work.
I tried DS4Windows to bind the controller keys to the default SSF keyboard controls, but the emulator doesn't recognize the gamepad inputs despite rebinding them. 
Drivers are up to date, everything works fine.

I tried some troubleshooting via google, got me into a bunch of old-ass threads, just to find out that very few people had this problem, and some of them fixed it with one of the methods listed above.

So, yeah: I ran out of options. I don't know if this forum is still pretty active, but i do know that Saturn Emulation is pretty much a dead topic. However, if someone could lend me a hand, I'll be extremely grateful. Thanks.

[zyrobs]

If I recall right, SSF had a bug where a trigger did not work if it used a certain value as a base, I think it was non centered Z-Axis/Rotation (0-255 range, 0 when not pressed). The XInput drivers at one point mapped to that exact thing and therefore did not work with SSF, but Microsoft reseted the triggers to use 0-255 range with 128 as the base value instead (but with the triggers sharing the same axis).

I don't know what DirectInput values a Dual Shock 4 maps to, but if you use a Z-Axis or Z-Rotation, that does NOT use the center value when not pressed, it may cause a bug in the input mapping of SSF. Note that it has been a long time ago since I found this bug, so I'm not 100% sure on the exact details, but I think it is the main reason why I have my controllers custom DirectInput mapping uses 128 as a base for the triggers (out of 0-255, basically halving its range).

Either way, you should be using the newer preview versions, the author links to them on his twitter.
twitter.com/FessX

[zyrobs]

note, I just tested it, the latest preview version works with XInput pads fine. However since the default DirectInput mapping for such pads puts the two shoulder triggers as positive and negative on the same axis, you can't press the two triggers simultaneously (they cancel each other out).

[draen]

Oh god.
FINALLY, IT WORKS!

I didn't know there were newer versions
A thousand thanks, my friend. I literally spent the whole day trying to solve this issue