Stéphane Lenclud

It does work in the control panel, it's showing two sliders, both are working nicely. 

And I can reproduce the issue in HID Demo. I'll try to debug that later today.

The issue it seems is indeed due to `HidP_GetUsageValue`. It looks like they even describe the problem in the [docs remarks section](https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/hidpi/nf-hidpi-hidp_getusagevalue#remarks). Basically to support that we should use [`HidP_GetUsageValueArray`](https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/hidpi/nf-hidpi-hidp_getusagevaluearray)...

We should switch to [Microsoft.Windows.CsWin32](#17) to gain access to [`HidP_GetUsageValueArray`](https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/hidpi/nf-hidpi-hidp_getusagevaluearray)

Except that our ReportCount is not above one so that array function might not be what we need here. I'm still missing a piece of the puzzle. I'm guessing I...

As feared using `HidP_GetUsageValueArray` does not work it returns `HIDP_STATUS_NOT_VALUE_ARRAY`. More investigation is needed to work that one out. I'll put on the ice for now however.

[UCR](https://github.com/Snoothy/UCR) can pick up both Slider axes properly through [SharpDX](https://github.com/sharpdx/SharpDX) DirectInput. However this is done through DirectInput which is a higher level API so it won't help us here.

@sonik-br Could you build and run the latest HID Demo? I'm just curious to see what kind of friendly name your PS3 controller is now reporting. Hopefully I did not...

I could try to use [API Monitor](http://www.rohitab.com/apimonitor) see how Joy.cpl gets the axis value. Though I reckon it's using the DirectInput API rather than the HID API.

In the HID Demo, is it still displaying `VID_054C` as the name of the device?