SS2Tool questions

[665c0de4875f5Kolya]

I can only tell you that I experienced dozens of cases where any kind of compatibility mode would keep the game from running. Even with the same symptoms you describe. And while I understand that in your case the game won't even start in normal mode, it's not like the compatibility mode fixed it for you either.

As for the black screen problem: I don't have a solution for you. Sorry to say. Try to tinker a bit yourself and watch the threads I linked above.
I don't have that crash so I can't test anything. But if any of you comes up with a solution I'll happily put it in the Technical FAQ thread.

[665c0de48779bJenza]

oh... I need DDfix aswell, Right il report back with my results after i get DDfix!

[665c0de4878b1Jenza]

didnt Solve

[665c0de487a79Kolya]

Updated to version 2.5

Changes:
- changed "Hyper Threading fix" description -> "MultiCore Processor Fix"
- Improved install.cfg file for finding resources more reliably (resname_base .\+.\RES)
- DirectPlay8 wrapper by Tos included
- Copies/Replaces user.bnd/user2.bnd (fixes quicksave overwriting and broken use/shoot mode problem)
- Includes Widescreen Mod by Weak-ling
- Includes DDfix by Timeslip

[665c0de487bbbmiracle.flame]

very sweet )

[665c0de487e9cMarvin]

So Tos' wrapper, the widescreen mod and the DDfix are automatically installed with predefined settings? Maybe you could make it possible for the user to type in the desired resolution (DDfix, widescreen mod), thus applying the correct settings.

[665c0de487f78Kolya]

Have you used the SS2Tool, Marv?

[665c0de488175Kolya]

I noticed two problems during testing (well actually I wanted to play secmod but anyway).

1. While the SS2Tool copies over a perfectly working user2.bnd to remedy the broken use/shoot mode problem, the game screws up this file entry again on first start. I will probably have to edit the default keybinds, in hopes that's where the game pulls its changes from.

2. For some reason the DDfix GUI doesn't write the resolution to cam.cfg on a fresh game and therefor leaves the game hanging after the first load screen. The game writes out 640 480 then but that of course doesn't work in most cases. On DDfix's next startup it complains about the mismatching resolutions and THEN it rewrites it.
Edit:
Okay, I know what's happening here: DDfix assumes there is a resolution line in cam.cfg to start with.
But on a freshly installed ORIGINAL game there is no resolution line in cam.cfg that could be replaced! (Unlike the HOTU version.) So DDfix never rewrites the line.
That's easy to fix though: I'll just write some resolution to cam.cfg myself which ddfix can change later.
On a sidenote: the Widescreen mod does exactly the same.

[665c0de488351Kolya]

Updated to version 2.6

As indicated above there were a few problems, so this is a bug-fix release.

- DDfix and the Widescreen Mod now work on a freshly installed original SS2 game.
- The Widescreen Mod used to throw an error on first use because of a missing log file. This is fixed now.
- ALL keybind files the game ships with + user.bnd and user2.bnd are now fixed against quicksave overwriting and the broken use/shoot mode problem. Additional save/reload keys are Insert and Delete. Changing keybinds may still screw the use/shoot mode but I haven't managed to produce that yet. In any case it works from the start now.

[665c0de488608Marvin]

Have you used the SS2Tool, Marv?

Nope, not the new version at least. Why? Does it already have that option?

[665c0de48880aKolya]

The implementation of the Widescreen Mod and DDfix is simple. The SS2Tool copies over the necessary files and starts the according GUI to let you choose the resolution etc. It does one thing better than these fixes: It can deal with a situation where no resolution has been set before, like in a new original installation.

[665c0de488af8Marvin]

The implementation of the Widescreen Mod and DDfix is simple. The SS2Tool copies over the necessary files and starts the according GUI to let you choose the resolution etc. It does one thing better than these fixes: It can deal with a situation where no resolution has been set before, like in a new original installation.

Should have tried that damn thing before posting ...

Righty right then.

[665c0de488bedPolo]

I too am having the black screen problem Jenzu had, after installing and trying everything.

[665c0de488cb7Kolya]

You're using the latest version?

[665c0de488f53Marvin]

I too am having the black screen problem Jenzu had, after installing and trying everything.

Strange, a friend of mine reports the exact same problem (SS2-Tool 2.6, Athlon 3200+, GeForce 7800 GS Forceware 169.04 ).

€dit: He seems to have solved it by starting shock2.exe with -lgntforce. That's the second time I noticed this to work.

[665c0de4890a6Koksa]

Hi!
I got the game / videos working just great, but i got a different problem.
Whenever in the game i use my inventory and try to move objects in there, the character only hits with his wrench.
Its impossible to move or read any logs while in game. Its like the inventory is responding to my commands but things in it are not.

Have anyone else experienced issues like these?

[665c0de489197miracle.flame]

yes, many

[665c0de4892deKolya]

Haha, the broken use/shoot mode problem really is rather common. I'd hoped to fix it with this version of the SS2Tool but maybe you changed your keybinds lateron?

[665c0de4893c2Barbach]

I had this problem recently, I'll try to reinstall and check if it's fixed or not

[665c0de48951bneoendedsmith]

Koyla, I had some problems with "Shadow Dithering" and after applying the latest DDFix v.1.3.11 (after 4 hours of trouble-shooting) it was finally fixed...can you apply the latest DDFix to your wonderful SS2Tool whenever is convenient for you.  I'd hate to think others out there are having the same problems as I was but don't know how to fix it...

BTW, my system config is:
-XP SP3 32-Bit
-NVIDIA GeForce 8700M GT and v.175.32 Drivers

Thank you for everything you've done for us Koyla!!

[665c0de4896ddKolya]

The SS2Tool is using the latest version of DDFix (1.3.11).
I just did a file by file comparison, it's still exactly the same as the latest that can be downloaded from Timeslip's site.
The SS2Tool simply copies these files to your game directory and then starts the DDFix GUI. Not much could go wrong with this I think.
Did you use the exact same settings each time?

[665c0de489a95neoendedsmith]

The SS2Tool is using the latest version of DDFix (1.3.11).
I just did a file by file comparison, it's still exactly the same as the latest that can be downloaded from Timeslip's site.
The SS2Tool simply copies these files to your game directory and then starts the DDFix GUI. Not much could go wrong with this I think.
Did you use the exact same settings each time?

The GUI won't ever work for me since I don't have .NET Framework installed...but I just got it working using the "Manual" method from "TimeSlip's" readme file.  I just found all this out...and now I know why it didn't install DDFix for me...there's no post that informs anyone that they should have .NET v.2.0 installed before they run SS2Tool v.2.6 in order to install the DDFix GUI automatically...the DarkWidescreen mod also didn't install automatically for me, so I did that manually also.  I'm sorry I confused you...and thanks for getting back to me.  Could you include .NET v.2.0 information in the main post so that people will know this from now on?

Thank you Koyla.

[665c0de489bc0Kolya]

The info that you need NET 2.0 has been there all the time, right next to the point "DDfix", in the first post.
I guess I could add it to the description in the installer as well.

[665c0de489ea3neoendedsmith]

The info that you need NET 2.0 has been there all the time, right next to the point "DDfix", in the first post.
I guess I could add it to the description in the installer as well.

I apologize Koyla, I see the note about .NET now...I ALWAYS strive to read any and all documentation so that I don't waste the time of website admins or techs with anything I do, and I missed it.  I just started playing System Shock 2 again (the first time on XP) and I've read just about every post on this whole forum so that I don't waste anyone's time.

May I suggest that a "description in the installer" might be useful for someone who accidentally overlooks important info, as I did.  Only "IMHO" though.

Thank you as always Koyla.