Black screen issue

[The Verc]

So I tried playing the game with a controller one night, and now any time I hit start, I get a black screen. I read somewhere that starting the game with a controller connected, disconnecting the controller and then restarting the game helps but it hasn't. I've also tried deleting the file in appdata, reinstalling and even deleting the common files folder for the game and reacquiring game assets...

Is there anything else I can do? :s

[morgan]

Reboot machine, make sure Steam is running, and load the game. That seems to do it for most people.

[The Verc]

I've tried to reboot, I don't launch outside of steam, loaded game from steam, used controller, didn't use controller, changed every resolution and video setting, deleted all files, reset configs, reinstalled game, did steam file integrity check, still to no avail. Are there registry entries that might be doing this?

[HughNonymous]

Same thing is happening for me PLEASE HELP!!!

[Cùran]

I'm seeing the black screen issue on Linux (Debian GNU/Linux "Jessie" (testing)). I think I've tried all suggestions from the various threads mentioning a black screen. I see something up until I'm asked to press a button to begin playing. Afterwards I see a small statue spinning in the lower right corner for some time, music begins to play and eventully the screen is black with just the music playing.

[Cùran]

Ok, after prodding the game with GDB I'm seeing an endless SIGPWR (and sometimes SIGXCPU) being received by the game:

Program received signal SIGPWR, Power fail/restart.
[Switching to Thread 0x7fd60f6d9700 (LWP 15111)]
sem_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S:85
85      ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S: No such file or directory.
(gdb) c
Continuing.

Program received signal SIGPWR, Power fail/restart.
[Switching to Thread 0x7fd60409a700 (LWP 15133)]
sem_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S:85
85      in ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S
(gdb) c
Continuing.

Program received signal SIGXCPU, CPU time limit exceeded.
[Switching to Thread 0x7fd60f6d9700 (LWP 15111)]
0x00007fd613dd2482 in do_sigsuspend (set=0x7fd6103607f0) at ../sysdeps/unix/sysv/linux/sigsuspend.c:31
31      ../sysdeps/unix/sysv/linux/sigsuspend.c: No such file or directory.
(gdb) c
Continuing.

Program received signal SIGXCPU, CPU time limit exceeded.
[Switching to Thread 0x7fd60409a700 (LWP 15133)]
0x00007fd613dd2482 in do_sigsuspend (set=0x7fd6103607f0) at ../sysdeps/unix/sysv/linux/sigsuspend.c:31
31      in ../sysdeps/unix/sysv/linux/sigsuspend.c
(gdb) c
Continuing.

Program received signal SIGPWR, Power fail/restart.
[Switching to Thread 0x7fd60f6d9700 (LWP 15111)]
sem_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S:85
85      ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S: No such file or directory.
(gdb) c
Continuing.

Program received signal SIGPWR, Power fail/restart.
[Switching to Thread 0x7fd60409a700 (LWP 15133)]
sem_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S:85
85      in ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S

This is oddly reminiscent of radeonsi Bug #60929[bugs.freedesktop.org]. But I don't see this behaviour with other Mono-based (ie. Unity-based) games at the moment. Thus I'm not really sure, whether this is a game bug or a GPU driver bug or a combination of both.

Is there any log written by the game, that might shed further light on this? In any case, I've filed a bug against radeonsi over at Mesa's bug tracker[bugs.freedesktop.org]. Feel free to chime in, if you can provide further information.

[Cùran]

Ok, I got news. I starts to look like this is not a Mesa bug (I've closed the bug there already). Because with strace I can see the game starting to spam "Got a bad hardware address length for an AF_PACKET 16 8" the second it's stuck on the blank screen and gets those SIGPWRs/SIGXCPUs.

This behaviour is not that unknown, other Unity-based games have this as well, see e.g. http://forum.unity3d.com/threads/linux-64-standalone-got-a-bad-hardware-address-length.282402/
@morgan: Can you verify that the game was at least built with 4.5.5p4 or 4.6.0p1 and newer? In another thread it was suggested, that an older Mono Steamworks integration library might also cause this bug. I hope I've given you some pointers for further investigation

[Cùran]

This bug is fixed with 1.0.3 for me , it's the last item of the posted change log:

Fixed a unity crash enumerating network interfaces on Linux

[The Verc]

Ah I'm on a windows based platform. It was happening again for me even with the patch, but when I started a new game it worked fine. Seems that there is a method to corrupt your save file that produces the exact same result as the common black screen bug. It had something to do with the controller...

Come to think of it, it may have crashed while I was using a controller, and then the next time I played I tried keyboard and mouse. (Which resulted in the black screen bug)

[Helios]

Window mode and starting the game FROM THE DESKTOP SHORTCUT! worked for me.
good luck guys.