Originally Posted by Stiebler (Post 1656388)

...you have a variant of SH3.exe which cannot be patched because it is non-standard for some reason. Perhaps it has Starforce present, perhaps it was downloaded from Steam, perhaps some other irregular source...

Originally Posted by Stiebler (Post 1656388)

Thanks for all the useful information, everyone, and especially to Frau Kaleun.

@Salvoradeno:
It makes no difference at all to patching SH3.exe however many mods you may or may not have installed.

Just copy your SH3.exe into a separate folder and apply the patch kit, following the instructions provided (place patchkit and *copy* of SH3.exe into the same temporary folder).

If the patchkit says it has worked, then use the Options Selector (part of the patch kit) to decide which options you want active. If you use NYGM you must toggle OFF the realistic repairs option. Then copy the patched SH3.exe into your main SilentHunteriii folder. Or, much better, create a separate folder for the patched SH3.exe, then install it with JSGME as Frau Kaleun described above.


If the patchkit advises you that the patch has failed, then it has found a false checksum value. In other words you have a variant of SH3.exe which cannot be patched because it is non-standard for some reason. Perhaps it has Starforce present, perhaps it was downloaded from Steam, perhaps some other irregular source. In particular, any copy of SH3.exe which you have already successfully patched will NOT be accepted by the patch-kit. You must start with a clean version of commercial SH3.exe with patch 1.4b pre-added by the manufacturer and without any copy protection. In the event of any of these failures, you need to obtain a version of SH3.exe which lacks these problems. Any modern copy (purchased 2008 or later) of Ubisoft's SH3.exe in a DVD wrapping should be acceptable to the patch kit.

However, I know that H.se has been attempting to provide a patch-kit suitable for an extended set of versions of SH3.exe, and this may be the final route we take.

It is very important to understand that the patchkit places modified code into exact places of the SH3.exe file. If the file is non-standard, the patch-code will go into the wrong places with uncertain results - a euphemism for a probable CTD (or worse). That is why we have to be so careful with the check-sums to verify that you have the correct version of SH3.exe for patching.

Stiebler.


Stiebler.

Originally Posted by Stiebler (Post 1657134)

@SquareSteelBar:
Good point. Thanks.:up:

@Salvadoreno:
The destroyer circling long after it has run out of depth-charges is a well known 'feature' of SH3, and is not connected to the SH3.exe patch. One could argue that it keeps the U-boat submerged and slow, while the convoy escapes.

This feature is particularly prominent with GWX, because its AI sensors have been set to be too sensitive. However, if the destroyer has run out of depth-charges, then reload your torpedoes, rise to periscope depth, and sink it.

Stiebler.

Originally Posted by Stiebler (Post 1658034)

@Tekai:

As Frau Kaleun says, any recent version of SH3 on DVD should be suitable.

Most of the problems concerning H.sie's patch-kit, and my adaption of it, seem to be caused by versions of SH3 downloaded off the Internet (including legitimate, paid downloads) and by the original Starforce-protected version of SH3.

Please note that use of the Starforce removal tool removes Starforce from your computer, and maybe even from your old copy of SH3.exe, but the SH3.exe file must still contain a lot of data where Starforce once resided. Thus the checksum tests of the patch-kits will not function.

Stiebler.