I suspect that this issue has to do with the Chromium environment version that OBS is using and it may need an update. I'm not sure if log files will help as it doesn't seem to identify how the gamepad is being enumerated.
I noticed this when opening a browser in OBS to Gamepad Tester (https://hardwaretester.com/gamepad). When pressing L2 and R2 on the DualSense Edge, it reports as if B6 and B7 are buttons, while the analog action is read as axis 3 and 4. On Chrome, it's correctly detected as B6 and B7 analog respectively.
In comparison, the regular DualSense controller is reported identically on both OBS and Chrome.
Chrome report for DualSense Edge (same as DualSense):
OBS report for DualSense Edge:
This also has an impact on mini-padder (https://dinir.github.io/mini-padder/) as it's looking for B6/B7 analog for the analog animation.
I noticed this when opening a browser in OBS to Gamepad Tester (https://hardwaretester.com/gamepad). When pressing L2 and R2 on the DualSense Edge, it reports as if B6 and B7 are buttons, while the analog action is read as axis 3 and 4. On Chrome, it's correctly detected as B6 and B7 analog respectively.
In comparison, the regular DualSense controller is reported identically on both OBS and Chrome.
Chrome report for DualSense Edge (same as DualSense):
OBS report for DualSense Edge:
This also has an impact on mini-padder (https://dinir.github.io/mini-padder/) as it's looking for B6/B7 analog for the analog animation.