Posted July 18, 2018
high rated
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. 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) 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.
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. 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) 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.
Attachments:
swep1rcr_2018-07.png (19 Kb)
gflags_2018-07-1.png (20 Kb)
devenv_2018-07-1.png (78 Kb)
mmc_2018-07-18_0.png (44 Kb)
Post edited July 18, 2018 by Tehelee
