View Full Version : SHIP SPOTTED - but no ship...
I get this occasionally trundling through the channel (western end of the channel- not the bit anywhere near Dover ;) ) using the latest GWX incarnation with the 16km dobery. Watchman calles out 'Ship spotted!' but there's nothing in sight on a clear day, except a new map contact that appears about 50 miles away in an enemy port. About 15 minutes later after a dive to 60m at ahead slow, all of a sudden I get a cuple of destroyers buzzing me.
Don't know if I'm missing something and this is correct behaviour, but it seems a little strange to me; no a bug as such, just odd.
Anyone else see this kind of thing happening? Maybe the britishers are using a primitive SOSUS (or whatever the acronym is) in the channel in '39 :lol:
This might have to do with the vampire vision that becomes noticeable when using 16 km visibility mods:hmm: SH3 visual sensor has apparently a hardcoded proportion between day and night sighting, so when you put the visibility limit to 16000 metres instead of the original 8000, the night vision also jumps way ahead:down: Mods tend to solve that through use of fog and other tricks, which give correct results in 90% of the situations (GWX and NYGM have very very elaborated visual sensors, but note that GWX default is 8km!) but sometimes it just happens.
Jimbuna
05-13-07, 05:13 AM
This should help you sort it :up:
http://www.subsim.com/radioroom/showthread.php?t=112712
Paajtor
05-13-07, 10:03 AM
I once had a similar thing, in GWX1.02...about 300km west of Ireland, I got a stationary radio-contact.
While I was shadowing a convoy, I kept an eye on it, and it stayed there, and didn't move at all.
So I thought - hey, let's check it out....maybe it's an easy prey.
Plotted a course, that would bring me at 12k from the target...the radio-contact was still there, allthough I saw no smoke.
Makes sense, I concluded...it has engine-damage, and is sending an SOS.
So I approached submerged, but saw nothing at the spot.
Went to the exact location - nothing!
Beats me what had caused this...probably a screwed save-game?
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.