For all who are having problems run SH3Cdr 2.6 with NYGM-TW 2.01, I believe I know what the problem is. NYGM changed the various .ZON files for all the Subs. SH3Crd randomizes the “crush depth” which is part of theses .ZON files. The randomized “crush depth” settings were in the “miscellaneous.cfg” in SH3Cdr 2.5, they are now in the “SH3 options.cfg” in 2.6. Even if you load the “miscellaneous.cfg” that comes with NYGM, 2.6 will “not” ready it. Therefore the .ZON files are corrupted and SH3 will hang when loading. To correct the problem opens the “miscellaneous.cfg” from NYGM in WordPad and copy the following:

[CRUSH DEPTH]
;Randomises/sets crush depth for each sub type.
;<Subtype>=<folder/file name>|.zon offset|default crush depth in metres>
;Upper and Lower provides the randomisation range.
;Written to each sub's .zon file
Upper=1
Lower=0.9

IIA=NSS_Uboat2A|x2688|175
IID=NSS_Uboat2D|x2688|200
IXB=NSS_Uboat9b|x2CA2|275
IXC=NSS_Uboat9c|x3066|275
IXC/40=NSS_Uboat9c|x3066|275
IXD2=NSS_Uboat9d2|x2CA2|275
VIIB=NSS_Uboat7b|x1A86|250
VIIC=NSS_Uboat7c|x1A86|300
VIIC/41=NSS_Uboat7c|x1A86|350
VIIC/42=NSS_Uboat7c|x1A86|450
XXI=NSS_Uboat21|x35A8|350


Then open “SH3 options.cfg” and replace this;

[CRUSH DEPTH] ;THIS BLOCK CAN BE DELETED IF UNWANTED
;Randomises/sets crush depth for each sub type
;<SUBTYPE>=<folder/file name>|<.zon offset>|<default crush depth in metres>
;Upper and Lower provides the randomisation range
;Written to each sub's .zon file
Upper=1
Lower=0.9

IIA=NSS_Uboat2A|x2688|175
IID=NSS_Uboat2D|x2688|200
IXB=NSS_Uboat9b|x2C43|275
IXC=NSS_Uboat9c|x3007|275
IXC/40=NSS_Uboat9c|x3007|275
IXD2=NSS_Uboat9d2|x2C43|275
VIIB=NSS_Uboat7b|x1BA3|250
VIIC=NSS_Uboat7c|x1BA3|300
VIIC/41=NSS_Uboat7c|x1BA3|350
VIIC/42=NSS_Uboat7c|x1BA3|450
XXI=NSS_Uboat21|x35A8|350




Also NYGM change the file structure of “AI_Sensor.dat” This is where the “Randomly adjusts active/passive listening device values to simulate the impact of thermal layers” setting are keep. If you look in the SH3Cdr 2.6 CFG directory you will note that along with “Randomised Events.cfg” there are also “Randomised Events_19xx.cfg”, each have entries that effect “AI_Sensor.dat”. Unless you replace theses entries in each file:

[0:data\Library\AI_Sensors.dat]
;Randomly adjusts active/passive listening device values to simulate the impact of thermal layers - by Hemisent
;Only MinHeight values are changed
ChooseFrom=10
RndMidPat=1

0_x0470=-105 ;AI_Hydrophone
0_x05FC=-90 ;AI_Sonar
0_x0784=-105 ;QGAP
0_x090C=-105 ;QClP
0_x0A94=-105 ;QCeP
0_x0C20=-108 ;Type144P
0_x0DAC=-105 ;Type138P
0_x0F38=-100 ;Type128P
0_x10C4=-100 ;Type123P
0_x124C=-90 ;QGAA
0_x142B=-88 ;QClA
0_x160A=-93 ;QCeA
0_x17ED=-95 ;Type147A
0_x19D0=-98 ;Type144A
0_x1BB3=-85 ;Type128A
0_x1D96=-88 ;Type123A

1_x0470=-150
1_x05FC=-130
1_x0784=-145
1_x090C=-155
1_x0A94=-145
1_x0C20=-150
1_x0DAC=-155
1_x0F38=-144
1_x10C4=-145
1_x124C=-130
1_x142B=-135
1_x160A=-125
1_x17ED=-135
1_x19D0=-130
1_x1BB3=-128
1_x1D96=-132

2_x0470=-180
2_x05FC=-170
2_x0784=-200
2_x090C=-195
2_x0A94=-195
2_x0C20=-215
2_x0DAC=-215
2_x0F38=-190
2_x10C4=-190
2_x124C=-195
2_x142B=-190
2_x160A=-180
2_x17ED=-200
2_x19D0=-190
2_x1BB3=-175
2_x1D96=-175

3_x0470=-235
3_x05FC=-220
3_x0784=-238
3_x090C=-235
3_x0A94=-230
3_x0C20=-235
3_x0DAC=-238
3_x0F38=-230
3_x10C4=-235
3_x124C=-225
3_x142B=-220
3_x160A=-215
3_x17ED=-228
3_x19D0=-225
3_x1BB3=-218
3_x1D96=-215

4_x0470=-270
4_x05FC=-260
4_x0784=-275
4_x090C=-270
4_x0A94=-268
4_x0C20=-275
4_x0DAC=-265
4_x0F38=-263
4_x10C4=-265
4_x124C=-260
4_x142B=-257
4_x160A=-255
4_x17ED=-263
4_x19D0=-260
4_x1BB3=-255
4_x1D96=-253



with




[0_data\Library\AI_Sensors.dat]
;Randomly adjusts active/passive listening device values to simulate the impact of thermal layers - by Hemisent
;Only MinHeight values are changed
FileType=B
ChooseFrom=10
RndMidPat=1

0_xC35=-105 ;AI_Hydrophone
0_xDC1=-90 ;AI_Sonar
0_xF49=-105 ;QGAP
0_x10D1=-105 ;QClP
0_x1259=-105 ;QCeP
0_x13E5=-108 ;Type144P
0_x1571=-105 ;Type138P
0_x16FD=-100 ;Type128P
0_x1889=-100 ;Type123P
0_x1A11=-90 ;QGAA
0_x1BF0=-88 ;QClA
0_x1DCF=-93 ;QCeA
0_x1FB2=-95 ;Type147A
0_x2195=-98 ;Type144A
0_x2378=-85 ;Type128A
0_x255B=-88 ;Type123A

1_xC35=-150
1_xDC1=-130
1_xF49=-145
1_x10D1=-155
1_x1259=-145
1_x13E5=-150
1_x1571=-155
1_x16FD=-144
1_x1889=-145
1_x1A11=-130
1_x1BF0=-135
1_x1DCF=-125
1_x1FB2=-135
1_x2195=-130
1_x2378=-128
1_x255B=-132

2_xC35=-180
2_xDC1=-170
2_xF49=-200
2_x10D1=-195
2_x1259=-195
2_x13E5=-215
2_x1571=-215
2_x16FD=-190
2_x1889=-190
2_x1A11=-195
2_x1BF0=-190
2_x1DCF=-180
2_x1FB2=-200
2_x2195=-190
2_x2378=-175
2_x255B=-175

3_xC35=-235
3_xDC1=-220
3_xF49=-238
3_x10D1=-235
3_x1259=-230
3_x13E5=-235
3_x1571=-238
3_x16FD=-230
3_x1889=-235
3_x1A11=-225
3_x1BF0=-220
3_x1DCF=-215
3_x1FB2=-228
3_x2195=-225
3_x2378=-218
3_x255B=-215

4_xC35=-270
4_xDC1=-260
4_xF49=-275
4_x10D1=-270
4_x1259=-268
4_x13E5=-275
4_x1571=-265
4_x16FD=-263
4_x1889=-265
4_x1A11=-260
4_x1BF0=-257
4_x1DCF=-255
4_x1FB2=-263
4_x2195=-260
4_x2378=-255
4_x255B=-253


SH3 will hang up on launch

Thanks lurker_hlb3. I'm sure that is all that is required to get them "back together" again.

But as I posted earlier, if anyone is experiencing problems with NYGM and SH3Cmdr, they should post over in the NYGM thread where the chance Observer will see it is higher. He may already have the solution ready for users.

Congrats, these things make the game a highlander!:up:

Roger your last, will post there also in the NYGM thread

Thanks lurker_hlb3 :up:

This will get players going again. I suspect Observer may post a link to replacement SH3Cmdr R2.6 files, or he may have some other method for updating them, or he may just use your solution!

You've reminded me of one thing that is explained in the readme, but I'll point it out for those that, well, don't read the readme...

By default SH3Cmdr will only model malfunctions. It will not model the effects of sabotage.

However, the effects of sabotage can very easily be "switched on" simply by deleting or renaming the "Randomised events_19**.cfg" files located in SH3Cmdr's Cfg folder.

Thus, an alternative to your solution, if NYGM players *want* sabotage effects, they can remove the "Randomised events_19**.cfg" files and just update the "Randomised events.cfg" file. Alternatively, if they don't want the sabotage effects, and they don't want to cut and paste into eight files, they can still follow the above steps, but in "Randomised events.cfg" they should delete every line on from:

I'd recommend for player ease that someone just post updated NYGM compat files for d/l, but I don't know whether Observer has other plans. Hopefully he'll visit shortly.

Links removed. Files superseded.

FOR GOD!!!!!!!! NOw I can Stop DW and Back to play my SHIII complete. I was just waiting that realease!! SHIII without CH3commander and NWGM is just a eye candy.
:cool:

HHIIIIIII pi HIIIII pi WHOOOHAAAA JScones is our king:arrgh!: :88)

thx:rock:

SH3Cdr 2.6 working okay on my boat. :D although im running the stock game with just a few graphic/sound mods. But a o kay here.

Down periscope.

anyone tried to start a carrer in 1944 or 45.. I can't there is nothing available to choose squadron or boat type :o

not a big worry for me cause I like 41 or 43 normaly but it is a bit wierd

SH3Cmdr doesn't add 1944/45 start dates to your game - for that you need a mod such as GW, RUb, NYGM, or at least Beery's FlotillaMod. SH3Cmdr just supports these years if they are available.

:p ah my noobyness is showing.. cheers :up:

Great effort JS just a quick Q.....................
I have GW installed that is all on a fresh version of SH3 and of course SH3C 2.5
so i just do as you say to uninstall every thing except SH3Cmdr.ini and then install 2.6 is this alright with GW and can i do it mid patrol and also in the same carear.
or would you reccomend a fresh install of SH3 then GW then your great SHC 2.6

thanks dude...........

Installing whilst in a current career is perfectly OK, but I'd return to base first. Then I'd follow the steps outlined on the previous page of this thread.

You definitely don't need to touch your installation of SH3/GW in any way (indeed, this is regardless of whether you run GW, RUb, NYGM, IUB or vanilla), but I will draw this paragragh from the GW readme file to your attention:

Quote:

This mod is fully compatible with SH3 Commander. However, in order to maintain the integrity of the destroyer aggression modifications, it is recommended to leave or set the "Lost contact time" to 15 minutes in SH3 Commander’s. Please refer to the SH3 Commander Help file for further instructions.

Big THX JScones :up:

2.6 is a great improvment. I´l loved :yep: