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

×
Hi guys,

So there are several threads already, asking for different things about GOG release, so I will try to ask thing here, in one thread only:

- which of these bugs have been fixed in GOG version?

- more than 4 cores (VERY essential fix) - EDIT:// still present - thanks virtualmarc
- some crashes later on in the game that Pandemic never got around to fixing, including one during a driving sequence that would crash at the same spot every time - EDIT:// probably fixed/nothing serious remains - thanks JMich
- any other (in/famous) bug, I haven´t explicitly mentioned (feel free to mention them below)

- map bug (YES, this is fixed)
- Nudity DLC - YES, this is part of the release, this has been answered in a release thread already.

And my last question: is there any unofficial patch out there (like the one for Vampire The Masquerade: Bloodlines, which is essential for playing) ?

Thanks for answers.
Post edited September 24, 2016 by Tarhiel
This question / problem has been solved by PraetorianWolfieimage
The bug that it doesn't start with more than 4 physical cores is still there. I still have to deactivate some cores in the EFI to be able to play it.
avatar
Tarhiel: - some crashes later on in the game that Pandemic never got around to fixing, including one during a driving sequence that would crash at the same spot every time.
Most likely fixed, since only crashes I had where out of memory ones on extra long play sessions. Can't recall any mission crashing on me, though I did intimidate the other drivers on the racing missions.
avatar
virtualmarc: The bug that it doesn't start with more than 4 physical cores is still there. I still have to deactivate some cores in the EFI to be able to play it.
avatar
JMich:
Thanks, guys.

Damn, that 4 cores bug is pretty critical, I don´t understand how EA went about not fixing it and happily selling the game.

I was only able to find this patch, but that is not unofficial one + it seems it still has that 4 cores bug problem.
avatar
Tarhiel: Thanks, guys.

Damn, that 4 cores bug is pretty critical, I don´t understand how EA went about not fixing it and happily selling the game.

I was only able to find this patch, but that is not unofficial one + it seems it still has that 4 cores bug problem.
I think this patch is identical to the one also mentioned in the EA forums here:
http://answers.ea.com/t5/Other-EA-Games/The-Saboteur/m-p/2469348/highlight/true#M14357

The patch is 1.03 beta patch for the Origin version of the game and was released by Pandemic Studios back in 2009. So it is official -- but nothing says that it would work with the GOG version. I don't think Pandemic ever released another patch or a "final" version for the 1.03.

The changelog for the 1.03 beta patch is:
-------
Game no longer freezes during play on the following hardware combination:
* ATI video card from the 3K, 4K, and 5K series
* Windows Vista/7 both 32 bit and 64 bit

Known Issues & Current Workaround:

Users with Quad core CPU's will possibly have significant streaming issues without the following work around. The team is aware of this issue and is working on a fix for it in the next patch update. If you are running a Quad Core CPU please follow the steps below to set Game Only affinity on your CPU. While this will decrease the amount of streaming glitches, it is not a full proof fix.

Recommended Game-only steps for Quad core users only:

Windows 7 and Vista

1.) Boot the game.
2.) Wait for the main menu to load, then press Ctrl-Alt-Delete.
3.) Select Start Task Manager.
4.) If the game is visible, press Alt-Tab, otherwise continue to the next step.
5.) Inside the Task Manager, go to the Processes tab.
6.) Find Saboteur.exe, right-click it, and select Set Affinity...
7.) De-select CPU 2 and CPU 3.
8.) Click OK.Game no longer freezes during play on the following hardware combination:
* ATI video card from the 3K, 4K, and 5K series
* Windows Vista/7 both 32 bit and 64 bit

Known Issues & Current Workaround:

Users with Quad core CPU's will possibly have significant streaming issues without the following work around. The team is aware of this issue and is working on a fix for it in the next patch update. If you are running a Quad Core CPU please follow the steps below to set Game Only affinity on your CPU. While this will decrease the amount of streaming glitches, it is not a full proof fix.

Recommended Game-only steps for Quad core users only:

Windows 7 and Vista

1.) Boot the game.
2.) Wait for the main menu to load, then press Ctrl-Alt-Delete.
3.) Select Start Task Manager.
4.) If the game is visible, press Alt-Tab, otherwise continue to the next step.
5.) Inside the Task Manager, go to the Processes tab.
6.) Find Saboteur.exe, right-click it, and select Set Affinity...
7.) De-select CPU 2 and CPU 3.
8.) Click OK.
-------

I am not sure if the GOG version already has this patch applied!
Is the core issue only with physical cores, or does it also apply to Hyperthreading as well?
avatar
Awkiba: Is the core issue only with physical cores, or does it also apply to Hyperthreading as well?
I think it's only physical cores.
With 6 physical cores the game won't launch for me at all.
With 4 active and 2 disabled (from BIOS) and H/T enabled, the games runs fine.
avatar
Awkiba: Is the core issue only with physical cores, or does it also apply to Hyperthreading as well?
avatar
PraetorianWolfie: I think it's only physical cores.
With 6 physical cores the game won't launch for me at all.
With 4 active and 2 disabled (from BIOS) and H/T enabled, the games runs fine.
Thank you for the response!
Strange. I used to play the disc version on my win7 64 with an I7 and it worked flawlessly. Never realised there was a quad core problem. The I7 has 6 cores, right?
Post edited October 01, 2016 by Goopydop
avatar
Goopydop: Strange. I used to play the disc version on my win7 64 with an I7 and it worked flawlessly. Never realised there was a quad core problem. The I7 has 6 cores, right?
Depends on the model. But most models are quadcores with hyperthreading.
avatar
Goopydop: Strange. I used to play the disc version on my win7 64 with an I7 and it worked flawlessly. Never realised there was a quad core problem. The I7 has 6 cores, right?
avatar
AHappyTurtle: Depends on the model. But most models are quadcores with hyperthreading.
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.
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.
Yeah, I have an i7 too (3770) and the game runs fine. I'm not quite sure I understand the quad core-bug...
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.
avatar
AHappyTurtle: Yeah, I have an i7 too (3770) and the game runs fine. I'm not quite sure I understand the quad core-bug...
Neither do I, I just hope that bug will not manifest on my PC.
The i7s you guys are talking about have 4 cores, 8 hyperthreaded.

For those of us with CPUs with more than 4 cores, the game doesn't boot at all, unless some are disabled in the BIOS, which is a complete pain.

Some users with exactly 4 cores have reported LOD issues, totally unrelated to the above.

Hope that helps!
I played the original PC release on my current motherboard pre-gog with an i7 3770k; however, that was when I was running Windows Vista x64 and with an ATI GPU. Haven't tried it again since my last round of upgrades though so don't know how it would work on the Nvidia GPU and Windows 10 I have today. On the old setup it did require the task manager workaround for disabling the extra cpu cores or else randomly game would hard crash losing any progress since last save. Typically crashes would occur after 1hr plus of playtime though sometimes it was only 20 minutes or so. It was not the unlauchable game issue some have experienced and even with the ea hotfix the cpu multicore lockup bug was still confirmed.

Hopefully this issue is resolved in Windows 10 natively, else GOG.com will need to have a fix for it at some point. When it had been a while since I played I would always forget to do the core disable workaround until I had crashed which means for some of the late game missions which take a long time I got to play them a bunch of times, since after a crash I would often decide I needed to do something else instead of playing the same thing over again.
Post edited October 05, 2016 by BlueKronos