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
Have you played Thrive before? I presume that the problem would be the Godot 4 update, meaning that 0.6.5 would work for you. If you haven't played Thrive before, could you try the 0.6.5 branch on Steam? (right click Thrive and go into properties to select the "beta" version as 0.6.5).
To get more info it would take finding the Thrive logs as currently on Windows Godot 4 doesn't output errors correctly to the launcher. The logs should be in a folder at "C:/Users/YOURUSERNAME/AppData/Roaming/Thrive/logs"
Vulkan API 1.3.242 - Forward+ - Using Vulkan Device #0: NVIDIA - NVIDIA GeForce GTX 1070
This is Thrive version: 0.6.6.0 (see below for more build info)
TODO: reimplement unhandled exception logger
Startup C# locale is: en-US Godot locale is: en_US
user:// directory is: C:/Users/megan/AppData/Roaming/Thrive
Game logs are written to: C:/Users/megan/AppData/Roaming/Thrive\logs latest log is 'log.txt'
Current CPU detected as not sufficient for Thrive
CPU is missing SSE 4.1 support
CPU is missing SSE 4.2 support
Thrive requires a new enough CPU to have various extension instruction sets, see above for what is detected as missing
Detected CPU features are insufficient for running Thrive, a newer CPU with required instruction set extensions is required
Thrive will now quit due to required native library requiring a newer processor than is available
TODO: re-add harmony init
Skipping settings apply as the game should close soon
Preventing startup due to StartupActions failing
Closing Thrive "normally" due to a detected problem
"
Thrive is starting. Log output (due to buffering this is likely not in real time):
Thrive was not detected as having started correctly. Will attempt to start Thrive again, attempt number: 2
Thrive is starting. Log output (due to buffering this is likely not in real time):
Setting breakpad minidump AppID = 1779200
SteamInternal_SetMinidumpSteamID: Caching Steam ID: 76561199227952403 [API loaded no]
=================================================================
Native Crash Reporting
=================================================================
Got a UNKNOWN while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
=================================================================
Managed Stacktrace:
=================================================================
at <unknown> <0xffffffff>
at TaskExecutor:SetNativeThreadCount <0x00082>
at TaskExecutor:ReApplyThreadCount <0x00142>
at TaskExecutor:.ctor <0x0017a>
at TaskExecutor:.cctor <0x00042>
at System.Object:runtime_invoke_void <0x0007c>
at <unknown> <0xffffffff>
at ThriveNewsFeed:StartFetchingFeed <0x000e2>
at System.Lazy`1:ViaFactory <0x0008c>
at System.Lazy`1:ExecutionAndPublication <0x000f2>
at System.Lazy`1:CreateValue <0x00112>
at System.Lazy`1:get_Value <0x0002a>
at ThriveNewsFeed:GetFeedContents <0x00022>
at ThriveFeedDisplayer:CheckStartFetchNews <0x0007a>
at ThriveFeedDisplayer:_Ready <0x00432>
at System.Object:runtime_invoke_void__this__ <0x00087>
=================================================================
Note: error lines may not match up when they happened in relation to normal output due to buffering.
Error lines are any lines received from the game's stderr output stream.
ERROR: src\steamnetworkingsockets\clientlib\steamnetworkingsockets_lowlevel.cpp (2493) : Assertion Failed: SteamnetworkingSockets service thread waited 241ms for lock! This directly adds to network latency! It could be a bug, but it's usually caused by general performance problem such as thread starvation or a debug output handler taking too long.
Child process exited with code -805306369
ERROR: Restarting Thrive due to detected startup failure
Setting breakpad minidump AppID = 1779200
SteamInternal_SetMinidumpSteamID: Caching Steam ID: 76561199227952403 [API loaded no]
=================================================================
Native Crash Reporting
=================================================================
Got a UNKNOWN while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
=================================================================
Managed Stacktrace:
=================================================================
at <unknown> <0xffffffff>
at TaskExecutor:SetNativeThreadCount <0x00082>
at TaskExecutor:ReApplyThreadCount <0x00142>
at TaskExecutor:.ctor <0x0017a>
at TaskExecutor:.cctor <0x00042>
at System.Object:runtime_invoke_void <0x0007c>
at <unknown> <0xffffffff>
at ThriveNewsFeed:StartFetchingFeed <0x000e2>
at System.Lazy`1:ViaFactory <0x0008c>
at System.Lazy`1:ExecutionAndPublication <0x000f2>
at System.Lazy`1:CreateValue <0x00112>
at System.Lazy`1:get_Value <0x0002a>
at ThriveNewsFeed:GetFeedContents <0x00022>
at ThriveFeedDisplayer:CheckStartFetchNews <0x0007a>
at ThriveFeedDisplayer:_Ready <0x00432>
at System.Object:runtime_invoke_void__this__ <0x00087>
=================================================================
ERROR: src\steamnetworkingsockets\clientlib\steamnetworkingsockets_lowlevel.cpp (2493) : Assertion Failed: SteamnetworkingSockets service thread waited 309ms for lock! This directly adds to network latency! It could be a bug, but it's usually caused by general performance problem such as thread starvation or a debug output handler taking too long.
Child process exited with code -805306369
Thrive exited abnormally with an error
If the game did not start correctly, please try the Thrive launch workarounds available under "Thrive Options" in the launcher settings
This hard CPU requirement is less stringent than what is specified as the minimum system requirement CPU on our Steam store page.