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
If you have played Gerty demo before, our save file structure has changed somewhat and may be causing problems, or something has gone wrong in creating those files. Try to delete files found in these locations and run the game again:
https://docs.unity3d.com/Manual/LogFiles.html
Windows C:\Users\username\AppData\LocalLow\CompanyName\ProductName\output_log.txt
It should be possible to delete the whole Spawn Point OSK / Gerty folder.
Hopefully this helps!
Initialize engine version: 2018.1.6f1 (57cc34175ccf)
GfxDevice: creating device client; threaded=1
Direct3D:
Version: Direct3D 11.0 [level 11.0]
Renderer: NVIDIA GeForce GTX 970 (ID=0x13c2)
Vendor:
VRAM: 3992 MB
Driver: 24.21.13.9882
Begin MonoManager ReloadAssembly
- Completed reload, in 0.747 seconds
<RI> Initializing input.
<RI> Input initialized.
<RI> Initialized touch support.
UnloadTime: 1.369978 ms
WindowsVideoMedia error 0x800700ea while reading C:/SteamLibrary/steamapps/common/Gerty Demo/Gerty_Data/sharedassets0.resource
Context: CreateObjectFromByteStream
Error details: More data is available.
Track types:
0x000007FEEEE9620D (UnityPlayer)
0x000007FEEEE9BF1F (UnityPlayer)
0x000007FEEE9CB13D (UnityPlayer)
0x000007FEEE82C589 (UnityPlayer)
0x000007FEEEE6E22B (UnityPlayer)
0x000007FEEEE6EF8E (UnityPlayer)
0x000007FEEEE6325A (UnityPlayer)
0x000007FEEE829A22 (UnityPlayer)
0x000007FEEE82A6BA (UnityPlayer)
0x000007FEEE829C67 (UnityPlayer)
0x000007FEEE82AB7F (UnityPlayer)
0x000007FEEE8D85A8 (UnityPlayer)
0x00000000775659CD (kernel32) BaseThreadInitThunk
0x00000000776C383D (ntdll) RtlUserThreadStart
(Filename: Line: 2503)
WindowsVideoMedia error 0x800700ea while reading C:/SteamLibrary/steamapps/common/Gerty Demo/Gerty_Data/sharedassets0.resource
Context: CreateObjectFromByteStream
Error details: More data is available.
Track types:
0x000007FEEEE9620D (UnityPlayer)
0x000007FEEEE9BF1F (UnityPlayer)
0x000007FEEE9CB13D (UnityPlayer)
0x000007FEEE82C589 (UnityPlayer)
0x000007FEEEE6E22B (UnityPlayer)
0x000007FEEEE6EF8E (UnityPlayer)
0x000007FEEEE6325A (UnityPlayer)
0x000007FEEE829A22 (UnityPlayer)
0x000007FEEE82A6BA (UnityPlayer)
0x000007FEEE829C67 (UnityPlayer)
0x000007FEEE82AB7F (UnityPlayer)
0x000007FEEE8D85A8 (UnityPlayer)
0x00000000775659CD (kernel32) BaseThreadInitThunk
0x00000000776C383D (ntdll) RtlUserThreadStart
(Filename: Line: 2503)
https://www.failbettergames.com/sunless-skies/known-issues/
that links to here:
https://steamcommunity.com/app/495560/discussions/0/1694917906659854505/
and essentially says to install windows media feature pack (Windows 10):
https://www.microsoft.com/en-us/software-download/mediafeaturepack
and a codec pack (k-lite codec as an example):
https://www.codecguide.com/download_k-lite_codec_pack_basic.htm
Seems this is kinda similar to what Fortnite has, people suggesting to download the windows media feature pack, (I'm on win7), also it's pointless, as anyone who as windows media player, has it by default. Codecs though is more like the issue, and I don't want to mess up my codecs.
So I'm gonna just use this CodecTweakTool_615 and see if disabling or enabling some features will help.
Ok it worked when I reenabled all my media foundation 64 bit formats, if it's gonna mess with ffdshow/haali not detecting videos and microsoft insisting it's codecs, I'm gonna disable them again, or at least only enable the one that is needed for this game.
Problem is mostly with file formats that microsoft os knows about, mkv and etc. stuff that are more special don't get that problem. So most common video formats will be disabled, like mp4 and avi so that ffdshow would work properly.
At least .avi and .mp4 isn't used by the game.