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

×
Evening, I dont know how or what happen, but I 've reinstalled the SS Enhanced version, started and after the intro i DID NOT USE the mouse to make my choise, like difficoult and etc...i use the keyboard, aftert started the game and....IT WORKS.... so strange.
so, does it still crash when you try to use the mouse?
avatar
nello66: Evening, I dont know how or what happen, but I 've reinstalled the SS Enhanced version, started and after the intro i DID NOT USE the mouse to make my choise, like difficoult and etc...i use the keyboard, aftert started the game and....IT WORKS.... so strange.
Does it work the second time you launch the game? or 3rd time?
We've found a possible fix (Thanks Glowhyena for working with me on this)

The sshock.ini that was shipped has this setting inside it:

; Custom screen resolution
; Select the width, height and aspect
; Aspect should be set to zero for automatic calculation
; For manual aspect, set its value using the formula Height / Width * 65536
; WARNING: Resolutions higher than 1024x768 may crash the system
CustomWidth=854
CustomHeight=480
CustomAspect=0

Change this to read:

; Custom screen resolution
; Select the width, height and aspect
; Aspect should be set to zero for automatic calculation
; For manual aspect, set its value using the formula Height / Width * 65536
; WARNING: Resolutions higher than 1024x768 may crash the system
CustomWidth=1024
CustomHeight=768
CustomAspect=0

All test so far are showing this is fixing the problem on affected machines.

Edit:

Also use VideoMode=6 instead of VideoMode=5

Edit 2:

Also found that just changing VideoMode to 6 should fix the crashing regardless of your CustomHeight and CustomWidth values.
Post edited September 24, 2015 by Saleck
Tried the above, still didn't work.
it doesn't fix the problem, i've tried (= i'm not assuming)
do you realize the logic behind the config is if you select 5 as videomode that it's the same as setting 6 as videomode & customwidth=1024 & customheight=768 (as long as there's nothing flawed inside game's code)?

avatar
Saleck: We've found a fix (Thanks Glowhyena for working with me on this)

The sshock.ini that was shipped has this setting inside it:

; Custom screen resolution
; Select the width, height and aspect
; Aspect should be set to zero for automatic calculation
; For manual aspect, set its value using the formula Height / Width * 65536
; WARNING: Resolutions higher than 1024x768 may crash the system
CustomWidth=854
CustomHeight=480
CustomAspect=0

Change this to read:

; Custom screen resolution
; Select the width, height and aspect
; Aspect should be set to zero for automatic calculation
; For manual aspect, set its value using the formula Height / Width * 65536
; WARNING: Resolutions higher than 1024x768 may crash the system
CustomWidth=1024
CustomHeight=768
CustomAspect=0

All test so far are showing this is fixing the problem on affected machines.

Edit:

Also use VideoMode=6 instead of VideoMode=5
avatar
Saleck: We've found a possible fix (Thanks Glowhyena for working with me on this)

The sshock.ini that was shipped has this setting inside it:

; Custom screen resolution
; Select the width, height and aspect
; Aspect should be set to zero for automatic calculation
; For manual aspect, set its value using the formula Height / Width * 65536
; WARNING: Resolutions higher than 1024x768 may crash the system
CustomWidth=854
CustomHeight=480
CustomAspect=0

Change this to read:

; Custom screen resolution
; Select the width, height and aspect
; Aspect should be set to zero for automatic calculation
; For manual aspect, set its value using the formula Height / Width * 65536
; WARNING: Resolutions higher than 1024x768 may crash the system
CustomWidth=1024
CustomHeight=768
CustomAspect=0

All test so far are showing this is fixing the problem on affected machines.

Edit:

Also use VideoMode=6 instead of VideoMode=5

Edit 2:

Also found that just changing VideoMode to 6 should fix the crashing regardless of your CustomHeight and CustomWidth values.
Glad to help out. Well, the game is really strange. It crashed when launched for the first time, but it didn't crash after relaunched. The game would crash after changing the video mode and custom screen resolution, but it wouldn't crash again when you try to re-launch the game.

EDITED
You shouldn't change the screen resolution bigger than 1024x768 if you do not like the unplayable choppiness.
Post edited September 24, 2015 by Glowhyena
man, since you look like somebody who's actually trying to solve this now - i very much hope you're playing with debugger right now looking at that offset and not with random shuffling of settings in sshock.ini..

avatar
Saleck: We've found a possible fix (Thanks Glowhyena for working with me on this)

The sshock.ini that was shipped has this setting inside it:

; Custom screen resolution
; Select the width, height and aspect
; Aspect should be set to zero for automatic calculation
; For manual aspect, set its value using the formula Height / Width * 65536
; WARNING: Resolutions higher than 1024x768 may crash the system
CustomWidth=854
CustomHeight=480
CustomAspect=0

Change this to read:

; Custom screen resolution
; Select the width, height and aspect
; Aspect should be set to zero for automatic calculation
; For manual aspect, set its value using the formula Height / Width * 65536
; WARNING: Resolutions higher than 1024x768 may crash the system
CustomWidth=1024
CustomHeight=768
CustomAspect=0

All test so far are showing this is fixing the problem on affected machines.

Edit:

Also use VideoMode=6 instead of VideoMode=5

Edit 2:

Also found that just changing VideoMode to 6 should fix the crashing regardless of your CustomHeight and CustomWidth values.
avatar
svatem1: also - right now, i'm doing your job for no money and i'm even paying for it, get your attitude right pls
You should exactly do this.
There may be a reason to be a bit sad but there is no reason to be rude since nobody said that they won't help you. .
low rated
i'm not rude
so far i've paid, i've helped gog owners with providing them with info about the bug, i've provided them with couple of feedback & I've warned potential customers there's problem
couple of fanboys have problem with it, i'll probably be able to live with it

avatar
svatem1: also - right now, i'm doing your job for no money and i'm even paying for it, get your attitude right pls
avatar
MarkoH01: You should exactly do this.
There may be a reason to be a bit sad but there is no reason to be rude since nobody said that they won't help you. .
avatar
voodoo47: so, does it still crash when you try to use the mouse?
Sorry for being late with the answer, actually I can use the mouse without any problem, no crash or other.
avatar
nello66: Evening, I dont know how or what happen, but I 've reinstalled the SS Enhanced version, started and after the intro i DID NOT USE the mouse to make my choise, like difficoult and etc...i use the keyboard, aftert started the game and....IT WORKS.... so strange.
avatar
Sebek: Does it work the second time you launch the game? or 3rd time?
I just re-installed the game and when lauched I used the keyboard to configure the difficulties, etc...not the mouse, start the game, and it works.
Post edited September 24, 2015 by nello66
avatar
svatem1: i'm not rude
Maybe not intentionally (translation problems) but your words are very rude. Your first post was not "please fix this error, I want to play..." it was "I am so sick of playing games not even being alpha tested". You see the difference?

avatar
svatem1: so far i've paid, i've helped gog owners with providing them with info about the bug,
Yes, you've paid and I guess everybody else who has bought the game. And you warned about the bug ... no, you didn't. You did not warn about the bug, you told everybody to not buy the game at all even if the devs are trying to fix this asap. Again - see the difference?

avatar
svatem1: couple of fanboys have problem with it, i'll probably be able to live with it
Why should any fanboy have a problem with you if you only want to help? The problem is that this is not the case. Everything you are writing is rude and everything you are demanding is ridiculous. Bugs do happen - even directly after release and even after an extreme testing phase. There is only a problem if nobody cares. And you can see that the devs are already posting in this thread (and they also said in the twitch stream that they will look into it) - so they DO care and there is no reason to announce the end of the world because of it. Boy, the game did not cost you 100$ and they are trying to fix it as I type this so just be a bit more patient.
low rated
i'm sorry to hurt your feelings
grow some skin

avatar
svatem1: i'm not rude
avatar
MarkoH01: Maybe not intentionally (translation problems) but your words are very rude. Your first post was not "please fix this error, I want to play..." it was "I am so sick of playing games not even being alpha tested". You see the difference?

avatar
svatem1: so far i've paid, i've helped gog owners with providing them with info about the bug,
avatar
MarkoH01: Yes, you've paid and I guess everybody else who has bought the game. And you warned about the bug ... no, you didn't. You did not warn about the bug, you told everybody to not buy the game at all even if the devs are trying to fix this asap. Again - see the difference?

avatar
svatem1: couple of fanboys have problem with it, i'll probably be able to live with it
avatar
MarkoH01: Why should any fanboy have a problem with you if you only want to help? The problem is that this is not the case. Everything you are writing is rude and everything you are demanding is ridiculous. Bugs do happen - even directly after release and even after an extreme testing phase. There is only a problem if nobody cares. And you can see that the devs are already posting in this thread (and they also said in the twitch stream that they will look into it) - so they DO care and there is no reason to announce the end of the world because of it. Boy, the game did not cost you 100$ and they are trying to fix it as I type this so just be a bit more patient.
avatar
svatem1: i'm sorry to hurt your feelings
grow some skin

avatar
MarkoH01: Maybe not intentionally (translation problems) but your words are very rude. Your first post was not "please fix this error, I want to play..." it was "I am so sick of playing games not even being alpha tested". You see the difference?

Yes, you've paid and I guess everybody else who has bought the game. And you warned about the bug ... no, you didn't. You did not warn about the bug, you told everybody to not buy the game at all even if the devs are trying to fix this asap. Again - see the difference?

Why should any fanboy have a problem with you if you only want to help? The problem is that this is not the case. Everything you are writing is rude and everything you are demanding is ridiculous. Bugs do happen - even directly after release and even after an extreme testing phase. There is only a problem if nobody cares. And you can see that the devs are already posting in this thread (and they also said in the twitch stream that they will look into it) - so they DO care and there is no reason to announce the end of the world because of it. Boy, the game did not cost you 100$ and they are trying to fix it as I type this so just be a bit more patient.
avatar
svatem1:
And right back to being rude again.
avatar
Saleck: We've found a possible fix (Thanks Glowhyena for working with me on this)

The sshock.ini that was shipped has this setting inside it:

; Custom screen resolution
; Select the width, height and aspect
; Aspect should be set to zero for automatic calculation
; For manual aspect, set its value using the formula Height / Width * 65536
; WARNING: Resolutions higher than 1024x768 may crash the system
CustomWidth=854
CustomHeight=480
CustomAspect=0

Change this to read:

; Custom screen resolution
; Select the width, height and aspect
; Aspect should be set to zero for automatic calculation
; For manual aspect, set its value using the formula Height / Width * 65536
; WARNING: Resolutions higher than 1024x768 may crash the system
CustomWidth=1024
CustomHeight=768
CustomAspect=0

All test so far are showing this is fixing the problem on affected machines.

Edit:

Also use VideoMode=6 instead of VideoMode=5

Edit 2:

Also found that just changing VideoMode to 6 should fix the crashing regardless of your CustomHeight and CustomWidth values.
Holy shit, it actually works, at least for now! :-D