[REL] Wirebreak Mod (assembly code modding)

Skwabie · 02-20-19, 09:31 PM

-WirebreakSpeedThreshold in weapons.txt now works. Wire break chance only affected by speed.

-Angled tube jams at ~10% chance (speed / 300) above 30.5 knots.

-Snake search pattern changed to much narrower. Default is 10deg/sec for 9 seconds turns. Changed to 2 deg/sec turn for 20 seconds.

-Torpedo vertical homing algorithm changed to pure pursuit. - By default it was only altitude difference based and has nothing to do with slant range. Torpedoes thus are mostly immune to large height difference/maneuver when homing.

-Torpedo run deep depth set to 200ft above sea floor, or 1000ft, whichever is shallower.

-“Advanced” torpedoes (sensor angle >=55 deg) reject wrecks, whales and oilrigs, and have a routine to evade if the target it locks on to is destroyed by another torpedo: stop homing - dive to run deep depth – snake search. Exception: countermeasure homing when target destroyed or evaded, upon which it will only circle search.

-AI launched torpedoes with sensor range above 2700yards will use drive through on jam. Below 2700 – drive around jam. By default AI torp drivethrough/drive around is based on chance. Player launched torpedoes: drive through jam on passive homing, drive around jam on active homing.

-AI launched torpedoes: sensor angles < 45 deg – snake; sensor angles between 45 and 55 deg – chance for either snake or straight; sensor angles > 55 deg – straight search.

-Player ASW missile torpedo will dive to depth of closest enemy at drop point and trigger AI reaction, and can also target surface ships.

-Sonar ping lines fade much slower so can get a solid bearing out of it.

-Max number of helos increased to 8 and min number ~ half of TF total. More chance for 8 if total helo count above 8. Initial patrol radius increased.

-Fixed wing aircraft is much less sticky.

-Enemy torpedoes can hit surface ships again.

-Mission start spawn range increased, by decreasing sonar contact strength requirement.

-AI detection range against player missile is largest at missile launch. Missiles have size factor 0.4 within launch +7 sec (booster is bright and lotta smoke), 0.2 outside launch +7 sec, 0.25 beyond waypoint. – Don Kay search radar range 50k yards, so launch detection 20kyds, missile detection 10k, active missile 15k. AI will only counter fire if launch detection. Largely decreased radar detection points on player by detecting player missiles.

Small tweaks against other AI... simplifications.

update:

-Fixed player ASW missile bug.
-Restored helicopter navigation.
-Player Mast radar returns reduced.
-Player visual range bumped.
-Periscope max zoom factor set to x64.

update2:

-Fixed torpedo deep run depth bug under surface ice.

-Ping lines fade a little faster.

-New entry in config.txt:
HeloMADMultiplier
Gives helicopters a MAD detection range multiplier so they are not completely useless - or not, default is 1... In config.txt it would look like (7.5 my own setting)

Code:

...
MADDetectionRangeInYards=400
HeloMADMultiplier=7.5

-Simulates wide aperture flank array. New entries in sensors.txt:

SonarWAARange -- range of the WAA, ala 15000 yds for the Seawolf.
SonarWAATMARate -- Sol increase rate due to angle rate while in WAA range.
SonarWAATMABaseSol -- absolute Sol increase rate while in WAA range.

In sensors.txt it would look like

Code:

SonarModel=usn_an_bqq_10
SonarType=ACTIVE/PASSIVE
SonarFrequencies=L,L
SonarActiveSensitivity=32
SonarPassiveSensitivity=46
SonarBaffle=150
SonarNoisePerKnot=1
SonarOutput=235
SonarWAATMARate=10
SonarWAARange=15000
SonarWAABaseSol=5

With above settings perfect Sol can be achieved in 5-10 time units once within 15000 yds.

On the target data page, once target is in WAA range the RNG readout turns cyan:

If the WAA cannont get a reading but the estimated range is within WAA range, the RNG readout turns yellow, indicating the estimate is false.

update3:

-New entry in \ColdWaters_Data\StreamingAssets\override\hud\defa ult.txt
PingLineFadeRate=
Changes tactical map ping line fade rate.
Game default is 0.5.

-New keystrokes:
-Stop Time Compression; Start Time Compression. Original “Set Time Compression” key renamed to “Toggle Time Compression”.
-Previous Tube.
-Previous Contact.
-Increase depth; Decrease depth. Changes depth control on helm panels by 50ft, works just like mouse clicking dive controls in the default game. Mouse control now changes depth on helm by 10ft intervals.
-Signature List Forward 5; Signature List Backward 5. Cycles through targeting list on the signature panel by 5 on each key press.

-MaxPitchAngle for missiles in weapons.txt all changed to 7.

update4:

description in post

Link

Install:

1. Extract.

2. Backup all.

3. Extract and overwrite.

4. Keybinding in game options no longer works with expanded keylist. Better manually edit options.txt for new key assignments.

How?

Reflector (eating ramens this spring..) + Reflexil
dnspy (awesome)
MS Visual Studio
A guide on steam

02-20-19, 09:31 PM	#1
Skwabie Mate Join Date: Dec 2016 Posts: 51 Downloads: 31 Uploads: 0	Wirebreak Mod + North Atlantic 2000 -WirebreakSpeedThreshold in weapons.txt now works. Wire break chance only affected by speed. -Angled tube jams at ~10% chance (speed / 300) above 30.5 knots. -Snake search pattern changed to much narrower. Default is 10deg/sec for 9 seconds turns. Changed to 2 deg/sec turn for 20 seconds. -Torpedo vertical homing algorithm changed to pure pursuit. - By default it was only altitude difference based and has nothing to do with slant range. Torpedoes thus are mostly immune to large height difference/maneuver when homing. -Torpedo run deep depth set to 200ft above sea floor, or 1000ft, whichever is shallower. -“Advanced” torpedoes (sensor angle >=55 deg) reject wrecks, whales and oilrigs, and have a routine to evade if the target it locks on to is destroyed by another torpedo: stop homing - dive to run deep depth – snake search. Exception: countermeasure homing when target destroyed or evaded, upon which it will only circle search. -AI launched torpedoes with sensor range above 2700yards will use drive through on jam. Below 2700 – drive around jam. By default AI torp drivethrough/drive around is based on chance. Player launched torpedoes: drive through jam on passive homing, drive around jam on active homing. -AI launched torpedoes: sensor angles < 45 deg – snake; sensor angles between 45 and 55 deg – chance for either snake or straight; sensor angles > 55 deg – straight search. -Player ASW missile torpedo will dive to depth of closest enemy at drop point and trigger AI reaction, and can also target surface ships. -Sonar ping lines fade much slower so can get a solid bearing out of it. -Max number of helos increased to 8 and min number ~ half of TF total. More chance for 8 if total helo count above 8. Initial patrol radius increased. -Fixed wing aircraft is much less sticky. -Enemy torpedoes can hit surface ships again. -Mission start spawn range increased, by decreasing sonar contact strength requirement. -AI detection range against player missile is largest at missile launch. Missiles have size factor 0.4 within launch +7 sec (booster is bright and lotta smoke), 0.2 outside launch +7 sec, 0.25 beyond waypoint. – Don Kay search radar range 50k yards, so launch detection 20kyds, missile detection 10k, active missile 15k. AI will only counter fire if launch detection. Largely decreased radar detection points on player by detecting player missiles. Small tweaks against other AI... simplifications. update: -Fixed player ASW missile bug. -Restored helicopter navigation. -Player Mast radar returns reduced. -Player visual range bumped. -Periscope max zoom factor set to x64. update2: -Fixed torpedo deep run depth bug under surface ice. -Ping lines fade a little faster. -New entry in config.txt: HeloMADMultiplier Gives helicopters a MAD detection range multiplier so they are not completely useless - or not, default is 1... In config.txt it would look like (7.5 my own setting) Code: ... MADDetectionRangeInYards=400 HeloMADMultiplier=7.5 -Simulates wide aperture flank array. New entries in sensors.txt: SonarWAARange -- range of the WAA, ala 15000 yds for the Seawolf. SonarWAATMARate -- Sol increase rate due to angle rate while in WAA range. SonarWAATMABaseSol -- absolute Sol increase rate while in WAA range. In sensors.txt it would look like Code: SonarModel=usn_an_bqq_10 SonarType=ACTIVE/PASSIVE SonarFrequencies=L,L SonarActiveSensitivity=32 SonarPassiveSensitivity=46 SonarBaffle=150 SonarNoisePerKnot=1 SonarOutput=235 SonarWAATMARate=10 SonarWAARange=15000 SonarWAABaseSol=5 With above settings perfect Sol can be achieved in 5-10 time units once within 15000 yds. On the target data page, once target is in WAA range the RNG readout turns cyan: If the WAA cannont get a reading but the estimated range is within WAA range, the RNG readout turns yellow, indicating the estimate is false. update3: -New entry in \ColdWaters_Data\StreamingAssets\override\hud\defa ult.txt PingLineFadeRate= Changes tactical map ping line fade rate. Game default is 0.5. -New keystrokes: -Stop Time Compression; Start Time Compression. Original “Set Time Compression” key renamed to “Toggle Time Compression”. -Previous Tube. -Previous Contact. -Increase depth; Decrease depth. Changes depth control on helm panels by 50ft, works just like mouse clicking dive controls in the default game. Mouse control now changes depth on helm by 10ft intervals. -Signature List Forward 5; Signature List Backward 5. Cycles through targeting list on the signature panel by 5 on each key press. -MaxPitchAngle for missiles in weapons.txt all changed to 7. update4: description in post Link Install: 1. Extract. 2. Backup all. 3. Extract and overwrite. 4. Keybinding in game options no longer works with expanded keylist. Better manually edit options.txt for new key assignments. How? Reflector (eating ramens this spring..) + Reflexil dnspy (awesome) MS Visual Studio A guide on steam Last edited by Skwabie; 10-13-20 at 03:25 PM.