SHODAN can't be beat in cyberspace, the screen is filling up WAY faster than in the original (or in the Portable/DOSBox versions).
It's supposed to take about 30 seconds, but in the enhanced edition it's more like 10 seconds.

I guess there is a CPU timing issue? The rest of the game runs at normal speed, looks like it's just an issue with the screen filling thing.

EDIT: I double checked it with both SSP and Youtube videos of the DOS version. The screen fills up about three times faster in the enhanced edition, which makes the fight pretty much impossible.

EDIT: savefile right before the final cyberspace is here:

https://www.dropbox.com/s/5z03xvu5dgef8gw/savgam04.dat?dl=0

EDIT: success! http://i.imgur.com/EL16Ed9.gif

conclusion: it seems to be be somewhat more doable if you turn on vsync and/or bump up the resolution.
Just finished it like that, but the default settings make that part of the game run way too fast, at least on my computer (my CPU is a 6 year-old Phenom II X4, not exactly high-end.)

please post a save right before the event (from the LGS readme: Your saved games are stored in your sshock\data directory (or a subdirectory of whatever directory you installed the game to). These eight files are called savgam00.dat, savgam01.dat, ... savgam07.dat.)).

This is exactly the thing that CPU brake patch was avoiding. It seems that GOG or nightdive forget about that bit, which is strange, as SSP had the patch included by default.

System Shock Portable didn't have a patch for this, but a workaround: It included a CPU slowing program that could be run from the SSP launcher to slow down the game for the endboss.
Of course this problem didn't happen quite so often in SSP, because DOSBox emulation would slow down the CPU already.

@Malba: If possible this should be fixed by tying the duration of the endboss fight to an actual timer instead of framerate.

Yes, this is what i meant by "patch (all SPP "patches" are workarounds or tricks, there are no real engine modifications, AFAIK).

It is not possible to modify what endfight syncs to, but it could be possible to sync framerate to timer, thus - by extension - achieving the same result. No idea of it could be done automatically, though - might require user enabling it before loading endboss savegame, just like in SPP.

/Estel

nobody tested it even to the extent of playing through the whole game before asking for money for it?
ok

Hello , Whelp !

Please , attach your save file.

This was my first thought. Not that I've even downloaded the game yet (I wasn't even going to buy but I figured eh, I was saving #2 again until then), but it would have been nice to test from start to finish.

Is this end boss bug going to be fixed? I bought this game immediately, and am now wondering if I spent money on a broken game. The devs of this enhanced edition should issue a patch as soon as possible.

everyone got this bug ? ... or is it just "bad luck"

i finished lvl 2 now and its a blast so far ... still time till i see this boss ... but it would be a real bummer if this bug isnt fixed soon tm

or at least a message from the devs that we know that they are aware of this ... because this isnt some clipping stuff thats a game breaker

I just finish the game with savefile you provided (just click to see 'happy ending' screen ).

So - it's all fine to me.

Sorry - but I can't help , 'cause I can't reproduce the bug . :(


PS : Try to turn on vsync . Maybe ...

How long did the screen take to fill up for you approximately?

EDIT: Hmm you mean force vsync in video drivers? Could be worth a shot.

EDIT: nvm, that was a brainfart. Can't force vsync in a software rendered application I guess.

Nope .

I mean - to turn it on in sshock.ini .

; Vertical synchronization
; Options: On, Off
VSync=On ahemmm ....

More than 10 seconds - that's fo sure . I'm no a SS-pro to deal with SHODAN in just one click . :)

Just timed it. Takes 9 seconds then you're dead. Not enough time to blast her.

I'll try bumping the resolution way up, maybe that'll slow things down enough? ;)

EDIT: yeah just turned on vsync in the config, seemed to give me a *little* more time (but still way less than the original):

http://i.imgur.com/EL16Ed9.gif