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

×
it's an assessment based on available data and years of experience.

avatar
svatem1: not much thinking needed to see this though..
yeaah that's part of your problem. anyway, as you do not own the software anymore, you have no reason to post in a support topic, so do everyone a favor, and just.. go away.


steering this back on track - last few people with the crashing problem, please post your event logs and dxgiag exports, see here. the more info is available, the better the chance of finding the bug and fixing it.
Post edited September 23, 2015 by voodoo47
low rated
another way to say "it's true because i say so"..
now let's return to where it all begun (search fot that post): https://en.wikipedia.org/wiki/Software_testing#Alpha_testing
and let's state this: assesment based on available data and years of my experience tells me this hasn't gone through alpha
so we shared our feelings..
thx again for your care, i'll again do as i will since till the money are back in my wallet, this is still my problem

avatar
voodoo47: it's an assessment based on available data and years of experience.

avatar
svatem1: not much thinking needed to see this though..
avatar
voodoo47: yeaah that's part of your problem. anyway, as you do not own the software anymore, you have no reason to post in a support topic, so do everyone a favor, and just.. go away.

steering this back on track - last few people with the crashing problem, please post your event logs and dxgiag exports, see here. the more info is available, the better the chance of finding the bug and fixing it.
Post edited September 23, 2015 by svatem1
Crashes for me too. Will upload the dxdiag exports as soon as i get home.
don't forget the event log, it's equally important (maybe more).
First of all, a HUGE + to you Voodoo47 for trying to help even if someone throws shit at you.
Secondly, I've tried to mess with all the settings in the sshock.ini with no results, also compatibility settings are a no-go for me.
First time running the game - everything works smoothly but the second time you launch the game, it instantly crashes.
I've tried to look into this and I'm not sure but it seems (at least in my case) that running the game modifys some necessary files or at least generates something that clashes with the game or it just could be my PC messing with me since I'm running multiple background programs. I'm currently programming random fixes in hopes of finding the problem. Sorry for my stupid looking english :F
been in this businesses for almost two decades now, so I'm used to this, not really caring anymore. and I've seen (much) worse.

odd thing you have happening there, but anyway, if it hard crashes, you should be able to get the event log and dxdiag export - post them here, they will be helpful when trying to find and fix the bug. see here.
I'm suffering the same issues, here is my DxDiag report.

http://pastebin.com/KKVSTgB6
Is anyone that is having this issue NOT using an ATI graphics card?
avatar
Merlin8000: Is anyone that is having this issue NOT using an ATI graphics card?
Turning off Xfire helped and it doesn't crash anymore.
avatar
Merlin8000: Is anyone that is having this issue NOT using an ATI graphics card?
It shows up with NVIDIA Cards, too.
This is getting rather absurd, I've tried tons of possible fixes with no outcome :-D
this is literally a system shock.
6 cans of energy drink down, ima gonna get you mofo >:I
have you tried plugging in debugger and checking that offset you get in dump? (most of these crashes have the exact same one, i think i've seen 1 different)

avatar
Sebek: This is getting rather absurd, I've tried tons of possible fixes with no outcome :-D
this is literally a system shock.
6 cans of energy drink down, ima gonna get you mofo >:I
My proposal to fix it: uninstall completly, reinstall and wait(!) until it is really installed. Of course only in Galaxy
I believe if you press Play (or whatever it is in your local language) too early, you run into trouble.

IMHO it has -directly AFTER the installation - nothing to do with Ini settings in any of both config files.

At least this resolved the issue for me.
low rated
you're joking, right..
how exactly does one perform "wait until it is really installed"?

avatar
Grunzi: My proposal to fix it: uninstall completly, reinstall and wait(!) until it is really installed. Of course only in Galaxy
I believe if you press Play (or whatever it is in your local language) too early, you run into trouble.

IMHO it has -directly AFTER the installation - nothing to do with Ini settings in any of both config files.

At least this resolved the issue for me.
Post edited September 23, 2015 by svatem1
avatar
svatem1: you're joking, right..
how exactly does one perform "wait until it is really installed"?

avatar
Grunzi: My proposal to fix it: uninstall completly, reinstall and wait(!) until it is really installed. Of course only in Galaxy
I believe if you press Play (or whatever it is in your local language) too early, you run into trouble.

IMHO it has -directly AFTER the installation - nothing to do with Ini settings in any of both config files.

At least this resolved the issue for me.
avatar
svatem1:
No joke ...

first time I tried it after the "Play" button was available (again; Galaxy..) No success, same error as the thread starter.
Played around with the Ini files - nothing. Evn not starting it manually, playing around with compatibility settings ... nothing
Uninstalled the game - waited some seconds and played then - everything fine.
Sorry, can't explain it but this was my experience.