Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Any data which is used for nautical charts is measured much more accurate (using multibeam echosounder with a resolution of down to a few cm (!!!). This data is commercial and extremely expensive to buy and use, not achieveable for a game.
If you wanted to double the resolution of a bathymetric datasets of e.g. 2 GB, the size would quadruple, e.g. raise from 2 GB to 8 GB, which is way too large for the average home PC. Of course, high resolution is only needed in coastal and estuarine waters, but this data is often classified for military reasons.
Therefore, unless people provide manually improved sections of coastline bathymetry (through the Sailaway Editor), this situation will not improve.
i have had it happen in the middle of the atlantic where a submerged submarine wound not run a ground
When I first bought the game Georgian Bay was fine. This is a bummer!
Even Liverpool, my home port with a 9m range runs me aground at high water before I get into the Mersey!!!