Stadimeter Solution by Reaper7

[reaper7]

No reset to 0. The reason is because the built SH5 on top os Sh4.

The Sh4 Targetting TDC is made up of 3 parts Range, Speed and AOB.
In Sh4 you dragged the dial to value and clicked on send to tdc for each item.

Thats still happening in SH5 even though its meant to only use the stadimeter.

Here are the buttons used in SH4 TDC

PageTorpedoSolution_RightPanel_Range_SendRangeButt on
PageTorpedoSolution_RightPanel_Range_StadimeterBut ton
PageTorpedoSolution_RightPanel_Speed_SendSpeedButt on
PageTorpedoSolution_RightPanel_AngleOnBow_SendAngl eOnBowButton

Maybe we can get them all to activate at the same time sending the correct values

[TheDarkWraith]

Originally Posted by reaper7

No reset to 0. The reason is because the built SH5 on top os Sh4.

The Sh4 Targetting TDC is made up of 3 parts Range, Speed and AOB.
In Sh4 you dragged the dial to value and clicked on send to tdc for each item.

Thats still happening in SH5 even though its meant to only use the stadimeter.

Here are the buttons used in SH4 TDC

PageTorpedoSolution_RightPanel_Range_SendRangeButt on.Visible PageTorpedoSolution_RightPanel_Range_StadimeterBut ton.Visible PageTorpedoSolution_RightPanel_Speed_SendSpeedButt on.Visible
PageTorpedoSolution_RightPanel_AngleOnBow_SendAngl eOnBowButton

Maybe we can get them all to activate at the same time sending the correct values

I got an idea.....

[reaper7]

By commenting out the following that should fix the reset to 0 problem, will give it a try.

EDIT: No good either just stopped the SH4 dials turning

[Dial56]
Name=TorpedoSolution_Temporary_AngleOnBow
Type=42; DIAL_TGT_ANG_ON_BOW
;Cmd=Set_tgt_sel_value; shared between dials 
Dial=0x43010002
CrtVal=0x43010003
NewVal=0x0
DialVal=0.1,-0.1
RealVal=180,-180; degrees
Circular=Yes
CmdOnDrag=Yes
RelativeDrag=Yes
SndStep=5
SndList=1,Menu.TDC.AngleOnBow,360
 
[Dial57]
Name=TorpedoSolution_Temporary_Speed
Type=69; DIAL_TGT_SPEED
;Cmd=Set_tgt_sel_value; shared between dials 
Dial=0x43020002
CrtVal=0x43020003
NewVal=0x0
DialVal=0.01,-8.78; 360/41 
RealVal=0,40; knots 
Circular=Yes
CmdOnDrag=Yes
RelativeDrag=Yes
SndStep=5
SndList=1,Menu.TDC.AngleOnBow,360

[John Channing]

This is better than watching the World Cup!

JC

[reaper7]

Originally Posted by John Channing

This is better than watching the World Cup!

JC

A long as it doesn't end in a draw like most games played so far.

[TheDarkWraith]

Originally Posted by reaper7

A long as it doesn't end in a draw like most games played so far.

that $%^& thing I never liked in SH4 plus I shelved SH4 5 minutes after playing it so I'm totally unfamiliar with that integrated dial. But now that you've shed some light on how it works I think we can do something good with it

[reaper7]

Originally Posted by TheDarkWraith

that $%^& thing I never liked in SH4 plus I shelved SH4 5 minutes after playing it so I'm totally unfamiliar with that integrated dial. But now that you've shed some light on how it works I think we can do something good with it

It appears that when the stadimeter is released it updates the range correctly but also updates the temp speed and temp AOB to the Speed and AOB Dials hence the reason they both reset to 0 as the temp AOB and Temp Speed are set at 0.
Tried changing the default starting value of AOB to 90 degrees instead of 0 degrees via the DialVal= in dials.cfg
And when I updated the stadimeter it reset to 90 instead of 0 .
So the game is updating with the values that have not been set up yet.

So what is needed is to update the temp AOB and temp Speed with the current set values. That way they will reset to themselves.

[Gorshkov]

Is it possible to fix stock stadimeter?

[Ducimus]

Originally Posted by reaper7

It appears that when the stadimeter is released it updates the range correctly but also updates the temp speed and temp AOB to the Speed and AOB Dials hence the reason they both reset to 0 as the temp AOB and Temp Speed are set at 0..

Sounds like that might be related to the Position Keeper from SH4.

[reaper7]

I've been doing a hell of a lot of testing and the Mast Height Problem just wasn't adding up.
As your aware from the First post I announced that I had a fix for the stadimeter bug, and after impute from others that this and that didn't work due to mast height not being sent.
I went on to getting the Sh4 Recon Manual working in SH5 with the working send mast height to TDC.
Excellent everything work perfectly, Hmmm I still wasn't convinced.

So I started doing a lot of tests on different ships at different ranges and the results did not add up. So I did a bit of searching on the SH4 forums (As SH5 is built on SH4 - what applies there applies here).

And came across this which validates my results.

Originally Posted by CapnScurvy

I know a bit about Mast Heights, Manual Targeting, the relationship between the Stadimeter reading and the Position Keeper, and what results one gets with a poor firing solution (SCAF). May I say, with some of RFB 1.52's mast heights, you couldn't hit a bull's behind with a base fiddle!!! OK, so maybe you could if you were 600 yards from target; the torpedo's don't arm themselves before 400 yards!!

I've spent a lot of time testing, calibrating, retesting, finding manual range using the stadimeter, to know the stock mast heights are on average 25-35% incorrect. Enough so that one meter (the internal game files are all in meters) on average, will produce a little less than 50 yards of difference for a manual targeting solution compared to an automatically found one. This is with the range being taken at a standard 1200 to 1300 yard distance, and with an average mast height of 19-23 meters.

If you use the auto targeting feature you can stop reading now. The relationship of correct range finding with auto targeting compared to manual targeting is like day and night. The devs developed auto targeting to keep accurate track of targets for you. In this regard they did it very well. You can still screw up, but most of the hard work is done for you. In auto targeting the game doesn't use the mast heights to find range but rather object coordinates to find the correct relationship's between one another. The game keeps track of hundreds of objects, so finding the distance between just two is a piece of cake.

In manual targeting the player makes the inputs for a firing solution. The one I'm most concerned about is mast heights since this one figure is out of the players control (it is placed in the game through the ships .cfg files), and yet it makes part of the equation for manually finding accurate range when doing it yourself. The game crunches the numbers for you, but the solution is only as good as the input figures you use.

This is exactly what I was noticing in my Results:

If I use my fix for stadimeter as in the first post I was getting good results.
Now if I use the (Send Mast to TDC) which you would imaging to give more accurate results, this was not the case it gave results close to the Non TDC ones but still a bit off.

So the game is actually using accurate results when in Auto Mode and less accurate results whan using the Send mast Height to TDC method.
The reason for this is the game measures the distance between objects (ie Ships) in Auto Mode (Accurate) while the manual mode uses the .cfg file to get the Mast Heights which are not so accurate.


What this means is the Fix for the stadimeter is NOT in "sending Mast height to TDC" but in "sending range and bearing to TDC" as in my first post.


Expect a proper Stadimeter Mod Fix soon.

[TheDarkWraith]

my solution has no problems with it, I get excellent range readings with the automatic mast height's inserted with my code. I don't understand what you're talking about now. It appears you're trying to re-invent the wheel of make something work that won't work The range is set using the stadimeter (or the TDC range dial), the bearing/AOB/etc. are set using the TDC dials. So what's this proper thing you speak of?

[reaper7]

Originally Posted by TheDarkWraith

my solution has no problems with it, I get excellent range readings with the automatic mast height's inserted with my code. I don't understand what you're talking about now. It appears you're trying to re-invent the wheel of make something work that won't work The range is set using the stadimeter (or the TDC range dial), the bearing/AOB/etc. are set using the TDC dials. So what's this proper thing you speak of?

Like everything is this game its built for automatic mode (Noob mode).
When you use auto TDC (Not sending the mast height) the game gets the distance between ships (Objects) using its own ingame measurments. The same way the Percise Sonar range works.

as quoted by capnscurvy If you use the auto targeting feature you can stop reading now. The relationship of correct range finding with auto targeting compared to manual targeting is like day and night. The devs developed auto targeting to keep accurate track of targets for you

Now When you use The Send Mast height (manual mode) your telling the engine to use the heights found in the ship.cfg files which are not 100% accurate.
The ship mast heights has always been a problem from sh3-sh5 in there accuracy at time up to 30% off in the correct height.

What this means is using 'The Send mast height to TDC' you are actually introducing a small bit of error to the results.

EDIT: I'm not saying your method is wrong. I'm saying that the Devs messep up the implementaion of the Manual Targeting method. your method is bacically the way I had it working with the SH4 recon mod for stadimeter (Result wise that is).
It would be given the exact same results.
What I'm saying like most things in this game Mauals mode is giving worse result that Auto Mode.

Both ways give me great range readings, but the Auto Mode are slightly better and more so at very long range.

And if you bypass the Send to TDC part and use the Seng rand and bearing to TDC as found on the SH4 Position keeper dial it imputs the range using Auto Mode giving better results.

I'm posting this info for everyone to use if wanted

[TheDarkWraith]

Originally Posted by reaper7

What this means is using 'The Send mast height to TDC' you are actually introducing a small bit of error to the results.

from what you're saying then using the button for it will (in the rec manual) introduces the error. Setting the mast height by code introduces no error. My range readings are spot on no matter what ship, what distance. I played with that button you're playing with for days, that whole pk thing is fubar'd to no end. It was easier just to develop a better way of doing it
Here's probably why you're getting the error you're seeing: you have to have the XO TDC in off in order to use the button you're using. The minute you turn TDC back On the internal values for range, aob, speed, etc. get fubar'd by the game.