Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to create GameInput instance: 0xD0000034 #35

Open
Dirtmigurt opened this issue Aug 22, 2024 · 2 comments
Open

Failed to create GameInput instance: 0xD0000034 #35

Dirtmigurt opened this issue Aug 22, 2024 · 2 comments

Comments

@Dirtmigurt
Copy link

That is the only log I get. Can't find documentation for this HRESULT value.

@Dirtmigurt
Copy link
Author

According to MSFT error lookup tool https://learn.microsoft.com/en-us/windows/win32/debug/system-error-code-lookup-tool

Value 0xd0000034 is an NTSTATUS value: treating as 0xc0000034

It is either

ISCSI_ERR_CONFIG_IPSEC_TIMED_OUT iscsilog.h

Initiator Service failed to respond in time to a request to

configure IPSec resources for an iSCSI connection.

or

STATUS_OBJECT_NAME_NOT_FOUND ntstatus.h

Object Name not found.

2 matches found for "0xD0000034"

@TheNathannator
Copy link
Owner

Did you figure this one out yet, or are you still having issues?

This looks to me like GameInput isn't properly installed on your system. Which is weird, since the RB4InstrumentMapper installer is supposed to ensure that. Try following the manual install instructions I posted here: #27 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants