It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
Tehelee: If this solution works for you, could you please post the Hardware ID from the incompatible device.
Device Manager -> Human Interface Devices -> [BAD DEVICE] -> Properties -> Details -> Hardware Ids

See the attached picture for an example; just highlight the longest one and hit ctrl+c to copy to clipboard and paste it here.
If Your still interested: HID\VID_045E&PID_0922&Col0A
disabled this bad boy and away we go! :)
avatar
Tehelee: Does this loading bar look familiar? (SWEP1RCR_2018-07-18_02-27-43.png)
Have you been getting the dreaded "rdroid_gnome release build has stopped working"?

This is caused by an unsupported "HID-compliant vendor-defined device".
There's probably nothing wrong with the device, it's most likely working just fine for you, but Star Wars hates it.
(I had to reverse stack-trace the assembly code of the game to pinpoint this delightful error.)

The solution is to pop open Device Manager, look under Human Interface Devices, and disable and re-enable each one (launching star wars each time you disable one) until it finally boots to the menu. Mine was one of the last devices in the list and happened to be my Corsair Void Pro's headset buttons (the speakers and mic were separate).

NOTE: There may be more than one unsupported device in your system, the safest bet is to disable them all and re-enable one by one starting each time to check. If your keyboard and mouse are one of these devices, they will still function for now, but don't reboot without enabling your devices again or you may find them unresponsive when you boot next.

Now I'm sure you're ecstatic that you can finally show Anakin he's not the only racer in the sector, but it's going to get tedious disabling and re-enabling that device each time you want to play. So I made a handy batch file that uses Window's Devcon tool to automate this whole process for you. Take a look at the linked zip and follow the readme instructions to set it up for your device (each hardware id is different, so be sure to configure it properly).

Here's the zip on my google drive so you can see the contents yourself, if you're uncomfortable downloading the devcon.exe get the other files and go get the executable from microsoft.
avatar
Tehelee: This batch file is only configured to toggle a single troublesome device, but it's plain text and with a little googling I'm sure you can tailor it to multiple if that's the case.

As for the breakdown of why, I had to use Window's built-in Global Flags application to enable reverse stack-tracing and some other options for SWEP1RCR.exe (see gflags_2018-07-18_01-45-15.png)

Now that I'm getting useful information from the crash dumps other than a write access error, we can see the real issue (devenv_2018-07-18_01-48-47.png)
dinput.dll!_CHID_InitAxisClass@16()
There's a lot of jargon, but it's failing trying to check all the HID devices, (at least) one of them isn't supported.

Disabling the incompatible device in Device Manager fixes the issue (mmc_2018-07-18_02-10-54.png)
avatar
Tehelee: Frankly I'm so freaking happy to be able to consistently play the game now, not a single other solution worked and I fully appreciate the frustration many of you are going through. If this still does not fix your issue and you've tried the other trouble shooting steps please contact me directly and I'll do my best to help so that others won't have the same problems.
Just found this post and everything works now.
I found 2 devices id that created troubles:

HID\VID_046D&PID_0A5B&REV_0101&MI_03&Col04

HID\VID_046D&PID_0A5D&REV_0101&Col02

Didn't know what they really are but game starts now.

I don't know how to edit the batch file in order to fill it with 2 different id. No problem, I memorized them and enable/disable manually each time.

Thanks a lot, greetings from Italy. May the Force be with you
avatar
Zeo90: Just found this post and everything works now.
I found 2 devices id that created troubles:

HID\VID_046D&PID_0A5B&REV_0101&MI_03&Col04

HID\VID_046D&PID_0A5D&REV_0101&Col02

Didn't know what they really are but game starts now.

I don't know how to edit the batch file in order to fill it with 2 different id. No problem, I memorized them and enable/disable manually each time.

Thanks a lot, greetings from Italy. May the Force be with you
Another guy made a fix, so you don't have to disable HID Devices everytime. Just place the dinput.dll in same folder where the exe file is and run the game. Look here for download:


https://www.gog.com/forum/myst_series/unable_to_run_myst_iv_revelations/post74
Post edited April 03, 2020 by Shinzon
avatar
Zeo90: Just found this post and everything works now.
I found 2 devices id that created troubles:

HID\VID_046D&PID_0A5B&REV_0101&MI_03&Col04

HID\VID_046D&PID_0A5D&REV_0101&Col02

Didn't know what they really are but game starts now.

I don't know how to edit the batch file in order to fill it with 2 different id. No problem, I memorized them and enable/disable manually each time.

Thanks a lot, greetings from Italy. May the Force be with you
avatar
Shinzon: Another guy made a fix, so you don't have to disable HID Devices everytime. Just place the dinput.dll in same folder where the exe file is and run the game. Look here for download:

https://www.gog.com/forum/myst_series/unable_to_run_myst_iv_revelations/post74
When I tried the dinput.dll it successfully launched the game without me having to disable any devices, however... my Xbox One controller wouldn't work anymore. Everything I tried, I couldn't get the controller to work when using the dinput.dll file. Proceed with caution if you are going to use the dinput.dll method.

Best case for me was to NOT use the dinput.dll and instead to disable the problematic device:
HID\VID_1B1C&PID_0C04&REV_0200

And just in case anybody is curious, disabling that hardware device (haven't yet identified what it is) is all I need to get the game running. No need for any compatibility settings. I can run the game full resolution, full colors.
Post edited June 23, 2020 by joeymad
avatar
Zeo90: Just found this post and everything works now.
I found 2 devices id that created troubles:

HID\VID_046D&PID_0A5B&REV_0101&MI_03&Col04

HID\VID_046D&PID_0A5D&REV_0101&Col02

Didn't know what they really are but game starts now.

I don't know how to edit the batch file in order to fill it with 2 different id. No problem, I memorized them and enable/disable manually each time.

Thanks a lot, greetings from Italy. May the Force be with you
avatar
Shinzon: Another guy made a fix, so you don't have to disable HID Devices everytime. Just place the dinput.dll in same folder where the exe file is and run the game. Look here for download:

https://www.gog.com/forum/myst_series/unable_to_run_myst_iv_revelations/post74
"Just place the dinput.dll in same folder where the exe file is and run the game", didn't work for me and disabling the " HID Devices" one by one didn't work because I have three HID Devices IDs that are causing the issue so basically only when I disabled all the HID Devices and then enabled them one by one did I discover that, also only enabling them in the reverse order, bottom to the top, would Windows 10 allow me to enable them back on one by one as the other way would just re-disabled them!
Unfortunately I only learned Disabling the HID Devices worked after I had done the voodoo fix and as it works well enough with the three HID Devices disabled with the voodoo fix I can't be bothered reversing the voodoo after messing around after three days of trying and it now working.
Device hunt website can only give me the USB vendor and not the specific device ID which isn't an issue on the two Samsung USB IDs as they both belong to the Samsung Odyssey plus VR headset but the third HID Devices ID just attributed to MSI which is my motherboard manufacturer and without the device ID I am unable to narrow it down as to which port is the culprit!
Anyway here are the Samsung HID Devices IDs which both belong to the same VR headset:
HID\VID_04E8&PID_7312&REV_0200&Col01
USB\VID_04E8&PID_7084&REV_0005&MI_03

And for the problematic MSI USB device or port these are the HID Devices ID:
HID\VID_1462&PID_7B92&REV_0001

Hope that helps other people.
Post edited June 25, 2020 by optical10GOG