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
Hi, thanks for answering.
HW:
RX 480 8GB OC (18.7.1 driver)
i7 3770k
12GB RAM DDR3 1886Mhz
240GB Samsung 850 EVO
WD Black 2TB
I updated everything, even tried reinstalling Windows 10... But it didn't work either.
I'm really hyped to play the game as u can see haha.
Have a nice day.
Nope, just Windows Defender. Tried disabling it too.
Tried running the game as administrator, with Windows XP(SP3) and Windows 7 for compatibility as well.
I supposed one thing you could try is renaming the OpenAL dll in the game folder, it's possible there's some issue with that OpenAL implementation and your audio drivers.
I'm sure it has to do with something on the %appdata%/Exanima folder.
1st time I launch the game (after reseting PC) nothing happens.
2nd time I get that error.
If I delete or rename Exanima folder in %Appdata% and launch the game, it repeats whats above. 1st time it does nothing, 2nd time I get the same error.
On the inside of Exanima folder I have only 1 file named "Exanima.ini", which has nothing inside. Literally. Not a single line written.
I've read throught internet that this folder has more files, but that's not the case in my scenario.
Any idea of what files are missing there? Can I manually copy them in there?
*Tried renaming/Reinstalling OpenAL, nothing happened either.
We can be pretty certain that is the problem now. I believe we had one other user report such an issue caused by security software, but they were able to solve it by changing its settings. The file writes themselves are very basic stuff, so for whatever reason the game must be denied permissions to write data to that folder.
I've tried searching for similar issues and came up with a lot of different possible causes, I can't say which might apply to your system.
I'll try to make the game handle these errors more gracefully, and you might indeed be able to get it to launch by copying pre-existing files, however the game will not be able to function if it can't write data to disk, so the problem needs to be resolved anyway.
Yeah, if that were the case, Exanima's folder wouldn't be there+the .ini file! Something's messed up here.
As I said earlier, I have Windows 10 with barely any extra software. (Running Windows 10 1511 version if this helps you somehow).
*I'm thinking now that It might have something to do with this W10 Version. I'll check out patches from 1511 to a more recent version and see what I can find.
Thank you very much for your support, top quality devs right there.
I'll let you know if I find something with this W10 Version.
Well, creating a file or folder and writing data to a file are two very distinct operations. Creating the ini file immediately preceds dumping data into it, which means that very next step is failing. This usually happens when permissions are being denied to write to that folder. Often when the windows user running the application does not have ownership of the file. In this case the path is provided by windows as the current user's, so this should not be happening.
If you have Discord you can join our server https://discord.gg/Z5aV2bF and we can chat directly, maybe even try some custom builds to debug the issue.
Anyway I think it's better to post in the GOG forums as it might be GOG specific. More details help too like what you were doing before getting the error, screenshots etc..
I moved on from 1511 version of W10 and that solved the problem for me.
It seems that the error has something to do with older versions of W10, try updating your Windows from Updates and try again.
Hope this helped u.