[REL] patSH3r V1.1.0
 

patSH3r changes the way Silent Hunter III works by bringing new functionallity to the game. It uses a technique called code injection, which adds/replaces code in live memory while running the game. Thus it doesn't make modifications to any of the original game files. When the files belonging to this project are removed, the game is left as nothing ever happened.

While playing SH3 for some time now. I've been missing a major part of the game, where I wished that the crew actually made a difference. To day they don't. At least not to the extent I want it anyway. So that is where the main focus of the patSH3r project will be. ...to start with.



FEATURES:

• Crew rotation

This patch apply a auto rotation feature to the crew, so you don't have to manage them in such detail as in the original. This method is still quite simple and needs development, but it works just fine for the purpose.

• Range estimation fix

This fix is a further developed version of h.sies V15D range estimation fix, (thanks for the info h.sie). It makes the respective officers qualification (watch/helms), experience and endurance influence the results of range estimations.

INSTALLATION:

Unzip the downloaded file and copy the two files (patSH3r.act & patSH3r.cfg) to the directory where your SH3 installations resides.
Open the patSH3r.cfg-file with notepad and change the values (enable/disable) the features as you wish.
Next time you start the game, the changes will apply.

CHANGELOG:

Get your copy here.

Best wishes

/FB

So.... what does this do??:06:

Yes, that´s a very good question....:06:

I don´t understand the MOD from Fader_Berg too :o ! What must I do with them and what do the MOD with the game ??? :hmmm:

Please Fader_Berg, can you clearify us ? :D

Best regards,
Magic

If the range estimation fix is enabled in the config file, the range estimations done by the watch- and weapons officers will suffer in presicion depending on three variables. Their qualification, experience and their endurance.

An unqualified, exhausted and/or unexperienced officer will more likely make errors in hes estimations.

Unzip the downloaded file and copy the two files (patSH3r.act & patSH3r.cfg) to the directory where your SH3 installations resides. Open the patSH3r.cfg-file (with notepad) and change the value for range_estimation from off to on if you want to enable this feature.

When you've done that, the changes will apply the next time you start the game.

Hi !

Aaaah, okay, now I understand !!! :yeah:

Can I do this with the other fixes from h.sie too (I use his V15D Patch) ?

I mean, I want for example, that the persiscope don´t move down automatically. Is this with your MOD possible ?

Is this then the right entry in your .cfg File ? :hmmm:
hsie_periscope off

Best regards,
Magic

Yes. If you have 'manage_hsie_fixes' enabled.

Thank you
 

Thank you very much for your work.:up:

However, I have a couple of questions for you:

1. How much erroneus can be an estimation -maximum %- and how much exact can be in the best case -1, 10, 100 meters precision-?

2. I can see in your download server: sh3rr-patch.tar.bz2 with the remark:

SH3 Refresh Rate Patch - removes SH3's 50Hz refresh rate request at startup

If I apply that, what (good) will happen exactly?

Thank you again for sharing your work with us. :yeah:

:salute:

Congratulations. Not tested yet, but it seems you finally got it to work and it could make peoples life easier.

Could you provide me the information (source code) how you got the crew qualification, endurance and so on, because I'll also need these parameters for a future fix (crash dive fails depending on crew qualification)?

Thanks,
h.sie

At best (all times) = ±50m.
Worst:

< 2000: ±100m
2000 - 4000: ±200m
4000 - 9000: ±500m
9000 - 12000: ±1000m
> 12000: ±2000m

It's only ment for linux-users having problems to run SH3 under wine in fullscreen.

Thank you very much for answering.

I wait with big interest your next "deep-tweak".

:salute:

A great idea and fix, thanks!

I suggest you add the link to h.sie's "Realistic Repair- and Flooding Times (and more!)" thread:

http://www.subsim.com/radioroom/showthread.php?t=174225

Since this does some hacking of the Sh3.exe. (as far as I've read not definitively, but only at runtime) I'm sure alot of people like to know the details about it before they apply it.

Good points...

Thanks for Reply !

Sorry for my further dumb question, but can you please tell me whether these are the right entries is for my wish with the periscope:
This now looks like my File:


# patSH3r config
# h.sie fixes
#
# If you run a sh3.exe that have been patched by h.sie's V15D patch, you can
# enable and disable those fixes here. Uncomment these lines below.
#
#manage_hsie_fixes yes
#hsie_repair_time on; Repear time fix
#hsie_wo_estimation on; WO range estimation inaccuracy fix
#hsie_wp_estimation on; WP range estimation inaccuracy fix
#hsie_co2 on; CO2 calculation / dive time fix
#hsie_snorkel on; Snorkel speed fix
#hsie_periscope on; Periscope speed fix
#hsie_hydrophone on; Hydrophone fix
# range_estimatmation
#
# This patch gives more realistic range estimates by the WO and WP. The result
# is influenced by their qualification (watch/helms), experience and endurance.
# (Will overide V15D WO & WP estimation fixes if enabled)
#
# This patch is based on the range estimation patch by h.sie (thanks).
#
range_estimation off
manage_hsie_fixes yes
hsie_periscope off


Is this so correct ? Or must the File looks like this:

# patSH3r config
# h.sie fixes
#
# If you run a sh3.exe that have been patched by h.sie's V15D patch, you can
# enable and disable those fixes here. Uncomment these lines below.
#
manage_hsie_fixes yes
#hsie_repair_time on; Repear time fix
#hsie_wo_estimation on; WO range estimation inaccuracy fix
#hsie_wp_estimation on; WP range estimation inaccuracy fix
#hsie_co2 on; CO2 calculation / dive time fix
#hsie_snorkel on; Snorkel speed fix
hsie_periscope off; Periscope speed fix
#hsie_hydrophone on; Hydrophone fix
# range_estimatmation
#
# This patch gives more realistic range estimates by the WO and WP. The result
# is influenced by their qualification (watch/helms), experience and endurance.
# (Will overide V15D WO & WP estimation fixes if enabled)
#
# This patch is based on the range estimation patch by h.sie (thanks).
#
range_estimation off

The difference between the both Variants is, in the first version I added new entries below, just in the second variant I only removed the # and change from "on" to "off"!

What is now correct ? :oops:

Thank you very much for help,

Magic:salute:

They are both right.