Open ghost opened 9 years ago
Possible xam input problems?
I can step through the calls, I'm going to guess it's a bug in the keyboard input driver (not returning something that the gamepad driver does) - @benvanik can we have a flag to disable this?
Thinking about a game on real hardware, most would just pop up a window saying "controller not connected" or similar
It may be returning the wrong error code, however if you are launching with --hid=any (the default) it shouldn't be failing to find the device, as the keyboard device should always be found. Unless that is broken. Try launching with --hid=winkey to force xinput to be disabled.
Is there a way to disable all input drivers?
There always needs to be one, but the no-op driver should be the same thing, effectively --hid=nop
--hid=nop
- boots
--hid=winkey
- boots
--hid=xinput
- boots
--hid=any
- hang
Could be iterating multiple drivers that's breaking things.
Marketplace
Tested on xenia-project/xenia@fc7695f
Issues:
Loads to black screen, then hangs without a controller connected. I'm not sure where. Please let me know if there are any threads you are particularly interested in.
The logs show repeated calls for
XamInputGetKeystrokeEx(7010F954(0), 00000002, 7010F990)
, it's trying to detect a controller?With a controller connected, I can mash some buttons and get to what looks like a title screen with not much drawn correctly
If you're testing this on Windows you might need https://sourceforge.net/projects/turnoffxboxcontroller/files/latest/download to turn off your 360 controller
Screenshot(s):
Logs:
4B4E880E.zip
Labels:
state-load, xam-input-problems, gpu-drawing-corrupt