Chuck Walbourn
Chuck Walbourn
@EpicChrisWaters Did this get reported to the VS site yet?
The assumption in that code is that the ``pGuidProductFromDirectInput->Data1`` will have the Vendor ID for Microsoft which is "0x045E" in the lower DWORD. It appears that you are getting "0x005E"...
Does it work as an XINPUT device when attached via Bluetooth?
Thanks for the additional details. I've reproduced this bug on Windows 11. I'm trying to track down the owner of the driver...
For the "Xbox One S" controller, what is the full ``bstrVal`` reported from the device on Bluetooth (the string that contains ``IG_``)? For example, the Xbox Series X controller when...
There is a fix for this driver in the works.
Windows.Gaming.Input on Windows 10/11 supports more than 4 devices. Have you tried that?
Please be more specific about exactly which sample of the 40+ samples in the repo are showing an issue.
I assume this is a report of a problem with `SubD11` that was also commented on the [MSDN Code Gallery](https://code.msdn.microsoft.com/Direct3D-Tessellation-70afba2c/view/Discussions).
The problem is in the shader. It works if built with #43 (DXSDK) or #46 (VS 2012), but not with #47 (Windows 8.1 or Windows 10).