[REL] Solution Solver 1.3

[russ555]

Originally Posted by Hitman

Wellcome Russ

yes this will work with ANY submarine simulation, as it will simply run as separated application on your desktop. If you are missing much that's probably more because you don't estimate correctly the AOB/speed of the target. Shoot with as less Gyro Angle as possible (This tool by gutted is fabulous for that, as it gives you the 0 GA bearing), and get close. I mean REALLY close, under 1000 metres/yards

Thanks.

Yeh i think the problem is with my AoB and sometimes speed as well. I was using a method i got from a documentry i found onthese forums that said something like "the angle between the periscope and the targets heading is the AoB" so using the ingame map tools i was able to work it out.

The speed however is very hit and miss. i use the ingame feature to work this out (the one on the datapad in Sh3) however the speeds I get tend to be very random anywhere between 0 even when the target is clearly moving to 87 even though its a rusty old cargo ship

[gutted]

Originally Posted by russ555

The speed however is very hit and miss. i use the ingame feature to work this out (the one on the datapad in Sh3) however the speeds I get tend to be very random anywhere between 0 even when the target is clearly moving to 87 even though its a rusty old cargo ship

You may be a victim of documentation in this regard.

In SH3, to use the stopwatch you had to provide an initial bearing/range reading along with the AoB at that bearing... then click the stopwatch. After some time, you'd stop it and it would give you a Speed. It calculated it by how many degrees the target moved since it was started.. which is why the AOB needs to be set.

This is how it was "Supposed" to work in SHIV as well when it first came out.. and is what is described in the manual.

But in a certain patch they changed it, because it wasn't working right.

The way it works now is the stopwatch will give you an estimated course/speed of the target between two stadimeter readings. The same info you'd get if you had plotted it on the map yourself.

So you simply take a range/bearing reading.. Wait some time.. then take another range/bearing reading and hit the stopwatch to get a heading/speed returned from these two points. You can take a thrid reading and have it estimated from the current and the previous one.. and so on. Always works with the last two readings.

How accurate it is depends on how accurate you are with the stadimeter, and how long you wait between readings.

[gutted]

ARGH, just read your post again.. and it seems you are indeed using SH3, not SH4.

In this case the stopwatch could be wrong due to a bad AOB given at the start of the stopwatch process. The margin for error in the AOB setting is extremely small to get a correct speed reading. And because of this.. im glad its not that way in SHIV.