Greetings,
we recently had to move away from Legacy JoyPosEx to using DirectInput when we upgraded to Win8. The game controller interface is working well except the first run after a reboot. The call to DirectInput8Create leads to a heap corruption exception in ntdll. Interestingly, MS dxdiag does exactly the same (in fact, its next run asks if DirectInput check should be ignored due to the last run's exception). Our app is Win32.
We had noted that the legacy JoyPosEx was redirected to DirectInput, and there we were having runtime exceptions in dinput.dll, which was another reason we went to using the newer MS APIs.
It is a very vexing problem that sorely needs a solution in a timely manner.
Cheers & much oblidged.
we recently had to move away from Legacy JoyPosEx to using DirectInput when we upgraded to Win8. The game controller interface is working well except the first run after a reboot. The call to DirectInput8Create leads to a heap corruption exception in ntdll. Interestingly, MS dxdiag does exactly the same (in fact, its next run asks if DirectInput check should be ignored due to the last run's exception). Our app is Win32.
We had noted that the legacy JoyPosEx was redirected to DirectInput, and there we were having runtime exceptions in dinput.dll, which was another reason we went to using the newer MS APIs.
It is a very vexing problem that sorely needs a solution in a timely manner.
Cheers & much oblidged.