[TEC] SH5.exe patches to fix bugs and add functionality

[gap]

Two last questions about the U-boat position thing:

can you use the header at the beginning of each section for determining the type of unit spawned? And can you assign to that unit her correct number, based on the first column of each entry?

[TheDarkWraith]

Originally Posted by gap

Two last questions about the U-boat position thing:

can you use the header at the beginning of each section for determining the type of unit spawned? And can you assign to that unit her correct number, based on the first column of each entry?

I can try. It would need to be in a different format though. It would need to be in the game's classname format: SSTypeVIIA, SSTypeVIIB, etc. I can definitely assign a custom u-boat number to a dispatched sub no problem (already doing this).

[THE_MASK]

Using TDW_GenericPatcher_v_1_0_73_0

Open up the SH5 Patches
I dont want the CO2 bugfixes enabled so i dont enable them .

Open up the collision patches and enable all .

Open up the Sim patch and i dont enable the CO2 patch because i dont want it enabled .
Close the Sim patch and open it up again to check it .
Torpedo dud fix change 1 is disabled (i didnt do it) .
Enable the Torpedo dud fix change 1 and close the Sim patch .
Open the Sim patch again to check it and now CO2 change 1 fix is enabled (i didnt do it).

[TheDarkWraith]

Originally Posted by sober

Using TDW_GenericPatcher_v_1_0_73_0

Open up the SH5 Patches
I dont want the CO2 bugfixes enabled so i dont enable them .

Open up the collision patches and enable all .

Open up the Sim patch and i dont enable the CO2 patch because i dont want it enabled .
Close the Sim patch and open it up again to check it .
Torpedo dud fix change 1 is disabled (i didnt do it) .
Enable the Torpedo dud fix change 1 and close the Sim patch .
Open the Sim patch again to check it and now CO2 change 1 fix is enabled (i didnt do it).

Excellent observation/catch I had two patches who had identical changes (one of the changes in each patch was identical) Thus when you disabled one it affected the other (but the icons were never updated for it). I removed these duplicate changes and made an Update out of them

v1.0.74.0 released. See post #1

[THE_MASK]

My pleasure .

[volodya61]

Hi TDW!

Have you already searched a solution for this problem? - http://www.subsim.com/radioroom/show...postcount=1105

Thanks!

[Trevally.]

Testing new version v1.0.74.0

When Btu is sending a message re wolfpacks - it is going through the % chance to receive.
So sometimes I am not getting any messages:-

00000302 194.67671204 [6472] Intercepted stock game radio message. Routing to radio messages feature
00000303 194.67683411 [6472] Adding an available radio message for day. Message is: Be more aggressive!Bdu
00000304 196.56646729 [6472] Failed to intercept radio message - transmit once. Message was: Be more aggressive!Bdu

Should these be the same as the campaign messages and receive 100%

[TheDarkWraith]

Originally Posted by volodya61

Hi TDW!

Have you already searched a solution for this problem? - http://www.subsim.com/radioroom/show...postcount=1105

Thanks!

Haven't revised that patch yet.

Originally Posted by Trevally.

Testing new version v1.0.74.0

When Btu is sending a message re wolfpacks - it is going through the % chance to receive.
So sometimes I am not getting any messages:-

00000302 194.67671204 [6472] Intercepted stock game radio message. Routing to radio messages feature
00000303 194.67683411 [6472] Adding an available radio message for day. Message is: Be more aggressive!Bdu
00000304 196.56646729 [6472] Failed to intercept radio message - transmit once. Message was: Be more aggressive!Bdu

Should these be the same as the campaign messages and receive 100%

I'm not using my radio message engine to send these Bdu messages. I'm using the game's. Entirely different implementation thus entirely different results. Thus it is normal to miss some messages due to % chance kicking in.

[gap]

Originally Posted by TheDarkWraith

I can try. It would need to be in a different format though. It would need to be in the game's classname format: SSTypeVIIA, SSTypeVIIB, etc.

Okay, changing it to match SH5 class name is the least problem for me. Would it be easier for you accessing this information if I put it in columns, instead of using sections and headers? like this:

U-27	SSTypeVIIA	56.51N 14.48W	55.03N 13.45W	...
U-27	SSTypeVIIA	11	11	...
U-28	SSTypeVIIA	52.21N 13.45W	52.21N 13.45W	...
U-28	SSTypeVIIA	11	11	...
U-29	SSTypeVIIA	55.03N 16.45W	53.15N 16.45W	...
U-29	SSTypeVIIA	11	11	...
...

Originally Posted by TheDarkWraith

I can definitely assign a custom u-boat number to a dispatched sub no problem (already doing this).

Excellent

as you can see from the previous example I've duplicated the U-boat number from each first row to second rows, so that now torpedo figures match the respective u-boat coordinates (and their dates) in the same column.

One last note: for similar alignment reasons, I am using a dash symbol '-' for marking missing coordinates of subs that got at least one daily position log in a month. Indeed, when no coordinates are available during a whole month, the unit gets no entry at all in the respective file. When you come across dashes you should ignore them (unit not available), and use them only for column count.

[Dogfish40]

I feel like a dummy here, but I need to know the location of the menu.txt file. The only one I am familier with is the UI's menu txt file.
Where is the menu.txt file?
Thanks
D40

[gap]

Originally Posted by Dogfish40

I feel like a dummy here, but I need to know the location of the menu.txt file. The only one I am familier with is the UI's menu txt file.
Where is the menu.txt file?
Thanks
D40

data/Menu

[Dogfish40]

Originally Posted by gap

data/Menu

Thanks GAP.
So, we are talking about the menu.txt file in the UI correct?!
Yes I see where it is.
Thank you GAP.

[Dogfish40]

One more question with regards to the text. Now, I have UI versions 7.1 and 7.2.
7.1 being the download page version. I notice that if I use version 7.1 that the entries end at 9987. If I tack the patcher entries on, the numbers paick up at 10025.
Should I be using the 7.2 UI version??
Thanks again.
D40

[Trevally.]

V7.2 fixes some bugs, so best to use that one.

Edit your data/menu/menu.txt file like this:-

 
Top of txt file:-
MaxStrings=11100<<<change to this
 
Bottom of txt file:-
; Independent engine controls patch
10025=Shafts
10026=Click to enable/disable speed commands for the port shaft
10027=Click to enable/disable speed commands for the starboard shaft
 
; Contact report wolfpack patch
11000=Dispatching available u-boats to your patrol area| Form group Benecke| Remain undetected and in patrol line ahead of convoy|Send status reports| |Bdu
11001=All available u-boats have been dispatched to your patrol area and will form patrol line ahead of convoy| From now on keep radio silence, except for important tactical messages. | |Bdu
11002=u-boats in your area have received instructions to form group Umbau| Patrol in line to the front of convoy| Contact keeper, send bearing signals| |B.d.u
11003=Steer to form patrol line to the front of convoy| Send bearing signals as boats arrive| |Bdu
11004=Form group Wohlgemut|  Contact keeper send signal bearings to form line in front of contact| Further details to follow| |Bdu

;Wolfpack request denied
11010=No boats are within your patrol area|Act as lone boat| |Bdu
11011=No support within range|Be more aggressive| |Bdu
11012=Contact report received|Act on own data| |BdU
11013=Be more aggressive!| |Bdu
11014=Attack contact| |Bdu

; Reports from dispatched subs
11020=Contact keeper continue to send bearing signals|Group act on own data|Take every opportunity to attack
11021=Convoy in sight|Signal bearing sent|Moving to attack port side
11022=I believe to have made contact with the convoy|Sending bearing signals|Act according to own data|Attacking at full speed
11023=Requesting bearing signal from contact keeper
11024=Beacon signals lie in the line of approach according to dead reckoning.|Attacking far side of convoy
 
;END OF FILE

Paste the green txt into your file

[Dogfish40]

Originally Posted by Trevally.

V7.2 fixes some bugs, so best to use that one.

Edit your data/menu/menu.txt file like this:-

 
Top of txt file:-
MaxStrings=11100<<<change to this
 
Bottom of txt file:-
; Independent engine controls patch
10025=Shafts
10026=Click to enable/disable speed commands for the port shaft
10027=Click to enable/disable speed commands for the starboard shaft
 
; Contact report wolfpack patch
11000=Dispatching available u-boats to your patrol area| Form group Benecke| Remain undetected and in patrol line ahead of convoy|Send status reports| |Bdu
11001=All available u-boats have been dispatched to your patrol area and will form patrol line ahead of convoy| From now on keep radio silence, except for important tactical messages. | |Bdu
11002=u-boats in your area have received instructions to form group Umbau| Patrol in line to the front of convoy| Contact keeper, send bearing signals| |B.d.u
11003=Steer to form patrol line to the front of convoy| Send bearing signals as boats arrive| |Bdu
11004=Form group Wohlgemut|  Contact keeper send signal bearings to form line in front of contact| Further details to follow| |Bdu
 
;Wolfpack request denied
11010=No boats are within your patrol area|Act as lone boat| |Bdu
11011=No support within range|Be more aggressive| |Bdu
11012=Contact report received|Act on own data| |BdU
11013=Be more aggressive!| |Bdu
11014=Attack contact| |Bdu
 
; Reports from dispatched subs
11020=Contact keeper continue to send bearing signals|Group act on own data|Take every opportunity to attack
11021=Convoy in sight|Signal bearing sent|Moving to attack port side
11022=I believe to have made contact with the convoy|Sending bearing signals|Act according to own data|Attacking at full speed
11023=Requesting bearing signal from contact keeper
11024=Beacon signals lie in the line of approach according to dead reckoning.|Attacking far side of convoy
 
;END OF FILE

Paste the green txt into your file

Great, that confirms Version 7.2.
Thanks much Trev!