Sign in to follow this  
Kest

Direct Input: user breakpoint?

Recommended Posts

I've been using Direct Input for a while, but this problem has popped up in between program modifications, without me noticing when it did so. Whatever it is that is happening is only visible during debug mode while running from the MSVC++ environment. Nothing at all is apparent while running in debug mode outside of the environment. I've tried unplugging all devices except the keyboard and mouse, and the problem still persists. It looks to me like a user-breakpoint is halting the program. It breaks when DirectInput8Create() is called - the program never exits that function. But it breaks on a location in my own program code, not Direct Input code. The location it breaks on in my code randomly changes each time I compile, so I doubt it's even related to the problem. It looks like a random compiler hiccup. Here is the output window data:
DINPUT8: DIHid_BuildHidList(0)
DINPUT8: DIHid_CheckList(00000000)
DINPUT8: DIHid_CheckList(00000000) -> 
DINPUT8: DIHid_BuildHidListEntry(001c5918, 0012F404)
DINPUT8: DIHid_GetDevicePath(001c5918, 0012F404)
DINPUT8: DIHid_GetDevicePath(001c5918, 0012F404) -> 00000001 OK 
DINPUT8: DIHid_GetDevInfo(001c5918, 0012F404, 0012F358)
DINPUT8: DIHid_GetDevicePath(001c5918, 0012F404)
DINPUT8: DIHid_GetDevicePath(001c5918, 0012F404) -> 00000001 OK 
DINPUT8: DIHid_CreateDeviceInstanceKeys(0012F358)
DINPUT8: DIHid_CreateDeviceInstanceKeys: RegQueryValueEx failed (2) to get state for instance 6&12EEA817&0&0000
DINPUT8: DIHid_CreateDeviceInstanceKeys(0012F358) -> 00000000
DINPUT8: DIHid_GetDevInfo: CreateFile(
\\?\hid#vid_0461&pid_4d15#6&12eea817&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}) failed? le=5
DINPUT8: DIHid_GetDevInfo(001c5918, 0012F404, 0012F358) -> 00000000 le=[5]
DINPUT8: DIHid_BuildHidListEntry: DIHid_GetDevInfo failed, ignoring device
DINPUT8: DIHid_BuildHidListEntry(001c5918, 0012F404) -> 00000000 le=[5]
DINPUT8: DIHid_BuildHidListEntry failed?
DINPUT8: DIHid_BuildHidListEntry(001c5918, 0012F404)
DINPUT8: DIHid_GetDevicePath(001c5918, 0012F404)
DINPUT8: DIHid_GetDevicePath(001c5918, 0012F404) -> 00000001 OK 
DINPUT8: DIHid_GetDevInfo(001c5918, 0012F404, 0012F358)
DINPUT8: DIHid_GetDevicePath(001c5918, 0012F404)
DINPUT8: DIHid_GetDevicePath(001c5918, 0012F404) -> 00000001 OK 
DINPUT8: DIHid_CreateDeviceInstanceKeys(0012F358)
DINPUT8: DIHid_CreateDeviceInstanceKeys: ID VID_0925&PID_8866&COL01\6&2194989F&0&0000, len 24 not VID PID
DINPUT8: DIHid_CreateDeviceInstanceKeys(0012F358) -> 00000000
DINPUT8: DIHid_GetDevInfo: Have \\?\hid#vid_0925&pid_8866&col01#6&2194989f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
DINPUT8: DIHid_GetDevInfo: Device changed from VID_0000&PID_0000 to VID_0925&PID_8866
DINPUT8: DIHid_CreateDeviceInstanceKeys(0012F358)
HEAP[Kestarda.exe]: Heap block at 001D32A0 modified at 001D32A9 past requested size of 1
Unhandled exception at 0x7c901230 in Kestarda.exe: User breakpoint.
The thread 'Win32 Thread' (0x6f0) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x4d8) has exited with code 0 (0x0).
The program '[2024] Kestarda.exe: Native' has exited with code 0 (0x0).

Does anyone have any clue as to what might be happening?

Share this post


Link to post
Share on other sites
After yanking everything off of my computer, I found that the problem was indeed caused by a device. It's a device that converts PS2 controllers to USB for the PC.

It's never caused any problems before, so I'm guessing some driver or software has slapped something out of place. That, or perhaps I spilled coffee on it. It still works fine, so I can't make sense of the problem Direct Input is reporting. If anyone can shed any light on that, it would be great. I can't run my game from MSDEV with controllers attached until I find a way around it. Not even with Direct Input in release mode.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this