[REL] Multiple UIs for SH5 with TDC

[reaper7]

Originally Posted by TheDarkWraith

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):


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 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):


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.

Simply Amazing Stuff . I don't know how you do it.

[Sonarman]

Originally Posted by TheDarkWraith

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

Either would be fine (a simple "intercept" may be better in terms of text box length), another idea would be having the bearing stated as Red XXX when to the port side and Green XXX when to the starboard.

[TheDarkWraith]

Originally Posted by Sonarman

Either would be fine (a simple "intercept" may be better in terms of text box length), another idea would be having the bearing stated as Red XXX when to the port side and Green XXX when to the starboard.

I'll go with intercept then. I'm not too fond of changing the text color as it's sometimes hard to read against different backgrounds you can get in the TAI. I'll stick with the - meaning to port, and positive values to starboard.

EDIT:

or can remove the - altogether and add a 'P' at the end for port or 'S' for starboard?

[kylania]

I'd go with a straight relative bearing. So if it's 55 degrees to port rather than having to figure out 360 - 55 then setting that, just turn to 305 and hit heading to view. Also, P and S work for English, but it would be BB or SB for German. Best to just leave it as the relative bearing I'd say.

It's easier to plot a 305 with a bearing overlay than 55 degrees to port as well. Just my 2 cents.

[TheDarkWraith]

Originally Posted by kylania

I'd go with a straight relative bearing. So if it's 55 degrees to port rather than having to figure out 360 - 55 then setting that, just turn to 305 and hit heading to view. Also, P and S work for English, but it would be BB or SB for German. Best to just leave it as the relative bearing I'd say.

It's easier to plot a 305 with a bearing overlay than 55 degrees to port as well. Just my 2 cents.

that's what intercept is for. Intercept is bearing + current sub's heading.

Bearing is just telling you where the contact is relative to your sub.

[kylania]

Originally Posted by TheDarkWraith

that's what intercept is for. Intercept is bearing + current sub's heading.

Bearing is just telling you where the contact is relative to your sub.

I see, a direct relative bearing would be a lot more clear than having to figure out a - to relative bearing to end up with the true bearing. In this example I'm travelling on course 308. I get a contact at True Bearing 95. I'm told the Heading is 95 and my Bearing/Intercept is -213. 308 -213 = 95. But I was already told it was at bearing (true) 95?

This explains how I thought it would work:



That way there's no math for the captain to figure the Bearing and Heading and he can tell quickly from the bridge, using relative bearing, or the map, using true bearing, where the contact is.

It would also avoid the "heading" confusion, which should be something like 45 in this example. Obviously the actual heading of the contact is given behind the scenes, hence the tail, but did we want to give that exactly to the player or leave that bit of human error in?

[TheDarkWraith]

Originally Posted by kylania

I see, a direct relative bearing would be a lot more clear than having to figure out a - to relative bearing to end up with the true bearing. In this example I'm travelling on course 308. I get a contact at True Bearing 95. I'm told the Heading is 95 and my Bearing/Intercept is -213. 308 -213 = 95. But I was already told it was at bearing (true) 95?

This explains how I thought it would work:



That way there's no math for the captain to figure the Bearing and Heading and he can tell quickly from the bridge, using relative bearing, or the map, using true bearing, where the contact is.

It would also avoid the "heading" confusion, which should be something like 45 in this example. Obviously the actual heading of the contact is given behind the scenes, hence the tail, but did we want to give that exactly to the player or leave that bit of human error in?

I'll take a screenshot in game and explain everything. Heading has changed to intercept now to avoid confusion.

[Sonarman]

Originally Posted by TheDarkWraith

I'll go with intercept then. I'm not too fond of changing the text color as it's sometimes hard to read against different backgrounds you can get in the TAI. I'll stick with the - meaning to port, and positive values to starboard.
EDIT:
or can remove the - altogether and add a 'P' at the end for port or 'S' for starboard?

Sorry, I didn't actually mean the color of the figures themselves but actually to display the words "red" and "green" ahead of the figures which is what an officer of the deck might say i.e. target bearing "Red 45 sir" etc. But I like Kylania's True & Rel Bearing idea above as well, either would be great.

[TheDarkWraith]

This should explain about the contact date-time-stamps, the bearing, and the intercept:



EDIT:

went to UZO view. Now I think I understand what you all are looking for. I rotated my UZO to the target...heading indicator said 260....it would be nice to have this value already computed for us So what's the formula for determining this? I'm playing with numbers right now trying to figure it out.....

EDIT2:

the simple things elude me sometimes! True north (360) + bearing = True heading to contact (value you would rotate scope to and press heading to view)

so it looks like I need to add another item to the contacts: True bearing....

[TheDarkWraith]

True bearing added and explained:


and went to UZO view and rotated UZO to True bearing and look what I saw:

[subaxe]

true bearing working great so far


i did have a gfx glitch tough top left side
http://www.subsim.com/radioroom/pict...pictureid=1906

[kylania]

Originally Posted by subaxe

true bearing working great so far


i did have a gfx glitch tough top left side
http://www.subsim.com/radioroom/pict...pictureid=1906

That's a hopefully upcoming feature at work! Draggable speed chart, like this:

[subaxe]

ah nice glitch then
that looks sweet

looks in is data folder, ah i see speedtable

[TheDarkWraith]

Originally Posted by subaxe

ah nice glitch then
that looks sweet

looks in is data folder, ah i see speedtable

I had to get the contact date-time-stamps things working first and more importantly working correctly before moving onto anything else.

I had one suggestion for something else to be added to the contacts: how it was detected. There's only two ways (currently until I figure out the rest) I know a contact is detected. It is either detected because your sub's sensors detected it or it was added to the nav map (radio contact, or some other unknown reason(s)). I'm not quite sure what to call this new addition: Det method (detection method), By (it would follow the contact date-time-stamp...i.e: Contact spotted: 1/1/1939 0320 By: xxx), ???
Since I only know sub or something else the other part would have to be sub or other. i.e.: Contact spotted: 1/1/1939 0320 By: Sub

What's the general concensus on this one? Add it or not?

[kylania]

Originally Posted by TheDarkWraith

Since I only know sub or something else the other part would have to be sub or other. i.e.: Contact spotted: 1/1/1939 0320 By: Sub

What's the general concensus on this one? Add it or not?

For me at least the whole contact time thing was only really needed for single ship contacts. Convoy radio reports were usually listed in the message box so by the time you dropped out of TC you'd be able to account for the lead time between when it was reported to when you started plotting.

You were never able to do that with single ship contacts, so had no method of accurately plotting an intercept since you had no idea where the ship actually was. This is now fixed, yay!

Contact time for hydrophone contacts or visual contacts isn't really needed I don't think, since you can always simply ask for an update or look/listen to see where they are. The contact time thing was always just for figuring out long range intercept lead time. It'd be cool to have I guess, but not required for me as a captain.