[Bug 21750] New: Bioshock v1.1: GL_FRAMEBUFFER_UNSUPPORTED after program crash or timeout
http://bugs.winehq.org/show_bug.cgi?id=21750 Summary: Bioshock v1.1: GL_FRAMEBUFFER_UNSUPPORTED after program crash or timeout Product: Wine Version: 1.1.38 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: mgavl69(a)juno.com Created an attachment (id=26281) --> (http://bugs.winehq.org/attachment.cgi?id=26281) Bioshock Debug Logs and glxinfo Revisiting Bioshock I came across an odd behavior if you have to Ctrl-C or 'killall Bioshock.exe' to exit when and if it hangs on exiting to the desktop and then trying to restart. If I try to restart thereafter without changing anything I'll get this output(GL_FRAMEBUFFER_UNSUPPORTED/GL_INVALID_FRAMEBUFFER_OPERATION) and a frozen opening menu screen. See attachment with debug logs and glxinfo. If I change the ORM to 'backbuffer' everything loads and displays OK. If I switch ORM back to 'fbo' I still get the error and frozen menu screen. The only cure I've found for this is to delete the ~/.wine/update-timestamp and reupdate by doing a simple 'winecfg' or 'regedit'. After that FBO detection is OK and it loads and displays normally again. :Info: kernel 2.6.33-rc8 Xserver 1.7.99.901 git master wine git master from commit 5c4d3fb5a21210f48dfb7d9c0af8a91b23dc7ac4 (2/17) nvidia 195.36.03 beta binary (also affects 190.53 the same way) geforce 6100 nforce 405 Ubuntu 9.10 x86_64 env WINEPREFIX="/home/foo/.wine" wine "D:\FOO\Bioshock\Builds\Release\Bioshock.exe" -dx9 -nointro Direct3d registry settings [Software\\Wine\\Direct3D] "DirectDrawRenderer"="opengl" "Multisampling"="disabled" "OffscreenRenderingMode"="fbo" "PixelShaderMode"="enabled" "RenderTargetLockMode"="auto" "UseGLSL"="enabled" "VertexShaderMode"="hardware" "VideoMemorySize"="256" "VideoPciDeviceID"=dword:000003d1 "VideoPciVendorID"=dword:000010de -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=21750 blaise <mgavl69(a)juno.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID --- Comment #1 from blaise <mgavl69(a)juno.com> 2010-02-17 16:13:39 --- :update: Actually it's necessary to delete/remove the Running.ini in ~/.wine/drive_c/users/foo/Application Data/Bioshock/Running.ini to get the display/program to work again normally after a crash. Deleting the ~/.wine/.update-timestamp has nothing to do with fixing the error after a crash/timeout in Bioshock. Bioshock's bug/problem. You can mark this closed/resolved. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=21750 Vitaliy Margolen <vitaliy(a)kievinfo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED Component|directx-d3d |-unknown --- Comment #2 from Vitaliy Margolen <vitaliy(a)kievinfo.com> 2010-02-17 17:57:31 --- Closing invalid -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
participants (1)
-
wine-bugs＠winehq.org