http://bugs.winehq.org/show_bug.cgi?id=30958
Bug #: 30958 Summary: StarForge Alpha build: Black screen due to shader compilation errors Product: Wine Version: 1.5.6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: billy65bob@gmail.com Classification: Unclassified
Created attachment 40619 --> http://bugs.winehq.org/attachment.cgi?id=40619 log of running the game, letting it load and then exiting - no WINEDEBUG variable set
The StarForge guys have put out a freely available alpha build of their game.
Attempting to run it in wine with all quality settings gives me a black screen and the console I have running in the background prints a great many errors about shader compilation, including a multi hundred line shader dump - the log is attached. The user interface and the HUD can be seen.
Relevant hardware specs GPU NVIDIA 460GT driver: nvidia 302.17
http://bugs.winehq.org/show_bug.cgi?id=30958
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |http://www.forgeplanet.net/ | |starforge_build.php CC| |dank@kegel.com
--- Comment #1 from Dan Kegel dank@kegel.com 2012-06-20 10:45:30 CDT --- The key bits of the log are:
err:d3d_shader:shader_vaddline The buffer allocated for the shader program string is too small at 65535 bytes. fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #239: fixme:d3d_shader:print_glsl_info_log (0) : error C0000: syntax error, unexpected $end, expecting ',' or ')' at token "<EOF>"
The limit you're running into is SHADER_PGMSIZE, http://source.winehq.org/source/dlls/wined3d/wined3d_private.h#L399
Can you try increasing that limit? If that helps, we could make it grow the buffer on demand. (And we should encourage the starforge guys to use shorter shaders.)
Alternately, does setting UseGLSL=disabled help? See http://wiki.winehq.org/UsefulRegistryKeys or do 'winetricks glsl=disabled'
http://bugs.winehq.org/show_bug.cgi?id=30958
--- Comment #2 from Dan Kegel dank@kegel.com 2012-06-20 23:44:32 CDT --- OK, tried it on a system with an nvidia GeForce 8500 GT, NVIDIA 295.40 drivers. Doubling SHADER_PGMSIZE does indeed get rid of the "buffer allocated for the shader program string is too small" error. Performance is unbearably slow on any settings, though. "winetricks glsl=disabled" didn't seem to change much (though it by itself should also get rid of that error message).
I don't get a black screen; I get a ghostly forest view.
http://bugs.winehq.org/show_bug.cgi?id=30958
--- Comment #3 from Kevin Meyer billy65bob@gmail.com 2012-06-21 01:37:01 CDT --- It seems I changed the offscreen renderer to backbuffer to work around another issue with another game (gives me a black screen with GLSL off and an increased PGMSIZE).
I set that back to fbo and it seems to be rendering fine with the increased shader size limit; I can see the ground, trees, various particle effects and the player... But the game's no accepting any input from my mouse outside the menus, so I'm not really in a position to test beyond that.
http://bugs.winehq.org/show_bug.cgi?id=30958
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |matteo.mystral@gmail.com
--- Comment #4 from Matteo Bruni matteo.mystral@gmail.com 2013-09-02 15:42:39 CDT --- (In reply to comment #3)
It seems I changed the offscreen renderer to backbuffer to work around another issue with another game (gives me a black screen with GLSL off and an increased PGMSIZE).
I set that back to fbo and it seems to be rendering fine with the increased shader size limit; I can see the ground, trees, various particle effects and the player...
Since cf12f51b1520546dc855e8e8e43135a06e7a0cbf (which is in Wine 1.5.25 and newer) we're dynamically extending the shader buffer as needed so the game should work out of the box. Can you please retest?
http://bugs.winehq.org/show_bug.cgi?id=30958
Kevin Meyer billy65bob@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #5 from Kevin Meyer billy65bob@gmail.com 2013-09-03 01:35:13 CDT --- Everything appears to be working for the V0.100 alpha. Performance is pretty horrendous though.
Seems some raw input patches landed in the interim as well, so the demo is fully playable.
http://bugs.winehq.org/show_bug.cgi?id=30958
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Alexandre Julliard julliard@winehq.org 2013-09-13 13:20:01 CDT --- Closing bugs fixed in 1.7.2.
http://bugs.winehq.org/show_bug.cgi?id=30958
Ian ipickert55@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ipickert55@gmail.com
--- Comment #7 from Ian ipickert55@gmail.com 2013-12-02 13:04:10 CST --- I believe that this is an issue in Alpha Protocol but I could be wrong (if i am right then this bug should not be listed as solved). Basically when I start alpha protocol it just has a black screen with no menu, mouse, sound or anything. Just black I will upload my log which has similar lines as the original one.
http://bugs.winehq.org/show_bug.cgi?id=30958
--- Comment #8 from Ian ipickert55@gmail.com 2013-12-02 13:04:48 CST --- Created attachment 46702 --> http://bugs.winehq.org/attachment.cgi?id=46702 Alpha Protocol-Black Screen Log
http://bugs.winehq.org/show_bug.cgi?id=30958
--- Comment #9 from Ian ipickert55@gmail.com 2013-12-02 13:10:57 CST --- Disregard those two comments I didnt mean to post them on this bug.
-
wine-bugs＠winehq.org