@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.

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:

CTD in regarding to BdU-Messages
 

Hello everyone

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

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

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?

Solution found!
 

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 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:

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.

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

...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.

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.

My pleasure, mate! :salute:

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

Best regards,
Magic

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?

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.

@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:
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.