Quote:
Originally Posted by torpedobait
... I generally draw a circle 10.2 Nm around the Base indicator (anchor) and set my course to pass just inside the circle, long enough to trigger the flashing anchor symbol in the upper right of the screen. I then complete the refuel/rearm task and proceed to my next intended destination... I was not yet in the 10.2 Nm circle, so there was no way I had visual targets. I did turn off the SD/SJ radars using the "T" key. I did not check the actual radar sets to see if they were off. I have looked at them before and found that although the on/off switches light up when touched by the cursor, they did not move when pushed. clicking on either of them only lets me move the display up or down on the screen. The switches do not operate. I had to pass a mile or so beyond that 10.2 Nm circle before the sea and air contacts faded out. Still, I waited until well around Savo Island before turning on the radars with the T key (getting the appropriate message)...
|
What boat were you driving, your port, and the date, that would be all we'd possibly need, if that. If you do not have active radar sets on your boat, the <Ctrl><T> combo does nothing, and while going to the Radar Station with either the menu button, or the <J> key (be sure an look at the "SH4_Q-Ref_Card_Front.jpg" file), you will see the sets, but they do not function - there are no radar set covers as the SSI Silent Hunter originally had... I think mouse clicks on the Radar display will do as you describe, where the button on the console lights-up and you get the name of the switch showing on-screen, but then the view just rotates around as you move the mouse. Once you have operational radar, all of the buttons should work as expected.
With that, I'm going to say you most likely only have the SD air radar, and it really doesn't matter which boat you are on. I don't remember all of the particulars (it has been a few weeks ago), but it seems to me that what you describe has been worked on already... I just wish I could remember if this was an older issue, or fixed ~after~ v0.63 beta...
We'll have to await "official" notification from either s7rikeback (he's younger - surely he'll remember
) or CapnScurvy, who did the fix.
