SS2Tool v6 Beta Test

[6740602d66af8voodoo47]

it starts, allows me to select options, and when going to the actual patching process, displays this;

[6740602d66cc9Kolya]

Ah oh! Okay, that old version you mean. Yeah well, that was merely a test whether the sync works. It didn't have any of the features of the current release. Unless it actually downloads something you cannot be sure if it connects, because it doesn't even try to download version.txt at the start. It didn't have that feature either. That's why it had an expire date. Throw it away, it's useless.

[6740602d66de1Kolya]

The fact that 5.1 works for you is what's really surprising me. I just checked and it's the same code for version.txt in 6.0.
I'll create a test build tomorrow that does nothing but that part. Off to bed now.

[6740602d66f07Kolya]

So far I haven't been able to figure out the problem that's causing the connection to fail on voodoo's machine.
I would really appreciate more testers, especially if they happen to run into the same problem.
Updated version is in the first post.

[6740602d66ff5krist2]

Just tested the new tool on a clean copy from a CD. No problems updating and installing. Haven't tried with any mods or FM's so far.

[6740602d67107Yankee Clipper]

I just tested the tool with a clean SS2 install (GOG) on an XP machine. No problems. My firewall threw up multiple permission requests during the install, but no glitches. One thing I did notice is that it installed a slightly older version of Blue Mod Manager - 1.09 vs the 1.10 that I was using before. I just replaced it, but thought you should know. Tested with mods and FM, all good.

[6740602d6727bDenhonator]

Installed on clean Steam version on Windows 8.1 no problems or prompt windows at all, and ticked all the boxes (except safe mode/shortcuts). I have UAC disabled though. It even fixed SS2 crashing when switching to 1920x1080 for the first time, which the previous SS2Tool hasn't done for me

[6740602d67428voodoo47]

chrome: "SS2Tool-BETA-v.6.0.0.1.exe is not commonly downloaded and could be dangerous."
me: "just you wait a week or two ya little pest."

after selecting "update", I was allowed to go back and choose again, picked "clean install", went back, but wasn't allowed to choose between the two options anymore. also, blending explosions should definitely be enabled by default, this prevents some major ugliness from happening.

also;

Code: [Select]

SS2Tool 6.0.0.1
SS2ToolVersion: Latest version
CRF: 17/307700
MIS: 53/195078
Checksum error [34b3d1ff4dad7cef16ab5a5f5fc61eed]
Not a valid game. No changes were made.
If you think this is a mistake, post this log to systemshock.org.
Creating log file
when trying to patch up a ss2tool 5.1 install (manually updated to 2.43). it's a fully working install. currently on a win7 netbook, mobile connection.

[6740602d6752dKolya]

I don't think being able to go back and forth at this point is critical but if it's an easy fix I'll do it.
Acknowledging the blending explosions and Blue Mod Manager 1.10. And I'll see into the validation issue.

//Updated Blue Mod Manager in the master build

[6740602d6764dvoodoo47]

it's a behavior inconsistency (when selecting update, you are allowed to go back and reselect, but not when selecting clean install), so it should be fixed if possible.

also, the blending explosions are pretty much a bugfix, so I would just enable it and not expose it as configurable. there is no sane reason why anyone would want to NOT have the fix enabled.

[6740602d679c6Kolya]

when trying to patch up a ss2tool 5.1 install (manually updated to 2.43). it's a fully working install. currently on a win7 netbook, mobile connection.

It would seem that your game is missing all the cutscenes?

[6740602d67acfvoodoo47]

ah, correct. it's a "dev" install, getting rid of cutscenes spares me a click or two here and there. anyway, a warning would be enough, with an option to continue anyway - not having cutscenes might be a deliberate choice.

[6740602d67cb0Yankee Clipper]

I just used the update feature of the tool and I have a few minor criticisms (constructive, I hope).

1. The tool requires me to browse again to my SS2 folder. I can see how this would be necessary on first use, but couldn't it retain that location for future use? Also, other options such as Enable Weather Effects and so on. Once I have checked those boxes the first time, it would be great if the tool remembered my choices for future updates. I like that I still have the ability to change those choices in the future, but it would be preferable if it had my previous choices preselected in the future.
2. Although I had the latest version of BMM, after running the tool, my configuration choices in BMM were wiped out and I had to redo them all. Why clear the configuration file for BMM if it is already up to date?
3. Same deal with ShockEd. I already had the latest version, but the configuration file was reset to its original state.
4. DML files in the root directory. For some reason, there are more recent .dml files in the misdml subdirectory, but older ones in the root directory.  I make a habit of deleting those redundant files from the root, but the tool puts them right back in. What is the point of those useless files, and does the tool need to make sure that they are there?
5. cam.cfg: My dml logging lines are getting wiped out as this configuration file gets restored to its new state.
6. Keyboard bindings are getting wiped out. Again, on an update, especially on one where the game files are already up to date, there is no reason to reset the key bindings.

[6740602d6800aKolya]

ah, correct. it's a "dev" install, getting rid of cutscenes spares me a click or two here and there. anyway, a warning would be enough, with an option to continue anyway - not having cutscenes might be a deliberate choice.

Validation does two things: Ensure that we're on the sunny side of the law AND that our little server doesn't get crushed by people dowloading huge amounts of data. If I let missing videos pass with only a warning, then next thing the synchronisation will download the cutscenes from the master build. Having cutscenes in the sync is useful in certain cases. Short version: I won't write an exception for that special minority who delete their cutscenes deliberately. Partly because I have no way of knowing if it was deliberate.

@Yankee Clipper
1. Drop SS2Tool into your game folder. Run it there and it will know the game location. Leave it there for future updates.
2. It looks like SS2BMM doesn't store mod active status in it's configuration but reads it directly from cam_mod.ini. That will indeed get overwritten and mod active status will be lost. SS2BMM's other settings remain.
3. Did you choose the option to install shocked? Which config file are we talking about?
4. Interesting. There's a bunch of DMLs in the master build root. I'm not sure why. Pretty sure these should go. Voodoo?
command2.mis.dml
earth.mis.dml
hydro1.mis.dml
hydro2.mis.dml
station.mis.dml
5. cam.cfg indeed gets synced and previous settings in there will be overwritten.
6. Keybinds should not be reset on an update. But I forgot to exempt user.bnd. Thanks for the heads up. Changed now.

Also remember that all changed/removed files can be found in the folder SS2ToolSyncBackup.

[6740602d683d8voodoo47]

yeah, if the new set of dmls still resides in the misdml folder as before (can't check, as I did not manage to fully patch a SS2 install with 6.0 yet for one reason or another, heh), the old dml set from the root needs to go - if they are left there, they will prevent the new ones from loading, so this is important.

Short version: I won't write an exception for that special minority who delete their cutscenes deliberately. Partly because I have no way of knowing if it was deliberate.

fair enough, but do make it bail with some humanly understandable message, like "cutscenes missing, reinstall" or something.

[6740602d6855aYankee Clipper]

1. OK, dropping the tool in the game directory allows it to find the game files unassisted, but it still doesn't remember the other choices like Enable Weather Effects.
2. ? Were you talking about my 2 in your 2?
3. Yes, I chose the options to install BMM & ShockEd even though I knew both were already up to date. My point is that those features would be much more handy to use if they could be used even if I don't know one way or another if there is a new update available. The tool should check my version against the latest. If a new update available, it updates. If I am already up to date, instead of wiping out my configuration files, it just leaves them alone. I see the tool doing version checking of other files, so why not with those as well?
4.
5.
6. No, it is not working as designed. I just redid everything: clean install, configure, update. I made sure that the Reset keybinds was unchecked during the update. No matter. They got wiped.

[6740602d68829Kolya]

1. That is correct.
2. Yes.
3. I have no way of checking what your local version of SS2BMM or anything else is. I can check if a file is different/non existent and then (over)write it. That's how it works. It doesn't wipe out the SS2BMM config files, see my comments above.
6. See my comments above.

but do make it bail with some humanly understandable message, like "cutscenes missing, reinstall" or something.

The message to post their log here if they think it's an error was well considered. Divulging how exactly validation fails would open it up to manipulation. Don't worry, it won't happen too often. (Famous last words, eh?)

[6740602d68909voodoo47]

just "reinstall" maybe then?

[6740602d68a6bYankee Clipper]

Sneaky! You're editing your previous reply, so it makes my later reply look confused.

2. It looks like what is happening is that on the first time that the update is used, if it is selected, BMM gets reinstalled, different or not. The active mods are stored in ss2bmm.log, so when that gets overwritten, the info is lost. However, running update a 2nd time does not cause this to happen. I'm not sure why, but if you select BMM during the initial install, the first update doesn't know that it was already installed, but the 2nd update does.
3. User.cfg is where the screen size for ShockEd is stored.
5. How come? Why update a config file if there is no change in the game files? Sure, if there is an update to New Dark and the config files are changing, it makes sense, but why wipe out configurations on an update where the relevant files are already up to date?
6. Cool!

[6740602d68b55Kolya]

No, I'm not editing my post to make you look any way. When I started editing it you hadn't replied yet.
I edited it because I found out stuff and my post was the last in the thread.

[6740602d68c33Yankee Clipper]

I did not mean to imply that you were motivated by a desire to make me look confused. I was merely stating that the edits had that effect.

[6740602d68dfdKolya]

Understood.

2. Unfortunately active mods are NOT stored in ss2bmm.log. These config files are never touched by SS2Tool: ss2bmm.cfg, ss2bmm.log. Try changing your cam_mod.ini and you will see active mod status change.
3. User.cfg is exempt from sync. But if you reinstall shocked it will be overwritten.
5. What "Update" means in SS2Tool: All files are synchronised with the master build, except those in the exclusion list (SS2ToolExcludeSync). After updating you have an up to date game, but it doesn't take into account your deliberate changes to files (except those in the exclusion list). It just copies over files if they are different locally than in the master. Unlike "Clean Install" the "Update" option does not delete local files that don't exist in the master.

[6740602d68f4evoodoo47]

hmm.. leaving cam_mod.ini alone if BMM is detected might be a good idea.

[6740602d6905eKolya]

I'm not sure if this exception would make sense in all cases. There's a lot you can screw up in cam_mod.ini even if you have BMM. And SS2Tool's goal is to make sure your game works.
Furthermore I don't think resetting the active status of your mods is a big deal. And I do think SS2BMM should use it's own config files to store that active status. Maybe.