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

×
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.
Attachments:
Post edited July 18, 2018 by 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.
Attachments:
Thank you for this post! I have the Corsair Void Pro too, so I tried unplugging the receiver and the game launched perfectly. You can reconnect it after the game finishes booting and it works just fine. That is kind of annoying to do every time so I'll look into using your method later, but for now this is perfect, thank you!
avatar
Koden.685: Thank you for this post! I have the Corsair Void Pro too, so I tried unplugging the receiver and the game launched perfectly. You can reconnect it after the game finishes booting and it works just fine. That is kind of annoying to do every time so I'll look into using your method later, but for now this is perfect, thank you!
You have also to thank me ;). I was the one who found out. But Tehelee made this great Batch file, which is automate this process, thanks for this. :)

I also added my Hardware ID, which causes the error for me.
Attachments:
Post edited July 21, 2018 by Shinzon
avatar
Koden.685: Thank you for this post! I have the Corsair Void Pro too, so I tried unplugging the receiver and the game launched perfectly. You can reconnect it after the game finishes booting and it works just fine. That is kind of annoying to do every time so I'll look into using your method later, but for now this is perfect, thank you!
avatar
Shinzon: You have also to thank me ;). I was the one who found out. But Tehlee made this great Batch file, which is automate this process, thanks for this. :)

I also added my Hardware ID, which causes the error for me.
Yeah as I pointed out in my post you were super right about this; I was coming from the crashdumps and backtrace when I stumbled upon your post as I was writing up my findings on here. I figured it was still worth posting the confirmed cause and I decided to write the batch file to make my life easier.

I'm working on my one-stop-shop trainer that already re-enables the debug menu, ideally I'll include a fix to the executable so we won't have this issue anymore.
avatar
Shinzon: You have also to thank me ;). I was the one who found out. But Tehlee made this great Batch file, which is automate this process, thanks for this. :)

I also added my Hardware ID, which causes the error for me.
avatar
Tehelee: Yeah as I pointed out in my post you were super right about this; I was coming from the crashdumps and backtrace when I stumbled upon your post as I was writing up my findings on here. I figured it was still worth posting the confirmed cause and I decided to write the batch file to make my life easier.

I'm working on my one-stop-shop trainer that already re-enables the debug menu, ideally I'll include a fix to the executable so we won't have this issue anymore.
And this with the Batch file is great work. I didn't even knew, that is possible to do it on the easy way.
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.
Here are the Hardware IDs that crashed mine.

0x0A66 seems to be "Logitech, Inc. [G533 Wireless Headset Dongle]".
I don't know what 0x0A67 is but its Logitech again.
Attachments:
I ended up discovering the same thing. My constant crashing was a USB wireless headset (afterglow) Instead of going 1 by 1 through device manager you can also just plug/unplug all your usb devices and try to launch the game till you discover the offending device.
avatar
AlphaPapa10784: I ended up discovering the same thing. My constant crashing was a USB wireless headset (afterglow) Instead of going 1 by 1 through device manager you can also just plug/unplug all your usb devices and try to launch the game till you discover the offending device.
Yes, of course, if it is a removable device. But in my case it is the lightning of my casing and this I can not unplug :D.
In my case, it was the orientation sensor in my Surface Pro 3:

HID\VEN_MSHW&DEV_0030&REV_3090850&Col03
HID\VEN_MSHW&DEV_0030&Col03
HID\MSHW0030&Col03
HID\*MSHW0030&Col03
HID\VID_045E&UP:FF04_U:0050
HID_DEVICE_UP:FF04_U:0050
HID_DEVICE_UPR:FF00-FFFF
HID_DEVICE
Post edited December 06, 2018 by nockgeneer
Mate of mine said this worked a treat for her, so thank you so very much! We've been reminiscing while she struggles, haha. I never got it working myself and got a refund, but since this worked for her... I might very well buy it again.

She had two instances of the same hardware ID so we had to block both occurrences of:

HID\VID_1B1C&PID_1B1C&REV_0380&Col02

Which had another shorter ID of:

HID\VID_1B1C&PID_1B1B&MI_03&Col02

The only thing different in the second instance was the second PID:

HID\VID_1B1C&PID_1B1C&Col02

I also checked her Event Viewer to try and see what it was. Not sure if its related but at the same time, the Windows 10 Push Notification service was apparently returning error codes.
Post edited December 13, 2018 by Varell
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.
This workled perfectly fine for me
Great thanks to both of you

Also added the device for fixing, have fun guys. im playing now
Attachments:
After a good hour of google-searching I found your post, and just wanted to thank you for making me able to play this old gem.

I know the post is a year old, but just wanted to let you know your work is still helping people :D
Have to toss this in in case the devs look, there's 100% an issue with how this game detects a Corsair Void Pro.

I bought this game a couple hours ago, went through the beginnings of troubleshooting the game as it would always get stuck on the initial load. Tried changing the start up resolution, tried changing my PC resolution. If it was set to default, it would crash. Otherwise it would freeze on the initial loading if I changed anything else.

Found this post, literally yanked out my Corsair bluetooth transmiiter and now the game boots like a dream.
Hi, I disconnected the USB receiver of my wireless Logitech mouse, and all the devices under HID disappeared at once. It even removed the HID submenu from the devices manager.

Then I launched the game and it crashed as always :-(
Any other idea?

Best regards.