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 had a look at our troubleshooting guide here[www.terratechgame.com].
Let us know how you get on.
Matt
SystemNotInitializedException: FMOD Studio initialization failed : Calling initialize : ERR_OUTPUT_INIT : Error initializing output device.
at FMODUnity.RuntimeManager.CheckInitResult (RESULT result, System.String cause) [0x00000] in <filename unknown>:0
at FMODUnity.RuntimeManager.Initialiase (Boolean forceNoNetwork) [0x00000] in <filename unknown>:0
at FMODUnity.RuntimeManager.get_Instance () [0x00000] in <filename unknown>:0
UnityEngine.Object:Internal_CloneSingle(Object)
UnityEngine.Object:Instantiate(Transform)
PrefabInstantiator:Instantiate(Boolean)
PrefabInstantiator:Awake()
If this is helpfull, I've allready tryed deleating my previeous saves and re-installing the game.
Hello,
After reviewing previous threads I've encountered which are similar to the described issue above perhaps one of them will be of help in the current situation.
https://steamhost.cn/steamcommunity_com/app/285920/discussions/0/1520386297686804604/#c1744482417422229071
https://steamhost.cn/steamcommunity_com/app/285920/discussions/0/1693785669866329215/#c1744479063991071986
https://steamhost.cn/steamcommunity_com/app/285920/discussions/1/1643170269574714004/#c1643170269577189622
One Describes an Audio Issue; where updating the Audio Driver's were at fault; Another seemed to be cause by "Frame-rate" monitoring software. The third seemed to be caused by an invalid OS Clock / Timezone setting.
Good Luck.