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
ZGT: Just encountered this issue on my PC, getting an older no-CD patch as mentioned my @randommonsters above worked, but while messing around with the files I found out that somehow changing the name of the .exe file also solved the issue. When it's named fforce.exe the game crashes after the Crave logo, after renaming to anything else it starts with no problems whatsoever. I have no idea why it works, but I'm sharing my find in case anyone experiences the same situation.
Trippy. I just changed it from fforce to force and it worked plain as day. Thank you for posting this.
avatar
soundchaser1: I had the same problem, bought the game yesterday. Tried various settings under Win 10 and dgvoodoo2, nothing worked. Game crashed after the second screen. Unfortunately I wasn´t allowed to past a link, but there is a topic on gog where it says to add "-w" to the execution file (fforce-w). This finally worked for me and full-screen is still enabled.

My other settings: Combatilbilty mode off, Dgvoodoo 2 DirectX Settings: Disable and passthru to real DirectX. So far I just tried to load the first mission, no problems at first glimpse.

Good Luck!
Adding the "-w" worked like a charm thanks!
avatar
soundchaser1: I had the same problem, bought the game yesterday. Tried various settings under Win 10 and dgvoodoo2, nothing worked. Game crashed after the second screen. Unfortunately I wasn´t allowed to past a link, but there is a topic on gog where it says to add "-w" to the execution file (fforce-w). This finally worked for me and full-screen is still enabled.

My other settings: Combatilbilty mode off, Dgvoodoo 2 DirectX Settings: Disable and passthru to real DirectX. So far I just tried to load the first mission, no problems at first glimpse.

Good Luck!
avatar
Darabka: Adding the "-w" worked like a charm thanks!
Ditto for me. tried this first before going down the rabbit hole with fixes and worked right off the bat.
avatar
ZGT: Just encountered this issue on my PC, getting an older no-CD patch as mentioned my @randommonsters above worked, but while messing around with the files I found out that somehow changing the name of the .exe file also solved the issue. When it's named fforce.exe the game crashes after the Crave logo, after renaming to anything else it starts with no problems whatsoever. I have no idea why it works, but I'm sharing my find in case anyone experiences the same situation.
renaming the file instantly worked without the need for doing anything else. I don't know how you figured it out but you're a genius.
avatar
ZGT: Just encountered this issue on my PC, getting an older no-CD patch as mentioned my @randommonsters above worked, but while messing around with the files I found out that somehow changing the name of the .exe file also solved the issue. When it's named fforce.exe the game crashes after the Crave logo, after renaming to anything else it starts with no problems whatsoever. I have no idea why it works, but I'm sharing my find in case anyone experiences the same situation.
avatar
elephantelephant: renaming the file instantly worked without the need for doing anything else. I don't know how you figured it out but you're a genius.
Never encountered such a thing. I would guess GOG could not completely remove the old DRM Securom from the game's data and it crashes if it sees the filename.

Anyways thank you citizen, your solution worked like a charm. FOR FREEDOM! :D
avatar
ZGT: Just encountered this issue on my PC, getting an older no-CD patch as mentioned my @randommonsters above worked, but while messing around with the files I found out that somehow changing the name of the .exe file also solved the issue. When it's named fforce.exe the game crashes after the Crave logo, after renaming to anything else it starts with no problems whatsoever. I have no idea why it works, but I'm sharing my find in case anyone experiences the same situation.
Wow, it's crazy to think that such a simple fix would work, or that something so bizarrely rudimentary would be the cause of the issue at all. And yet, that's all it took to get this running, Thanks!