it's related to a word called assuming....which you know what happens when you do that ;) Yep, bit me in the @ss.
The contacts are stored in an array and I assumed that new contacts would be added to the end of the array.....not so! The game adds contacts wherever it wants to in the array. So I had to adjust my code to account for this. This problem no longer exists.

I'm trying to add another feature to the map contacts but running into a little difficulty. I'm wanting to compute their lattitude and longitude. The game gives me the distance from the origin. Origin is in the Gulf von Guineea west of Kongo (you can find it on your nav map). These distances from origin are in meters. I know that a degree of lattitude is approx. 111km and a degree of longitude is approx 111km at the equator and goes to 0 at the poles. If I divide the distance the game gives me for lattitude by 111000 (in meters) the value comes close but doesn't match what the game puts in the messagebox (say for a radio contact report). The longitude part I haven't derived the mathematical formula for it yet. Can any math majors help me out here?

There is some delay between message being generated and message being delivered. How big is the mismatch?

For those saving the game and restarting for fixing sound issues try hitting Esc and then Esc again to get back into the game. 9 outa 10 times this fixes it for me and don't have to worry about saving and restarting the game. :up:

negligible

making the navigator actually work now :03: He has to keep track of every contact and update the bearing to the contact now. Bearing to contact is updated in real time. Bearings are relative to the bow of your sub. Positive bearings are clockwise and negative bearings are counter-clockwise
http://www.subsim.com/radioroom/pict...pictureid=1895

adding the option for user to change date-time-stamp format. What different formats do you all want?

mm/dd/yy time
dd/mm/yy time
mm/dd/yy military time
dd/mm/yy military time
??

looks better and better

mm/dd/yy military time

that will be my choice for my game :rock:

Ignore reality! :D The lat/long lines are 120km from each other in game, a square grid rather than the lines-on-a-globe they really are. Should make things much easier.

true they are 120km from each other but the game is factoring in geographical location into the mathematical formula it's using to derive lat and long. I used the costant 120000 (120km) and it still didn't come out right.

EDIT: ok, I have my moments.......the fractional part left over I forgot to factor as 60 minutes to a degree. I'll see what that gives.

There are 10 types of people in the world. Those that understand binary and those that don't.

Sorry.. just stray from base 10 and life gets wonky. :)

Just love that saying. :D

yep. Got it working.

Ok, the TAI information has changed. You now get the contact date-time-stamp and also the bearing to the contact (Bearing) and the heading you need to take to head to the contact (Heading):
http://www.subsim.com/radioroom/pict...pictureid=1896

I've added some information to the nav-map contacts also. Notice in this example that the messagebox's radio report's lat and long match the info displayed for the contact :rock: Bearing is the bearing from the sub's bow to the target (+ is clockwise, - is counter-clockwise, Heading is the heading you would turn to to head to the contact):
http://www.subsim.com/radioroom/pict...pictureid=1897

Bearing and heading are updated in real time. So if you turn the sub those values will change in real time.

When a contact is added to the nav-map, the original lat and long are saved with the contact. They do not get updated.

TheDarkWraith; have I told you today that I love you? :)

Great work, but maybe it would be better to say "intercept" or "Heading to target" rather than "heading" as this maybe mistakenly interpreted as the contact's heading/course?

intercept heading or intercept? I can see how heading could be misleading....