![]() |
From CCIP
Quote:
|
@AVG Warhawk: Forget about all this scope "lock" stuff, has nothing to do with it.
Point is, IRL the skipper hit the Mark Button to transmit the bearing the scope/TBT (Target BEARING Transmitter) was looking at *in this moment* to the TDC / PK. Or the bearing was read out by the XO and "Marked" by the TDC operator. As it is in SHIV, the bearing will only be transmitted when you transmit any other data like speed, AOB or range (some say it will only be transmitted with range, though I'm not sure about that) - there is no seperate Mark Button for it. At first glance it might seem it is the way it is for comfort ("one less button to hit"), though it is in fact annoying when you want to aim at specific parts of the target via the crosshairs, or when you want to send the latest bearing to the TDC just before firing, which was SOP iRL. Because even if your fire solution might be not so good, when you update the bearing just before you fire, the "time" until your solution error will matter again starts anew, since the error increases with time. |
Quote:
|
Quote:
As far as I can tell, there is no difference between the skipper IRL calling out "mark", and us simply sliding out the TDC 'thingy' in the upper right and re-transmitting information. Granted, it ALSO re-transmits the set range, AoB, and speed...which, I guess, is 'unrealistic', but...what does it matter? We didn't change those values, so...??? It shouldn't effect anything in the solution but the new bearing? |
Quote:
|
Quote:
This is how it looks to me. |
Quote:
|
Quote:
|
Quote:
|
Quote:
Quote:
Quote:
That aside... what I would like a bearing transmitter to do is this. Let's assume I have a fairly good solution. My AoB is good, my speed is off but not too far off, maybe 1 knot. Over time, because I'm off by 1kt on the speed, the solution slips to the stern of the ship. If I fire my torpedos they I know they will miss astern, no doubt. I have to adjust my solution. At this point, you would say "just update the distance to target". OK, good, distance is updated, bearing is adjusted, new bearing looks good, distance is right, AoB needed to open up a bit... it didn't. If the target was on a 270 heading and I followed the steps above, the PK would now be tracking as if the target was maybe 235... I have to now manually adjust the AoB as well. It would be nice if you had a Mark button that would allow you to update the bearing and the PK says, "Oh, the ship isn't as close as I thought" and changed bearing but also opened the AoB such that the tracking PK solution is still on the 270 base course, and also adjusted distance accordingly. Basically, just a shift forward or back in the projected target path. I accept the possibility that I may be asking for a feature here that didn't exist... I honestly don't know how the thing worked in reality. But do not think for a second that I don't fully understand the trig behind the torpedo solution, or more specifically, the "constant bearing" formula. If someone knows for sure, that what I've described just wasn't a feature, I'm OK with that. But please, if you don't have first or second hand knowledge, or at least some decent resource to point to as a reference please don't post on the thread, "Nah it didn't work like that IRL". Assuming for a moment that the mark button I've described was just not a feature... then I think I'm OK with the retransmit distance as a workaround for now. I do still wish that I could quickly change bearing without also effecting distance on the PK though. I'd even settle for half... gimme just a bearing update option (that doesn't effect or require me to re-enter distance) and I'll take care of the manual AoB tweaking. Ya know now that I talk it thru a bit... maybe it does do some of this and I'm just missin it at the moment... need to go play for awhile and stop typing. Ya know, a halfway decent manual explaining how the blasted gadgets in the game worked would probably go along way to shortening these threads. |
Quote:
I think I see your point, though. You want to 'keep' the AoB, speed, and range currently entered into the PK, and just update the bearing. |
:hmm: Good discussion here though! :up:
|
Quote:
Hello Neal, nice video. Apparently that's my problem... I've been trying to hit the moving ships. Technically, if I had to critique one thing in your video I'd say you shouldn't turn the PK on until you've transmitted all 3 data points. If the PK is set for speed zero, you're OK flippin it on as you suggest. If not it's degrading your firing solution by tracking the aiming point in the wrong direction until you transmit a proper AoB. |
Quote:
Last night was very satifying, I had two DD blowing by me at 14 kts. I was 1400 yards from the first and the PK was dead on his track. One torp set on fast and one torp set on slow. My fast torp went by the bow and the slow torp caught him under the first quarter of he bow. She went down. I quickly moved the scope to the next DD, got range, AOB and speed left alone, fired two at slow....both hit and what a glorious bloom of fire and ashes:yep:. I just wish my men would cheer:oops: |
Quote:
"Hours passed. Finally I could make out a faint place on the horizon where the haze was a little darker. "Conn - bridge. Enemy in sight. Stand by for a TBT bearing!" I jammed my binoculars into the TBT, centered on the smudge, pressed the button. The skipper's rasping voice came back: "That's him. How many can you see?"" - Capt. Edward L. Beach, USN, +, describing en encounter with him as XO on the Trigger in his book "Submarine!" When the skipper says "That's him.", he did cross check the bearing which was transmitted into the TDC by Beach pressing the Target Bearing Transmitter button with what he could see of the enemy on the radar, with which they were tracking him for some time already from beyond visual range. Quote:
Really, the TDC is not that complicated or a mystery to understand. You simply entered FOUR data values independently, and could change any of those independently thereafter as often as you wished. The Position Keeper would simply project the line of the target's travel (meaning adjusting the four values based on your initial input once you get the PK running) over time and update the gyro angle accordingly to those four values you entered. Those four values were: Bearing. Range. AOB. Speed. End of story. I didn't have much time to play SHIV lately, so I'm still not sure if it's true, but some people say bearing will only be transmitted with range. If that is true, that would be not so good, since taking range requires some time and 3 clicks as opposed to hitting one button. If it is transmitted with AOB, this would be bull, too, since your AOB ENTER dial will not update once the PK is active, so if you would want to take bearing again via AOB transmission in the upper right dial, you would also re-transmit the old and outdated AOB. So the best workaround for the missing "Mark" Button would be to transmit bearing via speed, since this is the value which will most probably stays constant during observations. |
All times are GMT -5. The time now is 01:39 PM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright © 1995- 2025 Subsim®
"Subsim" is a registered trademark, all rights reserved.