SUBSIM Radio Room Forums - View Single Post

Pisces · 07-02-14, 07:03 AM

The helmsman seems to go out for a coffee or something when he is near the commanded heading. And doesn't keep his hands on the rudder wheel until you tell him to stear to a different heading. Bug or lack of realism, I don't know what Ubisoft was thinking. Wrong for sure.

The only way to avoid this wandering of heading (likely due to numerical integration steps adding up small errors in to big ones over time) is to use waypoint placed far away on the map (on land if need be). So the helmsman won't ever be able to home into the waypoint location, but still keeps tracking the heading to it.

I remember people have tested if the boat is drifted of course by wind/weather. I don't know who any more, too long ago. But it was here in the forums for sure. It didn't seem to correlate with wind speeds and direction. There are no currents in the SH3 world (atleast not in the mission editor) so that can't be a reason either.

Maybe this can be corrected with some hardcode fixes to the sh3.exe.

07-02-14, 07:03 AM	#14
Pisces Silent Hunter Join Date: Dec 2004 Location: AN9771 Posts: 4,904 Downloads: 304 Uploads: 0	The helmsman seems to go out for a coffee or something when he is near the commanded heading. And doesn't keep his hands on the rudder wheel until you tell him to stear to a different heading. Bug or lack of realism, I don't know what Ubisoft was thinking. Wrong for sure. The only way to avoid this wandering of heading (likely due to numerical integration steps adding up small errors in to big ones over time) is to use waypoint placed far away on the map (on land if need be). So the helmsman won't ever be able to home into the waypoint location, but still keeps tracking the heading to it. I remember people have tested if the boat is drifted of course by wind/weather. I don't know who any more, too long ago. But it was here in the forums for sure. It didn't seem to correlate with wind speeds and direction. There are no currents in the SH3 world (atleast not in the mission editor) so that can't be a reason either. Maybe this can be corrected with some hardcode fixes to the sh3.exe. Last edited by Pisces; 07-02-14 at 08:11 AM.