http://bugs.winehq.org/show_bug.cgi?id=19913
--- Comment #3 from Jörg Höhle hoehle@users.sourceforge.net 2009-09-03 04:10:22 --- Created an attachment (id=23398) --> (http://bugs.winehq.org/attachment.cgi?id=23398) d3d_shader log from SM 2.0 commit (bzipped 33KB)
The attached +d3d_shader log may be somewhat redundant, since I had to press Esc multiple times to skip the cdv animation, brainmonster logo, intro video and then logo to eventually reach the main menu with the dark character, where I aborted using ^C.
Can you attach a +d3d_shader log?
Incredible! In wine-1.1.28, WINEDEBUG=+d3d_shader or even -all,trace+d3d_shader causes a completely black screen right from the start. This does not happen with the mentioned post-1.1.24 commit, so I used that one to produce the attached log.
I reviewed all TRACE[d3d_shader] and TRACE_ON(d3d_shader) in wined3d/ but found nothing obvious (those non-\n-terminated trace() snippets maybe?). Can you reproduce that other bug? Do you need help with it? Shall I start another round of regression testing to identify when the screen turns black?