Thanks Mate, helps to be on the same mission for testing purposes
As per my post here in stieblers thread:
Quote:
Originally Posted by reaper7
Hi Stiebler got your PM and thanks for the info - hope I can figure my way around OllyDebug and find the relevant info  .
Was at work today and had a thought that may be of Interest to you to add to your Asdic code.
It would be possible to make the sub harder to spot by ASDIC's when stopped and on the bottom by making MS = 80 or some relevant amount.
This would be great to add to the Defensive tactics when trying to escape destroyers when the sea floor is above crush depth.
Just bottom out and hide. 
I already have the Variable for subspeed and could find the variable for depth under keel. So if both variable = 0 then MS = 80 .
So to add to your Original Figures
Depth > 150m: MS = 100 (m2, metres squared).
Depth >100m: MS = 150
Depth >50m: MS = 200
Depth < 50m: MS = 300.
DepthUnderKeel=0 Speed=0 MS=80
If your Interested in adding this to the code I'll send you the OllyDebug Code and memory locations.
Sorry for making more suggestions, just excited by your discovery  |
I have found the Variable for Sea-Depth and its a Static Address too
Compared to usual DMA address with Pointers.
SH3Collisions.act+20550
Found the Variable for Depth under keel too but this only updates when the command is Issued, so may not be of use.
"sh3.exe"+001546C4 and 1 pointer offset 1C
Still using the Current Depth and the SeaDepth would suffice to know if the Sub in on the bottom. If Depth<=SeaDepth then apply Sensor adjustment.
Appears the SeaDepth Figure is Bang on if it read 111M then the seabed is 111M unlike the Depth under Keel command which applies an error to the Depth.
So therefore the sub can never dive deeper then the seaDepth value. so then if Subdepth=Seadepth, U-boat is on the seafloor.