[Bug 34658] Bioshock 2 runs out of GL memory quickly

wine-bugs at winehq.org wine-bugs at winehq.org
Thu Mar 9 04:37:47 CST 2017


https://bugs.winehq.org/show_bug.cgi?id=34658

Igor <ikk_pl at yahoo.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ikk_pl at yahoo.co.uk

--- Comment #21 from Igor <ikk_pl at yahoo.co.uk> ---
Created attachment 57561
  --> https://bugs.winehq.org/attachment.cgi?id=57561
log for wine-2.3-109-g1ddf2b4

As of wine-2.3-109-g1ddf2b4, I'm able to play through the first couple minutes
of the game until a most likely unrelated crash. I'm adding the log.

I was also able to get an interesting log for the bug from a wine-staging
version applied to commit 0dc677c05fb71 - though didn't manage to reproduce it,
so I didn't capture the log to a file. There are several instances of:

fixme:d3d_shader:shader_glsl_validate_link Program <number> link status
invalid.

followed by a dump of the shader program, then hundreds of lines of:

err:d3d:wined3d_debug_callback 0x18a72550: "GL_INVALID_OPERATION error
generated. <program> object is not successfully linked, or is not a program
object.".

Maybe in the latest wine the shaders compile properly, so the bug is not
triggered, or maybe Bioshock itself badly handles shaders that fail to compile?
I'll leave that to the experts.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list