Normally Antivirus Programs "behave" like that. When you start something (known exe changed) which the don't know or false identify them as Threat they block any kind of going further. Stupid but so they work. But I believe that was ruled out already? (make a new exception of the new egs.exe)
Finaly got it working by launching the game directly with the exe instead of through steam or the launcher program. In my case this is C:\Program Files (x86)\Steam\steamapps\common\Empyrion - Galactic Survival\Client\Empyrion.exe This time I got the usual complaint from my firewall and after granting permission the works and can now be launched for the launcher, the game exe. or steam with out issue. I can honestly say I have no idea what happened here or why launching the game directly fixed things but it works now.
Simply solution to it - Don't trust WIN to work "appropriate" but do it yourself instead. I am sure you got blocked by the Firewall in the first place. Without telling you.
Same problem here. Got through the suggested options, nothing works. All came up after 11.5 Patch. The game worked fine 36 hours ago. Updated GPU drivers and deactivated antivirus or windows defender. Same. Uninstalled, cleaned and reinstalled. Same. Launching through the expyrion.exe did not work either. Deactivated firewall and antivirus and launch through the .exe combo did not work. Windows 10, 8 GB RAM Version: Direct3D 11.0 [level 11.1] Renderer: NVIDIA GeForce GTX 1050 (ID=0x1c8d) Vendor: VRAM: 4031 MB Basically here is the sequence of events : - Launching game (via steam or directly) - Full screen launch - Loading - Loading stops - The game goes on high RAM use - In process manager it goes from no anwser to suspended multiple times - This pops up - it turns to this - Game crashes - Unity crash handler on process manager takes on and crashes - Window error journal turns on and writes it on. Logs from windows errors give up this (pardon the french) ____________________________________________________________________________________________ Nom de l’application défaillante : Empyrion.exe, version : 2019.2.14.56654, horodatage : 0x5dd53125 Nom du module défaillant : UnityPlayer.dll, version : 2019.2.14.56654, horodatage : 0x5dd532b4 Code d’exception : 0xc0000005 Décalage du défaut : 0x000000000046f2d4 ID processus défaillant : 0x26fc Heure de démarrage de l’application défaillante : 0x01d5b1949f9276bb Chemin de l’application défaillante : C:\Program Files (x86)\Steam\steamapps\common\Empyrion - Galactic Survival\Client\Empyrion.exe Chemin du module défaillant : C:\Program Files (x86)\Steam\steamapps\common\Empyrion - Galactic Survival\Client\UnityPlayer.dll Code de rapport : cef01238-8f27-467c-a3c4-eafef715d020 _________________________________________________________________________________________________ So something to do with the unityplayer.dll Going into empyrion error files, we got this : __________________________________________________________________________ UnityPlayer.dll caused an Access Violation (0xc0000005) in module UnityPlayer.dll at 0033:ab14f2d4. Error occurred at 2019-12-13_032124. C:\Program Files (x86)\Steam\steamapps\common\Empyrion - Galactic Survival\Client\Empyrion.exe, run by WaMaW. 93% physical memory in use. 8111 MB physical memory [542 MB free]. 5631 MB process peak paging file [5630 MB used]. 2868 MB process peak working set [2807 MB used]. System Commit Total/Limit/Peak: 13480MB/19887MB/13751MB System Physical Total/Available: 8111MB/542MB System Process Count: 239 System Thread Count: 2882 System Handle Count: 105630 Disk space data for 'C:\Users\WaMaW\AppData\Local\Temp\Eleon Game Studios\Empyrion - Galactic Survival\Crashes\Crash_2019-12-13_082119002\': 26859274240 bytes free of 254863732736 total. Read from location 0000000000000000 caused an access violation. ________________________________________________________________________ From the other error file : ________________________________________________________________________ Setting up 4 worker threads for Enlighten. Thread -> id: 29f8 -> priority: 1 Thread -> id: 5654 -> priority: 1 Thread -> id: 2e70 -> priority: 1 Thread -> id: 44ec -> priority: 1 Unloading 4 Unused Serialized files (Serialized files now loaded: 0) UnloadTime: 7.524100 ms 13-08:20:50.616 03_20 -LOG- EAC: Not configured 13-08:20:51.562 03_20 -LOG- Args: Client/Empyrion.exe -logFile ../Logs/2754/Client_191213-032043-77.log Unloading 387 unused Assets to reduce memory usage. Loaded Objects now: 4761. Total: 5.874600 ms (FindLiveObjects: 0.382300 ms CreateObjectMapping: 0.156300 ms MarkObjects: 5.200300 ms DeleteObjects: 0.134700 ms) Searching for compatible XInput library... Found Xinput1_4.dll. 13-08:20:54.068 03_20 -LOG- Local player 76561198045603191/'wario' WARNING: Shader Unsupported: 'Hidden/Nature/Terrain/Utilities' - All passes removed WARNING: Shader Did you use #pragma only_renderers and omit this platform? ERROR: Shader Shader is not supported on this GPU (none of subshaders/fallbacks are suitable)WARNING: Shader Unsupported: 'Hidden/Nature/Terrain/Utilities' - Setting to default shader. 13-08:21:15.758 03_21 -LOG- Voxelizing took 608ms, voxels=147155, shapes=1259, mem=644kB Crash!!! So, i am far from a specialist but it seems to me that something is going on when loading the shader "utilities". I updated the drivers but the problem persists. Anything new added to the terrain/utilities ? Copying unityplayer from dedicated server to main client did nothing to solve the issue. Hope it helps, Have a good day,
Shader issue is also to be found by those Players whose Game runs normal. So that can be left out. The other thing I noticed is that the majority of you have WIN 10 (one running Win 7). I would suggest to try the way @Inappropriate has found and post your findings here so the Devs can follow/root out was was already tried.
Tried, did nothing. If not with the shader, something with the activity of the unityplayer.dll is blocked by windows, i don't think it is by the firewall or the antivirus, seems like it is trying to get access to a secured location (Read from location 0000000000000000 caused an access violation.) From elsewhere : The actual error is a general protection fault because the native code tries to read from an invalid memory address (specifically 0x0). I can confirm that the offending code at the current program counter is part of the Unity.exe. However it's just a method which might be called from somewhere. It's one of the parameters which are actually 0 (the RDI / edi register) The closest i could find : https://forum.juce.com/t/solved-unity-plugin-crashes-unity/30237/13 So possibly on the dev side ? Will see what the devs think of it. Thanks for the reply ;-)
Hey, i finaly got an error in \AppData\Local\Temp\Eleon Game Studios\Empyrion - Galactic Survival\Crashes here it is ! I'm off working this day ... I'm sad cannot play. My wife makes me clean the house, make diner, HELP ME !
We're looking into it still & will attempt a fix for it soon. I'll update here once any more info is ready.
And we wait with full anticipation... please let us know more.. I don't have to work tonight.. so I really am anxious if I can play tonight... Yours... Tumdidumdidum..... And still waiting anxiously..........
Have updated to windows 10, reinstalled game verified integrity updated graphics drivers try diferent hard drive I don't even get a error log anymore just this.. please help!
Sorry about the wait unfortunately a fix for the issue is going to be alittle longer than expected we should have something ready tomorrow if all goes well I'll update here as soon as we have something ready.
My offer still stands.... I am happy to do a one on one to help anyone and attempt to resolve this. Please feel free to DM me, or add me on Discord. Dixon Ciderbush#9687
I wanted to play this game again but it crashes on start. I get Loading text and then version number is displayed. Afterwards game is not responding and crashes.
Just to add another update the build is intended to be out tomorrow for this issue. Again apologies for the inconveniences of this. Just to say you cannot do anything it is a engine update issue.