[REL] SH4 - Flavored to Taste (Updated 12 Apr. 07)

[Ducimus]

It makes me wonder if SH4 radar problems are bugs or features .
Might explain why the radar breaks after completing the first mission!
Or, why the radar switches on/off !!!!

After 1.2 is released, I'm wondering if you'd consider lowering the ProbInsideArc.
I'm going to play with the radar some more after it's released...
Perhaps this change ??? :
Radar uses crew efficiency=false [change to true]
ProbInsideArc = 0.75

I was thinking about it. Only reason i don't right now is because, well, no reason to make flakey an already flakey radar. When its 100% nailed down as to how to make it work 100%, tip top shape without error - thats when its time to see about adding back some random variations in its performance i would think. The best way to do that is to lower the percise range, and then play with the ProbInsideArc variable as you've cited. Increasing the surface factor would help too.

Alot of things all tie in together if you consider the whole experience. Depending on how radar and visual sightings work out, im struggling with myself right now to keep, or remove the aircraft speed reduction. Im also wondering if i should change the variables in aircraft bombs again so they go deeper before exploding. (right now they only expode randomly down to 10 meters)

[Ducimus]

Note to self:
Convert SJ radar to these ranges:
http://www.hnsa.org/doc/radar/part4.htm#pgSJ-9

[CruiseTorpedo]

What you've done for the rest of us so far is great, I was getting frustrated with SH4 especially with the radar, now that it's getting better, the AI isnt so dumb and blind, yet they're not super human, it's a great improvement! Keep it up and thank you!!

[LZ_Baker]

Could you add in the fix so you can open all the torpedo tubes at once? Would be an excilent feature to have.

http://www.subsim.com/radioroom/showthread.php?t=111616

[Ducimus]

Originally Posted by LZ_Baker

Could you add in the fix so you can open all the torpedo tubes at once? Would be an excilent feature to have.

http://www.subsim.com/radioroom/showthread.php?t=111616

Good idea. I keep forgetting about that.

[Engel]

After Patch 1.2 it seems the buttons you made for "Identify Target" and the other custom buttons are no longer available since 1.2 added some more buttons to the attack Periscope button bar.
Can you confirm that?

BTW: I found some interessting stuff in the commands.cfg
[Cmd344]
Name=WP_Solution_to_target
Ctxt=1
MnID=0x3F130003
Str=1074

[Cmd346]
Name=WP_Compute_solution
Ctxt=1
Str=1076

[Cmd347]
Name=WP_Report_tubes_status
Ctxt=1
MnID=0x3F150002


I assigend a key to CMD344 but it seems it does nothing. It gives you a feedback in the textbox though.

[Ducimus]

Thanks, ill look into it. Ive reworking the mod now. Hopefully ill have a new version up sometime late tonight or tommrrow.

[Barkhorn1x]

Originally Posted by Ducimus

Thanks, ill look into it. Ive reworking the mod now. Hopefully ill have a new version up sometime late tonight or tommrrow.

You are fast my man!!

[Ducimus]

Operative word being "hopefully".

Thankfully some aspects remain unchanged, unfortuntly most of aspects ARE changed.
The plus side is since i documented most everything, reapplying changes (as necessary) to the updated files shouldnt be as much of a chore as the first time around.

Alot of changed i made previously in regard to sub damage ill be tossing out for the time being.

[LZ_Baker]

Can't wait mate!

[Mraah]

Originally Posted by Ducimus

Thanks, ill look into it. Ive reworking the mod now. Hopefully ill have a new version up sometime late tonight or tommrrow.

Ducimus,

I made a new Sensors_sub_US Tweakfile if you haven't already. Pasted to end of this post. Appears you have to go back and "search" for everything again for 1.2 SIM file.

Noted changes to SD and SJ :

Early_SD
PreciseRange = 10000
MinHeight = 100
MaxHeight = 5000
ProbInsideArc = 0.85

Late_SD
MinHeight = 80
MaxHeight = 5000
ProbInsideArc = 0.9

ALL SJ
MaxHeight = 80

This new change almost fits the min_height data of aircraft SIM files.

AFB_A6M2_Zero
min_height = 50

ALBS_G4M_Betty
min_height = 5

ALBS_H6K
min_height = 50

ALBS_H8K
min_height = 100


Without doing any tests, in theory, using default 1.2 data, you should be able to detect an H8k beyond 10,000 m, the remaining aircraft at precise range. Also note, they never changed the ElevationMax data ... radar contacts still lost when sub heading south.

Also note, the Max_Height change. Back in my earlier tests (1.1) I played with max height for the SD without changes any other data except ProbInsideArc = 0... my findings :

1. MaxHeight=2500 the A6M2 was detected at 21,100m +/- 400m
2. MaxHeight=50 the A6M2 was detected at 14,600m +/- 100m

My conclusion was that MaxHeight determined the sensitivity (ie range) with a constant Surface=100. When I tested the SD using ONLY a change to the Surface value I got the same result ...

1. Surface=100 then A6M2 detected at 21,100m +/- 400m
2. Surface=200 then A6M2 detected at 14,600m +/- 100m

So, perhaps MIN and MAX height (if not related to actual distance above/below a certain point in space [changing the aircraft min-height may prove me wrong]) is actually a sensitivity adjustment or in radar terms RESOLUTION against some constant variable that has yet to determined.

<---- lump #1

Here's my new Sensors_sub_US file :

changes :

1. DropDownName from ref's original file added
2. More searches added for BearingMin/Max to reflect 2 entries in sonar sensors 13, 14 and 15.
3. Changed SensorType search from integer to byte. Ref's original file was integer. Since we're not changing the sensortype it hasn't caused me any problems. If you want to change the sensortype be sure to change it back to read integer.



EDIT NOTE : Be sure after pasting below that there isn't a space between the "h" and "t" at end of MinSensorHeight and MaxSensorHeight for sensors # 10-20.


Edit note : I deleted the paste below, it was broken and wrong. Sorry for bad post.

[Ducimus]

Well, heres where im at with the mod.

Things added to mod prior to patch 1.2:

- more percise bearing indicators for periscope/tbt/bino's (1.2 compatible
- medal fixes (1.2 compatible having reworked menu.txt)
- reworked gui bar with new button labels (status pendiing)


things removed after patch 1.2
- entire data/air directory
- all UPC files
- all career/flotilla files (*career start pending further examinatinon)
- all sub zon files
- US_sub_sensor file

things reworked so far:
- menu.txt
- zones.cfg

Items checked for compatiablity that are ok:
- contents of data/libary directory except sub sensor file.
- all sub cfg and sim files
- contents of data/cfg directory excepting commands.cfg

---------TODO:

HIGH priority:
- rework sub zon file
- compare commands.cfg with patch 1.2 version, rework as neccessary
- compare ordersbar.cfg with patch 1.2 version, rework as neccessary
- compare hud.tga with patch 1.2 version, rework as neccessary
- rework tweak file, and readjust radar.


MED priority
- bathtub removal
- careerstart.cfg
- move crewman at xmas tree to empty planesman position.

LOW priority
- any upgrade at an earlier date then normal. radar, ct, etc.

[Ducimus]

Mraah,

From the bottom of my heart, thank you, you just saved me a ton of time tonight.

[Frenssen]

Thank you for your efforts That radar bug was driving me crazy.

[Mraah]

Originally Posted by Ducimus

Mraah,

From the bottom of my heart, thank you, you just saved me a ton of time tonight.

Quite welcome!!!

Check for ERROR in my pasting :
Note that starting with sensor # 10 - that these lines moved the "t" at the end - one space ... could cause problem. from original post (note the t moved);

search,MinSensorHeight,18,single,>2,MinSensorHeigh t
search,MaxSensorHeight,18,single,>2,MaxSensorHeigh t

I tried to edit my post but it appears normal. So, you need to fix it after you paste to notepad to read :
MinSensorHeight
MaxSensorHeight

Rob