(Solved) Crashes at Launcher - wont load game

Every time I launch SOTA either through the launcher or if I start the application itself without the launcher I get a Unity splash screen loader (see image below) appear for a split second and disappear and then nothing happens - no crash dump, no load, no error, nothing. I have disabled all anti virus & firewalls. I've also tried to run it through the steam client and have the same thing happens. Have deleted both the local client and the steam client and done a complete reinstall with both - still receiving the same result. I've also update the video drivers - still does not make a difference. I have a pretty high end gaming rig which I've not encountered anything like this before.

 

@Sarduka welcome to the forums
it might help to know your system specs... (OS, processor, graphics etc..)

 

Have you been able to play before?

Also is your video card driver up to date?

 

Oh sorry I forgot the computer specs:
Intel i7 3.3gzh
16 GB ram
Windows 10
Nvidia GTX 980 (with latest drivers)
Also have a Acer 33in widescreen monitor (sometimes this caused issues with game resolutions)

I've not been able to get into the game on this computer (I'm a new comer to the game). I've tried to play (and ensure all files are patched) in safe mode and I've gone through a shutdown services in an attempt to see if there was a conflict. I have a Surface Pro 3 though which I happily installed and ran it (very slow though) but it installed and ran.

 

What happens if you copy all the files off your surface and run that on the desktop ?

There should also be some form of log file in the folder it’s installed in which will list some errors

 

I just tried to copy all the files across and test them on the main gaming rig - exact same issue, the splash screen above appears for a split seconds and then nothing. There no crash or anything, looks like something simply wont engage. Where would I find crash logs if any?

 

they would be in the folder you run sota from

 

Awesome thanks for that - I've found the logs but cant make heads or tails of it - there it two logs "error" and "sota_log".

the error log has this (amongst more jargon):

Shroud of the Avatar by Portalarium [version: Unity 2018.1.7f1_4cb482063d12]
UnityPlayer.dll caused an Access Violation (0xc0000005)
in module UnityPlayer.dll at 0033:ba7c4446.
Error occurred at 2018-10-14_005758.
C:\Program Files (x86)\Portalarium\Shroud of the Avatar\Shroud of the Avatar.exe, run by ******.
36% physical memory in use.
16280 MB physical memory [10307 MB free].
107 MB process peak paging file [74 MB used].
69 MB process peak working set [39 MB used].
System Commit Total/Limit/Peak: 8452MB/20640MB/28188MB
System Physical Total/Available: 16280MB/10307MB
System Process Count: 216
System Thread Count: 3316
System Handle Count: 126901
Disk space data for 'C:\Users\username\AppData\Local\Temp\Portalarium\Shroud of the Avatar\Crashes\Crash_2018-10-13_135757270\': 67619663872 bytes free of 249026191360 total.
Read from location 000000000000000E caused an access violation.
Context:
RDI: 0x0000008c795ae9d0 RSI: 0x0000000000001000 RAX: 0x0000008c795ae958
RBX: 0x0000000000000010 RCX: 0x0000008c795ae958 RDX: 0x0000000000000000
RIP: 0x00007ffcba7c4446 RBP: 0x0000000000000008 SegCs: 0x0000000000000033
EFlags: 0x0000000000010202 RSP: 0x0000008c795ae930 SegSs: 0x000000000000002b
R8: 0x0000000000000010 R9: 0x0000000000000000 R10: 0x0000000000000fff
R11: 0x0000000000000ff0 R12: 0x000000000000000e R13: 0x0000000000000000
14: 0x0000000000000000 R15: 0x0000000000000010






The Sota Logs start has this (amongst more jargon):
========== OUTPUTTING STACK TRACE ==================
0x00007FFCBA7C4446 (UnityPlayer) UnityMain
0x00007FFCBA7D114D (UnityPlayer) UnityMain
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFCBA1D1A39)
0x00007FFCBA1D1A39 (UnityPlayer) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFCBA1D1CC2)
0x00007FFCBA1D1CC2 (UnityPlayer) (function-name not available)
0x00007FFCBA1F2E56 (UnityPlayer) UnityMain
0x00007FFCBA1EE806 (UnityPlayer) UnityMain
0x00007FFCBA2057BC (UnityPlayer) UnityMain
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFCB9C6ED60)
0x00007FFCB9C6ED60 (UnityPlayer) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFCB9C70615)
0x00007FFCB9C70615 (UnityPlayer) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFCB9BA69EA)
0x00007FFCB9BA69EA (UnityPlayer) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFCB9B97BA9)
0x00007FFCB9B97BA9 (UnityPlayer) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFCBA1E190A)
0x00007FFCBA1E190A (UnityPlayer) (function-name not available)
0x00007FFCBA1E221B (UnityPlayer) UnityMain
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FF74BA61207)
0x00007FF74BA61207 (Shroud of the Avatar) (function-name not available)
0x00007FFD01ED3034 (KERNEL32) BaseThreadInitThunk
0x00007FFD03AC1461 (ntdll) RtlUserThreadStart
========== END OF STACKTRACE ===========

 

OH Wow, so after you told me where the logs were I took the crash error into google and went on the hunt for what might cause the crash. Well I found a heap of other unity based games in Steam that kept crashing and they all had one thing in common - CITRIX Receiver (I use to remote into work with). Guess what happened after I removed it.... yep im playing right now Thanks so much for your help everyone!

 

Glad you found it