Stiebler3A_Addon_for_V16B1 (Released)

[Stiebler]

Stiebler3A_Addon_for_V16B1.

This patch is now available from my signature below (item (9) in the menu list). Full instructions are included with the patch, so I summarise briefly here:

1. The patch is a hard-code fix that can be applied ONLY to a legitimate copy of SH3.exe that has already been patched with H.sie’s V1.6B1 patch. The Stiebler3A Addon provides extra functions.

2. This patch can be used with stock SH3 and ALL of the main super-mods (including NYGM and GWX), provided that it is installed correctly.

3. The Stiebler3A_Addon_patch contains these mods supplementary to H.sie's original V16B1 patch:
a) Silent-running mod
b) Surrender mod
c) "Smoke on Horizon" mod
d) CAM-ship mod
e) Asdic in shallow waters mod
f) Reduce ship warnings mod
g) Change patrol grid mod
h) Minimum TC mod
i) Improved BdU Congratulations mod
j) Weather improvement mod (NYGM patttern, but self-contained and can be used with any other super-mod or stock SH3, provided H.sie's V16B1 is already installed).

Most of the above mods will be familar to those who have previously installed my 'Stiebler2_Addon_for_V16A3' patch, but there is one important new addition:

The 'Minimum TC' mod (item (h) above) will force the game to play at a *minimum* time compression (TC) of 128, while in map mode. I designed this because I became tired of waiting for 'ship sighted' or 'ship detected' repeated 10 or 20 times as a large convoy came close, and TC dropped to 1 or 8 (default settings). But actually, this mod can be very useful in other ways too. For example, to sail easily through the Kiel canal, to depart quickly from the bases of Bergen and Lorient, to rise up quickly off the sea-bed. Whenever you get tired of waiting for something to happen, just activate the MinimumTC mod, and everything will advance at TC=128. Of course, there are also dangers.... For example, if an aircraft suddenly attacks. Use with caution.

There is also a new version (1.6) of the Options Selector supplied with the patch, so that users can toggle on and off those fixes that they prefer. This new Options Selector will not (I hope) cause the same problems as its predecessor 1.5 with non-standard installations of SH3.exe.

Finally, I wish to give my warm thanks to SquareSteelBar, who very kindly tested a preliminary version of this patch, and made many useful suggestions (that is why it is the _3A patch, not the _3 patch!).

Also I wish to acknowledge publicly all the generous help and support I have received from H.sie, the originator of the V16B1 patch (and many previous patches), and who has deservedly been awarded recently the 2011 modders' crown by SubSim for his ground-breaking work in creating new patches in hard code for our favourite U-boat simulation. Congratulations and special thanks to H.sie.

Stiebler.

[bigboywooly]

Nice one
Downloading now :yeah:

[Obltn Strand]

and I just left port:damn::wah:

but thanks for the update

[Wiking]

Thank you :up:

[erikdell]

I was looking forward for this one! :yeah: Amazing job! Thank you!
:salute:

[Borgneface]

Hello Stiebler,

I am glad i decided to check for anything new here!! I was going to leave port this evening for a fresh new campaign...so I will delay sailing time to be able to explore your addon..:yeah:

Merci

[Sepp von Ch.]

Thank you very much Stiebler!

[Victor Schutze]

I am happy I am still in port.

I'll make a nice mod soup and sail away. :haha:

Thank you Stiebler. :yeah:

[reaper7]

Excellent, that minimum TC will be very handy :up:

[erikdell]

Stiebler. I'm having problems to start a patrol on 1944. I started a thread in the SH3 forum. When i have the addon enabled i can't start the patrol. I don't know what i did wrong. This is the link http://www.subsim.com/radioroom/showpost.php?p=1853791&postcount=14. Excuse me for posting in two places but i didn't know it was this addon till i tested the mods one by one.
Thank you.

[Stiebler]

@Erikdell:

I've read your whole thread in the sh3 main group.

You reported difficulty with loading your first patrol with a mod list that at first did not include my Stiebler3 addon. Also, it seems that the CTD occurred on your first patrol of a new career, so the date 1944 is probably not relevant.

It is also not clear from your mod-list whether you have actually patched your copy of SH3.exe, first with Hsie's V16B1 patch, then with my Stiebler3_addon patch. If you have simply added our two ADDON folders without patching SH3.exe first, then you are certain to get CTDs.

If you HAVE made the two patches to sh3.exe, then try uninstalling all other added mods installed with JSGME, except those supplied by H.sie and by me. Report what happens then.

Stiebler.

[erikdell]

Acknowledged! :salute:

[Jinmei]

Hello everyone!

This error message appears at me: xd3 Invalid Input.
It sh3.exe does not create it,I did anything,everything it wrote down I did it on his basis.

[rik007]

Stiebler,

Great one. Curious about "Asdic in shallow waters mod". Just enabled it so...

By the way: are you able to solve the bug where you shouldnot increase TC 256 as airplanes will not spot you anymore? Would make you a hero.

Thanks anyhow for your excellent effort.

Rik

[erikdell]

Stiebler, i disabled all the mods and then enable only hsie's and your addon but the game still crashes. I can make the install process of hsie's and your addon again with all the others mods disabled and see if the previous modifications of the others mods on the menu, command, menu1024 are the ones which generates the problem when i install the suplement and the addon. I'm telling this cause i take the menu, commands and menu1024x768 from the sh3 directory once i have all the other mods enabled. I don't modify sh3's files directly, the same for the suplement mod.

Sorry if i don't make myself clear my english is quite limited! hehe :salute:
----
edit: to clarify about the 1944 date. when i start a career on 1939 i have no problems and it works perfectly. The problem appears when i want to start a career on 1944.

[Tanedin]

erikdell, do you mean that you think the menu_1024_768.ini is the cause of the problem? I use MaGui as well and I am also running into CTDs with a similar combination of mods.

edit
crap, didn't think I would make the thread roll over to the next page. Guess I'll have to add something more positive to kick off the new page, won't I?
Great job on the mods stiebler. Sure my own issues will resolve themselves eventually, I look forward to being able to fully enjoy the mod in the near future. I'm sure I'm not the only one who is grateful for all the hard work you and H.Sie have put into this game. How's it go anyway, you do it all in hex or similar, right? And I thought hex-editing myself infinite health in cave story was hard...

[Stiebler]

@Jinmei:
This error message appears at me: xd3 Invalid Input.I have never seen this error message before. However, it must be connected to the xdelta3.exe file (in folder 'tools'), which patches sh3.exe.
It seems that you have placed some of your files in the wrong folders.
Try again.

@Erikdell, Tanedin:
It seems that your difficulties are caused by the menu_1024_768.ini file.

The installation of the extra entries to this file, required for the grid-change mod, are complicated. You must insert the extra lines (stated in the documentation) and then *renumber* that part of the file which is affected. You can do this manually, or use H.sie's special renumbering tool for menu_1024_768.ini.

If the problem persists, use your preferred menu_1024_768.ini file (which is Makman's), and toggle OFF the grid-change option in the Options Selector. (Remember, you must alter the *last* occurrence of menu_1024_768.ini that is installed in your mod sequence with JSGME.)

@Rik007:
Aircraft can spot your U-boat at TC >256. I have seen it at TC=2048. However, for technical reasons, you will be seen less often by aircraft at TC 2048 than at TC 256. (In theory, about ( (2048/256)^2 ) * (aircraft-distance-per-second/ visibility-range) = <64 x less often.)

@Leitender: (Answer to question in another thread)
My boat stood in a perpendicular course to a destroyer (can´t remember distance) and although i showed my broadside, ASDIC didn´t recognize me at a MS=100², which in result meant a total dysfunction, at least in this trial. I then reduced MS to 75 and at last to 50m² and the result was i was recognized when in perpendicular position, but when i showed the DD my narrow side (bearing +-30deg) ASDIC lost contact. Confident about this result, I used from then on MS=50m².

Now i like to use your addon. But since you wrote about a "unique" value for MS which you have used to identify whether this MS-parameter works or not, i wonder if your mod is linked to this explicite value or if it also works e.g. with my favourite 50m². In general this mod is a great idea an i would really miss it within my game if it wasn´t usable with my settings.Unfortunately, the value of 100m2 is hard-coded as the only available indication that the code is looking at an asdic sensor and not at some other sensor.
Therefore I regret that I cannot change this value for one individual - it would probably upset everyone else!

Thanks for the feedback, everyone.
Stiebler.

[Leitender]

Unfortunately, the value of 100m2 is hard-coded as the only available indication that the code is looking at an asdic sensor and not at some other sensor. Thank you very much for your reply, Stiebler. That´s what i feared. Did you made similar experiences with that 100m² aspect, or did i gain a discrete result, not adaptive in general? Since this 100m² are standard for NYGM for years, maybe some players did their own observations and may report? I would be glad if the aspect-dependant detection worked as intended. :up:

[Jinmei]

This accurate error message: xdelta3: target window checksum mismatch: XD3_INVALID_INPUT

I cannot realise it that what's the problem,the V16B1 turned out easily...

The problem, only so much were resolved was how the trouble was not the V16B1 sh3.exe assigned the Realistic Repairs Option!!!!

[Dani]

@Jinmei

Try this:
After patching SH3 exe with V16B1 don't tick/untick nothing in the option selector.Make changes only after applying stiebler's addon.
It worked for me.

[SquareSteelBar]

...After patching SH3 exe with V16B1 don't tick/untick nothing in the option selector.Make changes only after applying stiebler's addon...That's the right way....

[Tanedin]

Alright, tried it without the 1024x768 file and was still having trouble. I decided to try a clean install, completely removed SH3 and mods and reinstalled everything, still running into trouble. Seems that after using the patch kit, I can run the game once without any problems. In order to launch the game again however, I need to delete sh3.exe and repatch from a fresh copy of V16b1. Not sure why that would happen though.

[makman94]

thank you very much Stiebler for this very important mod ! :salute:

[Dmitryi]

Thanks for the addon......:DL

[rik007]

Stiebler,

Thank you very much.

@Rik007:
Aircraft can spot your U-boat at TC >256. I have seen it at TC=2048. However, for technical reasons, you will be seen less often by aircraft at TC 2048 than at TC 256. (In theory, about ( (2048/256)^2 ) * (aircraft-distance-per-second/ visibility-range) = <64 x less often.)


I expected that. Rubini explained it in a thread. Everybody has a shortlist of shortcomings that should be solved to create the perfect SH-3 :).

[sharkbit]

I seem to be having a problem:
I downloaded the file, opened it up with 7-zip. I copied h.sie's patched sh3.exe file into a created temp file. I ran the batch file, the dos window opens up and it says it is searching for the patched sh3.exe, is patching it and creating a backup. Eveything seems ok so far, but....

when the dos window closes, there is no sh3.exe icon, only the back-up file of the old patched sh3.exe. :hmmm:

Where'd it go?
I looked around a little bit with no luck. I re-downloaded the add-on file from your site, same thing.

Any ideas?

Also, thanks to you and h.sie for all of your work in continuing to breathe new life into this game. :yeah:

:)

[Luno]

Can I ask what each of the features are? ie, what "smoke on the water" does to the game, etc. etc.

[Tanedin]

Seems it isn't a one-time-run issue, it's an issue with the year I choose to play. I get ctds when I try to play outside of 1939. I've tried with and without activating "No Continuous," with and without "supplement to V16B1." Tried using only shallow ASDIC, BDU Message improvement and smoke on the horizon mod. V16B1 mods are all except less contact reports.

I just tried it with none of the stiebler mods activated with a single scenario. In this configuration, it seems that I can only select scenarios in 1939 any others cause a ctd. Sometimes after a CTD, options selector V16 does not recognize the stiebler switches, giving me the "All switches must have value 0 or FF, with at least one FF" error.

It couldn't be SH3 commander related could it?

My mod list is as follows
GWX - Merged Campaign
GWX - No Medals On Crew
GWX - Open Hatch Mod
GWX - 16km atmosphere
MaGui F
No Continuous 'Ship Spotted' v1.2 for GWX3
optional - blue recmanual for MaGui F
optional - Intro Screen for MaGui F
optional - stopwatch with speed lines for MaGui F
supplement to V16B1
FUBARS - VIIB Plain
Stiebler3 addon for V16B1


Anyone have any ideas?

[SquareSteelBar]

I seem to be having a problem...Did you pay attention to Dani's post #20 ?

[Stiebler]

@Sharkbit:
when the dos window closes, there is no sh3.exe icon, only the back-up file of the old patched sh3.exe. :hmmm:
Where'd it go?Good question. It should be in the same folder. Use the 'Find File' option for your C: drive (or whatever drive you are using for Silent Hunter 3) to locate it. Make a note of the date and time you created the new SH3.exe, so that you do not get confused between alternative SH3.exe.
Or maybe you have created your temporary folder in an area where you do not have administrator rights, so the patched file cannot be created?

@Luno:
Can I ask what each of the features are? ie, what "smoke on the water" does to the game, etc. etc. Read either the help file provided with the Options Selector, or in the enclosed file Stiebler3A_patch_Docs.pdf. (I believe that the "Smoke on the Water" mod was created by the rock group "Deep Purple" in the 1970s, though.)

@Tanedin:
If Options Selector v1.6 throws up an error of no switches found, it means that it cannot find a single switch ON (ie value = FF) in the entire SH3.exe switches area. So either you are using an SH3.exe that is not patched at all, or your CTD has overwritten the entire switches area. (Most unlikely.)

I reckon that your difficulties are caused by error of installation of mods in correct order, and/or conflicts between your various menu_1024_768.ini files.

Unfortunately it is difficult to make an accurate diagnosis at long range.

Stiebler.

[Luno]

Read either the help file provided with the Options Selector, or in the enclosed file Stiebler3A_patch_Docs.pdf. (I believe that the "Smoke on the Water" mod was created by the rock group "Deep Purple" in the 1970s, though.)


:rock:

I will look through the PDF again. I didn't see descriptions for everything, but maybe I'm just too out of it after this long week.

[sharkbit]

@Sharkbit:
Good question. It should be in the same folder. Use the 'Find File' option for your C: drive (or whatever drive you are using for Silent Hunter 3) to locate it. Make a note of the date and time you created the new SH3.exe, so that you do not get confused between alternative SH3.exe.
Or maybe you have created your temporary folder in an area where you do not have administrator rights, so the patched file cannot be created?



I've searched a couple of times- no joy. I've got a "Patch" file that I've been doing the work in. H.sie's and yours are in there but in separate files within that one. Everything worked fine with h.sie's but with your add-on, my computer somehow loses the patched .exe file.

I'll try it one more time. If it doesn't work again, I'll copy my original .exe file onto my lap top and download your add-on kit and try everything on the laptop and transfer it back to my computer.

Thanks.
:)

[Tanedin]

Is the only change required in the sensors.dat the change in the minimum surface value for ASDIC in GWX? The crashes I'm experiencing seem to be related to the date. I would expect that would have something to do with a change in allied sensors past a certain date.

[sharkbit]

I'm officially stumped! :88)

I put my sh3.exe file that is patched with h.sie's V16B1 patch onto my laptop. Downloaded the add-on, un-zipped it, ran the patch file and same thing happened: the dos screen comes up and it says it is patching it, makes the back-up, but still no sh3.exe patched with the add-on.

Any ideas or am I missing something?
I'll re-read instructions. Maybe I'm having a mind fart-like that's never happened before :03: - and double check some stuff. It has got to be on my end since nobody has had this issue before.

:)

[J0313]

Actually I have had that same problem. I ended up doing the first patch ( hsie ). I didn't make any selections before doing the second patch ( Stieblers ). Everything worked okay. Wait to tick off your selections until after you have installed both patches.

I do have a major problem though. Now, when I tried to load a game after I have sank a ship or had a crewman killed the game crashes. But when I go back and load the saved game just before the one where I sank the ship or had the crewman killed it loads just fine. I wonder what heck is going on with that? Has anyone had this problem before?

[sharkbit]

Actually I have had that same problem. I ended up doing the first patch ( hsie ). I didn't make any selections before doing the second patch ( Stieblers ). Everything worked okay. Wait to tick off your selections until after you have installed both patches.



I actually thought of that this morning coming into work. I'm going to give it a try tonight.

I have been using a copied .exe of the first patch with a couple of items ticked off using the selector utility because I was doing some testing before I decided to try some of Stiebler's patches.

I'll bet money that is the problem.

:)

[Magic1111]

Hi Stiebler!

In your MOD I found the files EnvSim.act and SH3Sim.act. But these two files comes with h.sie´s V16B1 Patch too. Now my question is, should I let the two files from h.sie´s Patch override with the files from your Patch? And when yes, have I then the same functions as in h.sie´s Patch?

And what are the difference between the two files from h.sie´s Patch and yours?

And work the file "hsie.ini" with your MOD?

Best regards,
Magic

[Stiebler]

@Magic111:

My envsim.act is an optional replacement for that of H.sie. It has a different coded weather pattern. Use whichever version of envsim.act that you prefer for the weather.

My SH3Sim.act is the same as H.sie's, except that it contains also the code for the shallow-waters mod (asdic is poor in shallow waters).

Therefore you must install my SH3Sim.act over H.sie's original SH3Sim.act, but you can choose which version of envsim.act you prefer.

H.sie's original code (excepting the weather) is always preserved in my patch.

And therefore you can also continue to use H.sie's .ini file.

I hope that is clear.
Stiebler.

[Magic1111]

Hi Stiebler!

Let me summarize briefly, that I´ve understood correctly:

When I prefer the weather settings from h.sie´s Patch (what I do!) I can simple delete the envsim.act from your patch and I use the one from h.sie?!

If I want to play with the "Shallow water Option" from your MOD (what I want!) I MUST use your SH3sim.act and not from h.sie´s Patch?! ONLY when I want to play without the "Shallow water Option" I can delete your SH3sim.act?

Is this correct?

Best regards,
Magic

[Stiebler]

@Magic1111:
When I prefer the weather settings from h.sie´s Patch (what I do!) I can simple delete the envsim.act from your patch and I use the one from h.sie?!Correct.
If I want to play with the "Shallow water Option" from your MOD (what I want!) I MUST use your SH3sim.act and not from h.sie´s Patch?! ONLY when I want to play without the "Shallow water Option" I can delete your SH3sim.act?You must use my SH3Sim.act for the shallow-water option.
If you do not wish to have this option, then un-tick it in the Options Selector. It is not necessary to remove my SH3Sim.act, which contains also all of H.sie's mod-changes.

Stiebler.

[Magic1111]

@Magic1111:
Correct.
You must use my SH3Sim.act for the shallow-water option.
If you do not wish to have this option, then un-tick it in the Options Selector. It is not necessary to remove my SH3Sim.act, which contains also all of H.sie's mod-changes.

Stiebler.

Thank you Stiebler :up:, now everything is clear! :yep:

Best regards,
Magic:salute:

[Magic1111]

Hi Stiebler!

Sorry for a question again...:oops:

In regarding of the "Change-Grid-MOD" you write in the Instructions.rtf e.g. this:

[G3F I209]
Name=RO Report
Type=1026;Menu group
ItemID=0x3F290000
ParentID=0x3F0B0000
;;Pos=0,-45,436,560
Pos=0,-45,370,560
Color=0xFFFFFFFF

My "RO Report" looks like this (I´ve a different numbering, but that´s not the point), please look at the POS Line in red:

[G3F I219]
Name=RO Report
Type=1026;Menu group
ItemID=0x3F290000
ParentID=0x3F0B0000
Pos=218,0,436,560;0,0,436,560
Color=0xFFFFFFFF

The Main Differences between the two "RO Report" are the different POS Values!

Now my question is, are the POS Values "Pos=0,-45,370,560" from your Instructions.rtf Manual only for NYGM Users or should I use these values (I play with MaGUI Widescreen) too? :hmmm:

I hope you understand...!

Best regards,
Magic:salute:

[Stiebler]

Hallo Magic1111 again:
[G3F I219]
Name=RO Report
Type=1026;Menu group
ItemID=0x3F290000
ParentID=0x3F0B0000
Pos=218,0,436,560;0,0,436,560
Color=0xFFFFFFFF

The Main Differences between the two "RO Report" are the different POS Values! The positions I have given are for those who play with the default screen (1024 x 768).

Anyone who plays with a wide-screen (or non-default screen) will certainly require different values for 'Pos='.

Stiebler.

[Magic1111]

Anyone who plays with a wide-screen (or non-default screen) will certainly require different values for 'Pos='.


Aaah okay, thx Stiebler! :up:

Best regards,
Magic:salute:

[TorpLos]

I'm officially stumped! :88)

I put my sh3.exe file that is patched with h.sie's V16B1 patch onto my laptop. Downloaded the add-on, un-zipped it, ran the patch file and same thing happened: the dos screen comes up and it says it is patching it, makes the back-up, but still no sh3.exe patched with the add-on.

Any ideas or am I missing something?
I'll re-read instructions. Maybe I'm having a mind fart-like that's never happened before :03: - and double check some stuff. It has got to be on my end since nobody has had this issue before.

:)

I 2nd this problem. I dont quite understand what im doing wrong. Took original SH3.exe and patched it with HSIE... Took a copy of the patched and tried to update with Steiblers, but not SH3 exe popped up. In the DOS PROMPT it looked like it said XD3 INVALID INPUT...

[Eastwa]

Yeah no good with me either gone over it a few times and it keeps disapearing everytime I try to patch it, not sure what to do bit stumped with this one

[Stiebler]

@Torplos, Eastwa:

Take your version of SH3.exe which you have patched (successfully?) with H.sie's patch kit.

Restore all the defaults with the Options Selector. That is, everything ticked ON for H.sie's patches (except the Less Wolfpack option), and everything OFF for Stiebler's patches (if you cannot access the Stiebler menu screen, then everything is ticked OFF anyway).
[A safer and surer method would be to re-create the H.sie patch from your original legitimate SH3.exe file, then use it at once, without modification, in the next step.]

Then try again to patch the restored H.sie patch with the Stiebler_3A_Addon patch.

Stiebler.

[Eastwa]

Thanks Steibler, that seemed to do it now i'll see if it runs okay.

Cheers

[Kpt. Weyprecht]

I'm really impressed with this patch!
But I still can't get it to work: I followed the procedure of the H.sie's patch, then followed on to yours. I think I may have done something wrong with the modifications of the commands_en/de and menu files? Anyway, a career starts loading (I put it in 1941 to avoid the 1939 issue), then I have a CTD shortly before the mission should start.

When I disable the Addon with JSGME the game runs normally and appears to be successfully patched to 1.6b version.

Since my system prevents me from modifying files in the Program files(x86) folder, I copied those files into the foder of the addon (I created the Cfg folder in \Data), modified them there, then copied the whole in my MODS folder and tried to activate with JSGME. Was this a bad idea?

And one more question: since yous "Smoke on the horizon" and "Asdic" mods are much more critical for me than Change grid or Abandon U-boat, can I simply disable those two in the Option selector and leave my commands and menu files unchanged?

[Stiebler]

@Kpt Weyprecht:
Since my system prevents me from modifying files in the Program files(x86) folder, I copied those files into the folder of the addon (I created the Cfg folder in \Data), modified them there, then copied the whole in my MODS folder and tried to activate with JSGME. Was this a bad idea? No, that is the correct procedure.
since your "Smoke on the horizon" and "Asdic" mods are much more critical for me than Change grid or Abandon U-boat, can I simply disable those two in the Option selector and leave my commands and menu files unchanged? Indeed you can disable the Grid and Surrender options with the Options Selector.
However, you may still get CTDs if your en/de_menu.txt or commands_en/de.cfg files (or other files) are sufficiently damaged. You must use the original files en/de_menu.txt and commands_en/de.cfg.

I am puzzled by your CTDs. The usual problem with errors in en/de_menu.txt or commands_en/de.cfg is that some messages do not occur, or some commands do not function. Errors here are unlikely to cause CTDs. I believe that your problem lies with one of the campaign files, from your description (CTD near end of loading game). Try loading all your campaign files, one at a time, into the single mission editor, in order to see whether there are any errors reported here. Examine very closely the CAM-ship (M36B; see documentation for the Stiebler add-on).

Stiebler.

[Kpt. Weyprecht]

Thank you for help!
I tried to revert to original en/de_menu.txt and commands_en/de.cfg files but I still have CTDs.

Indeed, I missed the changes to make for the CAM-ship mod: I'll try doind this correctly or disabling the mod to see if the patch would work without it.

Sorry for my dumb questions but I'm not at all familiar with the mission editor: are the files I shoul check the three .mis files in the \data\Campaigns\Campaign? I opened them in the Mission editor and had no error message but maybe I should use some diagnostic tool or search for a particular detail?

[TorpLos]

Quick question.

The Stiebler_addon_for_V16B1 can be installed right away right?? Does it need the other part of the Steibler patch? or can i just add it to my mod list and get the Smoke on Horizon?

[Kpt. Weyprecht]

I'm not sure what you mean... I can disable all the other options and I actually tried changing (by deleting from the Addon folder all the other files) only what I care most to keep the original commands, menu or units. Is that what you mean by installing right away?

[TorpLos]

There are 2 parts of the patch.

Stiebelrs Additional_files V16B1
AND
Stieblers addon_for V16B1

Taken from instructions...


A subsidiary mod-folder ‘Stiebler3_Addon_for_V16B1’ which can be installed at once with JSGME. It contains SquareSteelBar’s change to the radio icons specially for the Surrender mod, two OGG sound files to be used by the "Smoke on Horizon" mod (conversions of the famous shouts created originally by the legendary "Aces of the the Deep" U-boat simulation), a modified sound file SH3Sound.act and a modified file SH3Sim.act.

Activiating that via JSGME without adding the rest of the sh3.exe patched version by steibler wouldnt cause problems right? Because i am still at a loss updating sh3.exe HSIE with Stieblers new patch.

[Kpt. Weyprecht]

Oh, I see. I really should read those docs more carefully. But does it really change the sim's behaviour when your Sh3.exe is a "bare" 1.6b? I recall some old discussions where the impossibility of seing a target's smoke (or just mastheads) over the horizon was said to be due to a hardcoded (to be corrected with the patch, I assume) problem of the sh3 world being flat?

Does this work on your rig?

[Stiebler]

Sorry for my dumb questions but I'm not at all familiar with the mission editor: are the files I shoul check the three .mis files in the \data\Campaigns\Campaign? I opened them in the Mission editor and had no error message but maybe I should use some diagnostic tool or search for a particular detail? If you had no errors in loading the three campaign_RND/LND/SCR.mis files into Mission Editor, then (probably) there are no errors with these files.
But does it really change the sim's behaviour when your Sh3.exe is a "bare" 1.6b?I think you mean SH3 with bare 1.4b patch, as originally supplied by Ubisoft. All releases of SH3 from year 2006 onwards had the 1.4b patch pre-added to the game before release.
But it is essential for H.sie's patches, and my patches, that your authentic, genuine, copy of SH3.exe be altered ('patched') before any of our additions work.

I think it is necessary here to emphasise again, that the Stiebler 3A_Addon patch for SH3.exe is intended to OVERLAY H.sie's patch for SH3.exe. That is, you MUST install H.sie's patch first (see his sticky thread for details about this). You MUST also install the mod folder that H.sie has provided for HIS patch. [Test the game at this point, to ensure that your first patch attempt succeeded.]

Only then can you install my 3A overlay patch, which also has its own separate mod folder to install. Both our mod folders are best installed with JSGME.

None of the files/mods, which H.sie and I have placed in our mod folders for our patches, will function by themselves. They must have the code patches in place, if the other files are to function correctly.

Stiebler.

[Magic1111]

Hi Stiebler!

I must report a CTD (reproducible) in regarding to the BdU-Messages Option!

When I in the "message menu" (key M) send a status report, namely by ingame 14.20h, I always get just one hour later (ingame) a CTD! ALWAYS and can be reproduced! I think that is indeed the time (after an hour-ingame), where the answer should arrive. Ingame it goes to 15.20h, then after a few more seconds, CTD!

Themselves have already tried the following: Went back to Windows and have via option selector disabled your option "Bdu-Messages-improvement" (the option BdU-Messages from h.sie furthermore enabled). Then load a savegame. However, the same result, CTD exactly one hour after submitting the status report.

Then back to Windows and via option selector the h.sie Option "BdU messages" disabled (now both BdU-Messages Options disabled, from h.sie and yours) and then load the same savegame. Then send a status report and it came after about 10 minutes ingame (this is probably standard SH3), the response back to the line of text of the 4198 de_Menu.txt (ie standard) and the game works normal without CTD!

Could you please help me? In what could be the problem? :hmmm:


I tried this on Mid-Patrol and in a single- AND Test-Mission, always the same result! I patched successfully several times the original SH3.exe with h.sie Patch and then immediately with your Patch, all other options from h.sie and yours works well!

When I use ONLY the h.sie Patch, the Bdu-Messages works well, after I give a Status-Report, the answer from "BdU" received without any CTD, ONLY when I use your patch, I become a CTD when a BdU-Message should receive! :wah:

I hope you can fix the problem, I would like to play with your Fix, but with BdU-Messages Option too! :yep:

Best regards,
Magic

[Stiebler]

Hallo Magic,

This is a puzzling problem. You believe that the Stiebler3_Addon causes CTDs when you send a message from the Radio Messages menu (key 'M'), but the CTD persists when you disable the 'Radio Messages Fix' in the Stiebler3_Addon with the Options Selector.

It is perhaps possible that some other bug in the Stiebler3_Addon is causing the fault (not the 'Radio Messages Fix'), but this is unlikely.

I suspect that the real problem lies with the combination of other mods that you perhaps use. Try again with all mods removed, except your basic super-mod (GWX?), and the H.sie and Stiebler3 patches.

Also re-test your game with a new career or new single-mission. Do not reload saved games that you know to cause CTDs.

I hope that helps,
Stiebler.

[reignofdeath]

Stiebler,
thank you very much for the work you and H.sie have done, I have two questions however.

Looking at the post, can you explain what some of these mods do?? Like the Cam ships and the asdic in shallow waters??

and secondly,

are you and H.sie going to continue work on this mod to see what happens and what else can be done?? Or are the updates for the hardcode mod finally finished??

[Magic1111]

You believe that the Stiebler3_Addon causes CTDs when you send a message from the Radio Messages menu (key 'M'), but the CTD persists when you disable the 'Radio Messages Fix' in the Stiebler3_Addon with the Options Selector.

Yes, I´m 100% sure! But I must disable both BdU Messages Fixe, from h.sie and from yours, then it works without CTD! But it receive then the Standard-Messages from de_Menu.txt, NOT from the Fixe. When I only disable your BdU-Messages-Improvement Fix and let the Bdu-Fix from h.sie enabled, same Problem > CTD! ONLY when I use the patched .exe with h.sie´s Patch without your "Stiebler3_Addon" with the BdU Fix from h.sie enabled, this works without CTD! :hmmm:

...

I suspect that the real problem lies with the combination of other mods that you perhaps use. Try again with all mods removed, except your basic super-mod (GWX?), and the H.sie and Stiebler3 patches.

I use rowi58´s CCoM Super-MOD (on base of LivingSilentHunter)! And yes, I will try it again ONLY with the Super-MOD enabled and without any other Additional-MODS and report the result here!

Also re-test your game with a new career or new single-mission. Do not reload saved games that you know to cause CTDs.

Okay, but I tested in Naval Academy, SingleMission and in a extra Test-Mission created from rowi58 for me to test this problem, and at last in a savegame of my current career! The result are all the same: CTD after sending a Status Report (when the answer from BdU received)! Again: ONLY with your patch! When I try a SH3.exe patched only with the fix from h.sie > No problem, the answer from BdU received without problems!


Hi Stiebler!

Read in green please!

Best regards,
Magic

[Stiebler]

@CaseySmith:
Descriptions of the roles of the mods are available with the documentation included.

@Magic1111:
The CTD when you send a radio message. There is not a bug in the code. Please understand that I test my mods before I release them (I know that some people do not...), and certainly I must have seen such an obvious bug (CTD one hour after transmission of radio message), if it existed in my version of NYGM-SH3. I test my mod releases: not in single missions, not on patrols, but with complete careers/campaigns (1939-1945).

Therefore your CTD is certainly caused:
EITHER: by differences between the *other* mods which you and I have installed separately on our stock SH3. (Perhaps incorrect sequence of installation of mods.)
OR: because for some reason your patches first with Hsie's patch kit, then with mine, have failed in some way.

There can be no other explanation. Sorry, but I cannot help further.

Stiebler.

[Magic1111]

@Magic1111:
The CTD when you send a radio message. There is not a bug in the code. Please understand that I test my mods before I release them (I know that some people do not...), and certainly I must have seen such an obvious bug (CTD one hour after transmission of radio message), if it existed in my version of NYGM-SH3. I test my mod releases: not in single missions, not on patrols, but with complete careers/campaigns (1939-1945).

Therefore your CTD is certainly caused:
EITHER: by differences between the *other* mods which you and I have installed separately on our stock SH3. (Perhaps incorrect sequence of installation of mods.)
OR: because for some reason your patches first with Hsie's patch kit, then with mine, have failed in some way.

There can be no other explanation. Sorry, but I cannot help further.

Stiebler.

Hi Stiebler!

Today I tested it on a fresh SH3 1.4b Install with only the Super-MOD "CCoM by rowi58" enabled, NOT other MODS, only CCoM!

Then I patched the stock SH3.exe again with h.sie patch, then with yours, after both patching operations I become the message "successfully patched"! I leave all options in the "OptionsSelector" unchanged and start a Single Mission and a TestMission (TestMission made by rowi58 for me):

The Result is all the same: CTD after sending a Status Report when I use your patch! When I use only the h.sie patch, all works well. I send a status report, and after this a BdU-Message received! When I use your patch > CTD after sending a Status Report!

Sorry that I must this report back Stiebler, but this are my experience with your Patch! :wah:

Any Solutions? :hmmm: E.g. can you upload for me the patched .exe that you use in your game? Then I can test it with your .exe again in my game! Is this possible please?

Best regards,
Magic:salute:

[Jinmei]

Hello everyone

The same one happened at me than Magic1111 his case.
I hope so how will be onto him solution.

[Magic1111]

The same one happened at me than Magic1111 his case.
I hope so how will be onto him solution.

Hi!

Thx for posting your valuable Feedback! :up:

I hope for a solution too...! :yep:

Best regards,
Magic

[h.sie]

@Magic: Try the following: Set all languages to "english" instead of german. Still CTD?

[Wolfstriked]

Stiebler,I got your ASDIC mod patched into my execute and wonder what is the minimum files I need extra.Am I right to think that all I need now is to add........AI_Sensors_GWX.dat..................... ...changed to AI_Sensors.dat?

[Magic1111]

@Magic: Try the following: Set all languages to "english" instead of german. Still CTD?

Hello Stiebler, hello h.sie!

After several tests I found the solution:

The Add-On for h.sie Patch "More wounded & less dead crew" from HERE (http://www.subsim.com/radioroom/showpost.php?p=1869895&postcount=3311) works not together with the Stiebler Patch!!!

The simple solution was: I delete the three files from the above Add-On "wounded.act" and the two ".bin Files" and all works well! I test it with all h.sie and Stiebler Options enabled and with my complete MOD-Soup and after send a Status Report the answer from BdU received without CTD!

When I enable the above Add-On together with the Stiebler Patch ---> CTD after sending a Status Report!

Now my question to h.sie and/or Stiebler: Is it possible, that one of you make the wonderful Add-On "More wounded..." compatible to the Stiebler Patch please? Please, in the interest of the community and your Fans of both patches, because we want to play with both patches without any CTD´s!

Many thx in advance! :yeah:

Best regards,
Magic:salute:

[h.sie]

If it's really my new Fix that causes the problem, I apologize.

But Magic, your last post #67 conflicts with your post #62, where you emphasize, that you had a CTD, although you tested only with "CCoM by rowi58" enabled, NOT other MODS, only CCoM!

-- Which of your two posts represents the truth?
-- Are your testing results and methods reliable?

Anyway, for security reasons, I deleted the "More wounded & less dead crew" from my mediafire page, until I find the reason for the problems some day in the far future.

Sorry, Stiebler, it was - of course - not my intention to cause incompatibilities between your work and mine.

[Magic1111]

Are your testing results reliable?

Yes, see Post #58 from Stiebler. In this Post he recommended to me, that I should test ONLY with my current Super-MOD enabled, not any other MODS. That I have did >>> CTD (with More wounded...enabled)!

Today I continued the tests. Only with CCoM enabled without "More wounded..." >>> all works well!

With CCoM as base and my complete other MODS enabled without "More wounded..." enabled >>> All works well!

Only when "More wounded..." is enabled I´ve CTD´s with CCoM and/or with CCoM and my complete MOD-Soup!

All tested on a fresh SH3 v1.4b Install!

Best regards,
Magic

[h.sie]

...there was indeed an incompatibility between Stieblers AddOn and my "More wounded & less dead crew"-Fix. This incompatibility is fixed now. New version v2 of the "More wounded & less dead crew"-Fix can be found on my mediafire page. The cause was a misunderstanding between Stiebler and me. Thanks, Magic1111, for helping to find the problem.

[Stiebler]

Clearly I must apologise to H.sie, and indirectly to other users of H.sie's 'More wounded..' mod.

H.sie is too much of a gentleman to state the blame, so I shall say it:
When I made a small change to H.sie's BdU messages code, as documented in the Stiebler3A-Addons patch, I thought it appropriate to add *my* extra code at the end of H.sie's original code. I should have placed it in my own code area.

H.sie was not aware of my change to his code area, and used what he believed to be a blank code space in his area to add the code for his 'More wounded..' mod.

Result: reproducible CTD whenever a radio status message was sent. (I had not installed this new H.sie mod, so could not reproduce the problem.)

So, apologies again to H.sie, who was the one who discovered the cause of the problem, and to those other persons affected.

Stiebler.

[Magic1111]

...
Thanks, Magic1111, for helping to find the problem.

My pleasure, mate! :salute:

And many thx for the new version of the "More wounded..." Add-On!! :yeah:

Best regards,
Magic

[Wolfstriked]

Stiebler,I got your ASDIC mod patched into my execute and wonder what is the minimum files I need extra.Am I right to think that all I need now is to add........AI_Sensors_GWX.dat..................... ...changed to AI_Sensors.dat?

[TorpLos]

Ok im sorry. Quick question.

I installed H.sie's patch fine. Worked perfectly.

I patched H.sies exe. from Stieblers without a hitch.

Now.. I take THAT SH3.exe put it into the folder "Stiebler3_Addon_for_V16B1" and activate via JSGME right?

Do i have to do all the other menu/txt stuff?? I know its for CAMSHIP and Change patrol grid but thats not very essential to me. I just want to activate the "Stiebler3_Addon_for_V16B1" and play with what i can.

[Stiebler]

@Wolfstriked, Torplos:

I advise strongly against selecting a few parts of the add-on package for Stiebler3A_Addons_V16B1. I have not tested my release for different parts, but only as the complete package.

Install ALL the add-on folder, with your patched SH3.exe within the add-on folder. Do NOT attempt to pick out the parts that you like best. I cannot predict what the result will be.

If you want to disable some of my patches, then use the Options Selector.

Wolfstriked said:
Am I right to think that all I need now is to add........AI_Sensors_GWX.dat..................... ...changed to AI_Sensors.dat? This is correct (if you are using GWX, you forgot to say).
But, as I have said above, use the complete package. Rename AI_Sensors_GWX.dat to AI_Sensors.dat, then copy this new file to the Stiebler3_ADDon_for_V16B1 folder, and install the folder with JSGME.

Stiebler.

[TorpLos]

Ugh! Ive done good thus far im a little nervous to mess with those files when they arent jsgme ready. Damn.. Ill give it a go then :(

[Wolfstriked]

Thanks Stiebler.I think I am good with everything in the data folder as it seems like its speech sound files,CAm ship files and dials.tgs files.But I am unsure of the envsim.act,Sh3sim.act and SH3 Sound.act files.Are these needed by the ASDIC mod....and the Cam Ship whcih I wanna try out next?Reason I wanna pick and choose is that I am constantly adding and taking away files with jsgme and wanna keep them as small as possible.

[Stiebler]

@Wolfstriked:
But I am unsure of the envsim.act,Sh3sim.act and SH3 Sound.act files.SH3Sim.act is essential - if this file is not added, you will get a CTD.
SH3Sound.act file is necessary if you want to hear the 'Smoke on Horizon' shout from the crew.
Envsim.act is completely optional. It includes the NYGM method of weather control. But H.sie's V16B1 patch already contains a different envsim.act file with H.sie's type of weather control. Use whichever file you prefer.

Stiebler.

[Jinmei]

Hi Stieber

Would interest what it what you modified the AI_Sensors.dat
,I compared it the 3.5 NYGM version AI_Sensors.dat and I did not find a difference.

[Wolfstriked]

@Wolfstriked:
SH3Sim.act is essential - if this file is not added, you will get a CTD.
SH3Sound.act file is necessary if you want to hear the 'Smoke on Horizon' shout from the crew.
Envsim.act is completely optional. It includes the NYGM method of weather control. But H.sie's V16B1 patch already contains a different envsim.act file with H.sie's type of weather control. Use whichever file you prefer.

Stiebler.

Thanks Stiebler.:salute:

[TorpLos]

Ok..

So when i add the command.de and command.en from my stiebler docs to my data/cfg folder in SH3 i run into a problem. The command line


[Cmd455]
Name=Request_New_grid
Ctxt=1
MnID=0x3F290006
Key0=0x4d,s,"SHIFT M"

is already in my sh3 cfg.... Do i delete the old Cmd455 file and add this one because they are exactly the same.

And for the de_menu and en_menu i just copy/past the lines to the END of the original lines? Even though those lines already exist? Seriously i dont know why this is confusing me so bad

[Vince82]

"Shallow-water Asdic mod"

Manual (Stieblers3A_patch_Doc.pdf):


It is necessary to use a single unique value for asdic minimum surfaces in AI_sensors.dat in all the
supermods, if this mod is to function. The unique value of 100.0 has long been used in NYGM, and
appears effective in practice. Other supermods may use different figures, for Asdic ‘MinSurface’, and
these will need to be changed in the super-mods’ AI_Sensors.dat file (found in
silenthunteriii\data\library). For example, both the stock SH3 game and GWX have values for
MinSurface of 0.0.
A list of the Asdics is given below:
QGAA, QC1A, QCeA, 147A, 144A, 128A, 123A.
Unfortunately, you cannot change these values in a text editor. You must use a data editor, such as
TimeTraveller’s ‘FileAnalyzer’, or Skywas’s ‘Sd3Ditor’. FileAnalyzer is easier to use for this
purpose.



I'm using Skywas's Sd3Ditor...
So I should only change the Minsurface value in the 7 Asdic types and I should leave '14 Node AI_sonar' unedited?

[Vermin]

Thanks for this add-on Stiebler!

[Stiebler]

@Vince82:
I'm using Skywas's Sd3Ditor...
So I should only change the Minsurface value in the 7 Asdic types and I should leave '14 Node AI_sonar' unedited? Good question.

However, AI_Sonar is not, in fact, used by any ship or other object, therefore it does not matter whether you alter it or not.

Stiebler.

[Vince82]

Thank you for your last answer, Stiebler.

I've got two more questions if you don't mind (or maybe somebody else knows...); does the simulated thermal layers by Hemisent used by SH3 commander conflict with your 'shallow-water' ASDIC mod?

JSGME:

"Dials1b.tga" has already been altered by the "MaGui 3.4" mod.
"Orders2.tga" has already been altered by the "MaGui 3.4" mod.


What will happen if I don't install those two files and what's the best way to solve this?

[drakkhen20]

where can i get all the stiebler patches ??

[Myxale]

where can i get all the stiebler patches ??

Second sticky on the SH3 board.
[/URL][URL]http://www.subsim.com/radioroom/showthread.php?t=174225 (http://www.subsim.com/radioroom/showthread.php?t=174225)
:salute:

[SquareSteelBar]

Second sticky on the SH3 board.
http://www.subsim.com/radioroom/showthread.php?t=174225
:salute:No.

Click Stiebler (http://www.subsim.com/radioroom/member.php?u=222167)'s signature.

[Myxale]

:D


Sorry. In my head i somehow merged h.Sie and Stiebler- :88)

[drakkhen20]

hhmm intresting. ill give them a try later, thanks.:salute:

[Albrecht Von Hesse]

...there was indeed an incompatibility between Stieblers AddOn and my "More wounded & less dead crew"-Fix. This incompatibility is fixed now. New version v2 of the "More wounded & less dead crew"-Fix can be found on my mediafire page. The cause was a misunderstanding between Stiebler and me. Thanks, Magic1111, for helping to find the problem.

I've no idea how to incorporate this. :88)

[fitzcarraldo]

Dear Stiebler:

I´m trying to compatibilize Stieblers´s Addon with the Aces SuperTurms 7 (taster version V2, a WIP).

The Aces mod has a "shift+N" and "Ctrl+N" commands for toggle/untoggle the UZO in deck.

With these commands, with Stiebler´s Addon, I have the Compressed Time function, and I lost the UZO commands. But I need (and I want) the UZO commands! :hmmm:

Where is the Compressed Time function? I would to change the commands for TC or eliminate the Time compressed function.

Many thanks in advance and Happy Easter!

Fitzcarraldo :salute:

[Stiebler]

@Fitzcarraldo:

The Ctrl-N command in the Stiebler4B_Addon (3A is somewhat outdated) for time acceleration is hard-coded, in the assembly code. There is no easy way to change it.

I believe that it ought to be much easier to change the Shift-N and Ctrl-N commands in Ace's mod, since that probably requires a change somewhere in text, and you could probably make a change for your mod only.

It is a pity that our mods have clashed, since Ace's mods are certainly very popular.

Stiebler.

[Anvar1061]

SSS
I believe that it is possible to change to the "shift+U" and "Ctrl+U" commands for toggle/untoggle the UZO in deck in Ace's mod.