AtomicTorch Studio Forums

VoidExpanse => Bug reports => Topic started by: consolegrl on May 31, 2016, 12:05:10 PM

Title: Blank Screen on Startup (Fullscreen) & Windowed Crash (Linux Gentoo 64bit)
Post by: consolegrl on May 31, 2016, 12:05:10 PM
I just bought this game because it looks great. :D
I was sad when my laptop wouldn't run it. Sure I could probably run it on my workstation, but I feel there's no reason it shouldn't work on my laptop given its history of running 3D Unity games.

Thanks in advance for looking into this,
details follow.

Game version: Steam Current (as of May 31 2016)
Game mode: N/A
Bug Location: Main Menu
Steps to Reproduce: Start the game.
Reproduction Rate: 100%
Screenshot: No need, its a black screen with the cursor on it.
Bug Description: The game goes through the AtomicTorch logo and VoidExpanse logo and then gets to the main menu. I can hear the main menu and I can here the hovering sounds of the cursor over buttons, but I can't see anything.
Mods used: None.

Other Unity Games:
(I noticed you asked this of another user so I thought I would add this section)

Logs:
http://pastebin.com/0tChZ7sB (http://pastebin.com/0tChZ7sB)

Crashdump: No Crash.

OpenGL stuff:

OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: AMD Radeon HD 6520G
OpenGL core profile version string: 4.3.13416 Core Profile Context 13.35.1005
OpenGL core profile shading language version string: 4.40
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.5.13416 Compatibility Profile Context 13.35.1005
OpenGL shading language version string: 4.40
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
Title: Re: Blank Screen on Startup (Fullscreen) & Windowed Crash (Linux Gentoo 64bit)
Post by: ai_enabled on May 31, 2016, 08:48:21 PM
Hello!

Thanks for detailed report!
Your GPU is below the minimal requirements - VoidExpanse need at least 512MB VRAM to run properly. So its very unlikely it will run the game properly. However, you should be able to open Main Menu.

Could you try the latest preview version please? Open the game properties in Steam Client, switch on "Betas" tab and select 1.6.11 in the dropdown menu. Then wait until the patch downloaded and installed.

If that still not resolves the issue, please try to add this launch option (there is a button "Set launch options" in the first tab of the Steam game properties window):
-force-gfx-direct
It will force the Unity engine to use obsolete (but more reliable) single-threaded renderer.

If the game still doesn't run properly, please upload this log file: ~/.config/unity3d/AtomicTorchStudio/VoidExpanse/Player.log

Regards!


Title: Re: Blank Screen on Startup (Fullscreen) & Windowed Crash (Linux Gentoo 64bit)
Post by: consolegrl on June 01, 2016, 10:52:27 PM
Hi, thanks for your quick response!

While my laptop may not have the minimum memory on its card, my workstation does.
My work station is a 3GB Tahiti Southern Islands card and it experiences the same problem as my laptop: the blank screen.
Interstingly, they are both ATI/AMD cards and both using the fglrx (most recent Catalyst 15.9) driver.

However, you hack of -force-gfx-direct worked so I can play it on my workstation, but I would like to run it without the hack in the future.

glxinfo for my workstation:

OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: AMD Radeon R9 200 / HD 7900 Series
OpenGL core profile version string: 4.4.13416 Core Profile Context 12.104
OpenGL core profile shading language version string: 4.40
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.5.13416 Compatibility Profile Context 12.104
OpenGL shading language version string: 4.40
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:



Cheers.
Title: Re: Blank Screen on Startup (Fullscreen) & Windowed Crash (Linux Gentoo 64bit)
Post by: ai_enabled on June 01, 2016, 10:54:28 PM
consolegrl, thanks for your feedback.
Yes, this a known issue with AMD GPUs and we're waiting for the fix from Unity team.

Regards!