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
Waiting for ai crews in the next update too. Good works...
but we are talking about pc's and there are so many variations out there for you too think you can get a flawless 0.8 released you may want to rethink your strategy.
i will guarantee you, you would be better off releasing 0.8 in the public branch and letting us send in crash reports than to share our saved files.
this is the point of having a beta public test.
to find the bugs.
if you just want our saves then that defeats the purpose of having a beta branch.
at least in a crash report you can see what is causing the conflicts. with our pcs.
This
Thank you for sharing your perspective. We completely understand your concerns and appreciate the feedback regarding how we’re approaching this process. Let me clarify our reasoning a bit more:
The reason we’re requesting save files is not to replace the public beta testing process but to complement it. We’re focused on edge cases, particularly those related to savegame compatibility, which can be tricky to identify even with a robust beta branch. Player-submitted saves provide invaluable real-world examples that may not be covered by internal tests or developer-created savegames.
While it’s true that PC systems vary greatly, which adds complexity, this diversity also means that having access to a range of save files from players allows us to simulate and preempt potential issues before the update goes live. This can make the public beta branch more efficient by catching specific upgrade issues early, so testers can focus on broader gameplay and performance testing.
We also see the value in public beta testing and crash reports, and rest assured, these remain an integral part of our process. However, addressing certain compatibility challenges proactively with player-provided saves enhances our ability to deliver a more stable experience right from the start.
On console platforms, savegames are locked so there is no way to send developers to use any player related savegames, this is only possible for PC.
Your input is valuable, and if you’re not comfortable sharing your saves, that’s absolutely fine. The beta branch and crash reports will still help us refine the update. However, for those willing to share, their contribution can help us resolve niche issues faster and ensure smoother transitions for everyone.
Thanks again for taking the time to voice your thoughts. Your engagement is what helps us improve and deliver a better game for the community.
Because right now wave heights must be turned down if you drive a small plastic bathtube like flippy to the fishing grounds on the open atlantic. But when we gain the tier 3 boats bigger waves would be fun. If my old character inforces small waves on the game world it´s useless to further use his saves!!
-Thanks
Me too, my saves are visible in game but says they are incompatible so unable to load a saved game.
Is this going to be fixed with a patch or update because I also have a lot of time and effort invested, close to 300 million saved and the licenses to boot!
I'm not starting over