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
AHappyTurtle: Depends on the model. But most models are quadcores with hyperthreading.
avatar
Goopydop: Oh. I've fallen behind on my CPU knowledge. I have an I7 6700 on my windows 10 machine and the game launches and runs fine though. It has 4 cores and 8 logical processors.
I have an I7 6700K on Win 10, the game won't launch, instant CTD... Weird, it's a 4 cores and 8 logical too.
avatar
Dark_Trinity: I have an I7 6700K on Win 10, the game won't launch, instant CTD... Weird, it's a 4 cores and 8 logical too.
Have you tried manually creating a working ini-file so it's not trying to start a higher refresh rate higher than 60Hz?

Also, mandatory with Win10: disable desktop composition and visual themes and play with the compatibility settings.
avatar
Dark_Trinity: I have an I7 6700K on Win 10, the game won't launch, instant CTD... Weird, it's a 4 cores and 8 logical too.
avatar
Nirth: Have you tried manually creating a working ini-file so it's not trying to start a higher refresh rate higher than 60Hz?

Also, mandatory with Win10: disable desktop composition and visual themes and play with the compatibility settings.
The .ini file is ok. I tried literally everything, except core disabling for obvious reason... i'll wait for another week and get a refund i think :(
avatar
Dark_Trinity: The .ini file is ok. I tried literally everything, except core disabling for obvious reason... i'll wait for another week and get a refund i think :(
I don't think you need to disable any physical cores but what you should try is disabling Hyper Threading in BIOS, that should work if the problem is your CPU and not Windows 10 although I wouldn't rule out Windows 10 yet but if it still doesn't work after disabling Hyper Threading it might be the combination of your hardware and OS that ends up causing some conflict.
There's another bug which existed in the console and PC versions and wasn't patched on account of the Pandemic studio closure. It's specifically the 'Blockbuster perk' under demolitions where you've to destroy 3 Wulf tanks using RDX or dynamite which unlocks the Super RDX upgrade.

The bug is if you die or if you ever stop playing and then reload a save file - you permanently lose Super RDX (which appears in the gun smugglers menu as "Super RDX") . The gun smugglers will have "Super RDX" on their menu in place of "RDX" after you earn the perk - but not if you die or ever turn the game off.

The only solution to this is destroying 2 of 3 tanks, backing up the save file. Then starting from that save point and completing the task i.e. if you want to tinker around with the 'Super RDX' . But you'll be stuck with the normal RDX if you die or if you reloaded a later save file.

The explosions from the Super RDX looks great when compared to the measly RDX.


Would be great if someone from the GOG team would answer if this was fixed too.
avatar
PapaShango: There's another bug which existed in the console and PC versions and wasn't patched on account of the Pandemic studio closure. It's specifically the 'Blockbuster perk' under demolitions where you've to destroy 3 Wulf tanks using RDX or dynamite which unlocks the Super RDX upgrade.

The bug is if you die or if you ever stop playing and then reload a save file - you permanently lose Super RDX (which appears in the gun smugglers menu as "Super RDX") . The gun smugglers will have "Super RDX" on their menu in place of "RDX" after you earn the perk - but not if you die or ever turn the game off.

The only solution to this is destroying 2 of 3 tanks, backing up the save file. Then starting from that save point and completing the task i.e. if you want to tinker around with the 'Super RDX' . But you'll be stuck with the normal RDX if you die or if you reloaded a later save file.

The explosions from the Super RDX looks great when compared to the measly RDX.

Would be great if someone from the GOG team would answer if this was fixed too.
Someone said in another thread that it was not fixed.

I'd still like for it to be fixed, there's no EA holding them back now (I remember the empty promises of patches they gave after the game went out... classic EA).