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

×
General Troubleshooting
-----------------------

1. black screen / crash on launch:

- Before starting the game, change video resolution to your desktop one (or the closest match). if that fails, try falling back to 1024x768. Video settings can be found under GOG Galaxy HERE
-- or in Start Menu HERE.

- Close any unnecessary applications running in the background, especially ones overlay-based like EVGA Precision, MSI Afterburner, GeForce Experience, FRAPS etc.

- If running multiple screen setup, try switching to a single monitor.

If none of the above helps, please send your DxDiag to our Support team HERE. The more information we have, the easier it will be to pinpoint the problem.

2. Controllers
- connect (turn on if wireless) your controller before starting the game
- start the game, go to Settings->Joystick Settings
- set Joystick to Enable
- press Default to fill controls with standard mapping or configure them manually

-------------
May the Force serve you well.
Post edited May 02, 2018 by Thiev
I found that the crash after blue bar issue was casued by permissions on the install folder.

After looking in the event log i could see that for unknown reasons that my user wasnt allowed to run stuff from the folder.

Changed the security policy on the folder and bobs your uncle :)
Installing DirectX 2010 worked for me from another support thread
I have a solution or better workaround for people, who have a crash at the blue loading bar on the startup before the intro FMVs. You know there, where the loading bar is loading a bit and then crashs without an error.
Here is the workarround, the problem is one of the HID devices, at least it was here at me.
You have to open the Windows device manager and then look for the Human Interface Devices. Then you have to try by deactivating the devices one by one, which device causes the error in Ep1 Racer. I attachted a screenshot (sorry it is in german) so you can see what you have to look for. For me it was the middle of the 5 devices. As I said you have to try, for you which causes the error. If you found the right, you have propably to reboot your computer. Please note, if you deactivate the device, something on your PC can no longer be controlled. I have an Alienware computer and in this case I can not change the lighting effects anymore.

So you have turn the device back on after playing. Same workarround also works with Myst 4, which also crashes at startup.

Maybe GOG can fix this?
Attachments:
hid.jpg (98 Kb)
high rated
avatar
Shinzon: I have a solution or better workaround for people, who have a crash at the blue loading bar on the startup before the intro FMVs. You know there, where the loading bar is loading a bit and then crashs without an error.
Here is the workarround, the problem is one of the HID devices, at least it was here at me.
You have to open the Windows device manager and then look for the Human Interface Devices. Then you have to try by deactivating the devices one by one, which device causes the error in Ep1 Racer. I attachted a screenshot (sorry it is in german) so you can see what you have to look for. For me it was the middle of the 5 devices. As I said you have to try, for you which causes the error. If you found the right, you have propably to reboot your computer. Please note, if you deactivate the device, something on your PC can no longer be controlled. I have an Alienware computer and in this case I can not change the lighting effects anymore.

So you have turn the device back on after playing. Same workarround also works with Myst 4, which also crashes at startup.

Maybe GOG can fix this?
There's some truth to this, I'm currently neck deep in assembly debugging to identify this issue. See attached files, the application is trying to access memory it's not allowed to in the dinput call for CHID_InitAxisClass. (I had to enable pages and stack backtracing with the GlobalFlags windows app). I'll follow up if I find a useful workaround that doesn't involve turning off and on your HID devices.

I can confirm that disabling this particular HID device fixed my loading hiccup 100% (mmc_2018-07-18_0.png).

I've submitted a support ticket to update these troubleshooting steps, perhaps they'll take a closer look with this additional information and we won't have to have such a janky work around in the future.


EDIT:

I've automated this as a batch file using Microsoft's Devcon tool, check out my full post:
Attachments:
Post edited July 18, 2018 by Tehelee
Thanks guys for the help. I've wanted this game for a long time and getting it on GOG made my day.

I just started playing it today, but I had to stop here first to get it running.

I purchased a Nintendo 64 just for this game nearly 20 years ago.
This did not help me out at all, I have no USB devices installed other than mouse and kb.

I am really done fighting with these games....
Post edited November 11, 2018 by NullARC11
The game doesn't respond to my steering wheel. I have a Logitech G29 Force Feedback steering wheel connected to my computer, but when I tried to turn on Force Feedback in the options menu, the game says that it can't detect a Force Feedback device. I've had a similar problem with other racing games, too.
Mine is Working Yet :D
Thanks for helping and supporting!
Wish That Yours Gaves Right Too
Thanks
So after nothing what I found here really helped much, I fiddliled around with the trusty 'ol Compatibility Administrator from the MS ADK.
(It offers advanced compatibility mode settings/fixes)

the attached image shows what fixed the crash on load for me

Optional:
DirectPlayEnumOrder causes the game to run at a lower probably capped framerate. Though I think that is necessary for the engine to work properly. The game physics are framerate dependant. Without the framerate cap sliding has almost no effect and the podracers stick to the ground like a magnet.

I found that the game is much more fun with the capped framerate as you actually slide if you press the 'slide' button and ramps actually lift you off the ground and you get proper airtime.
... although it is entirely possible to beat the game without the fps cap.


aside from that after some races the game first starts to lose textures on some/most surfaces and then crashes on the next loadscreen.
Any Ideas what to add to fix that?
Attachments:
fixes.png (7 Kb)
Post edited June 03, 2019 by S-p-Ace
I am trying to run star wars pod rader on Win 10 64 bit. I can calibrate my wingman extreme in winders just fine but Racer does not recognize my device. Apparently there are no drivers needed.