When playing Gothic everything works fine for 10 - 15 minutes, then the rendering just stops and the screen is left as it was. The game works normally (I can hear sounds from game and can blindly manipulate it). The rest of the system works just fine as well (the game is running in simulated windowed mode). Fedora 16 (Verne) x86_64 Graphic card: VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 2400 [tomason@odysseus ~]$ glxinfo |grep -i "\(render\|opengl\)" direct rendering: Yes OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD RV610 OpenGL version string: 2.1 Mesa 7.11 OpenGL shading language version string: 1.20 Using libtxc_dxtn.i686 as the game requires it to run I also tried kmod-catalyst (proprietary drivers) and running it with wine64 none of which helped.
please attach your xorg log and dmesg output. Does mesa from git help?
Created attachment 54006 [details] output of dmesg before running the game
Created attachment 54007 [details] output of dmesg after stucking
Created attachment 54008 [details] content of /var/log/Xorg.0.log before running the game
Created attachment 54009 [details] content of /var/log/Xorg.0.log after stucking
I included two versions of each for comparison. One is always from time before even starting the game, the other one was taken in the point when the game stopped rendering. I didn't try git version of drivers as it seems to be too hard. However I might try on Sunday when I hope to have more time.
Does disabling pageflipping help? Option "EnablePageFlip" "false" in the device section of your xorg.conf
No, disabling page flipping didn't help. It maybe caused the graphics to stop even faster.
(In reply to comment #1) > Does mesa from git help? Could you please point me to some tutorial as to how to do that? Thank you
(In reply to comment #10) > I also tried kmod-catalyst (proprietary drivers) and running it with wine64 > none of which helped. If the problem is the same with the proprietary drivers, then it's more likely a Gothic / Wine / configuration issue, as it's very unlikely that both drivers would have exactly the same problem.
Oh, sorry, I posted the copied the bugreport I created for wine. I tried again with correct version of proprietary drivers installed and the problem was gone. I also tried compiling the mesa drivers by tutorial on www.mesa3d.org and the game didn't even start then (gave me Access violation). I still have a few ideas how to run it on mesa from git, but it requires more try-fail attempts.
Does setting the environment variable vblank_mode=0 for the Wine process using OpenGL work around the problem? There should be a message ATTENTION: default value of option vblank_mode overridden by environment. on stderr to confirm it takes effect.
(In reply to comment #12) > Does setting the environment variable vblank_mode=0 for the Wine process using > OpenGL work around the problem? There should be a message > > ATTENTION: default value of option vblank_mode overridden by environment. > > on stderr to confirm it takes effect. No, it doesn't help. The message was printed and the game run slower, but got stuck after 6 minutes.
New updates came: kernel 3.1.5-2.fc16 mesa-dri-drivers.x86_64 7.11.2-1.fc16 No changes, rendering stops after a few minutes (5 - 10). I can't build mesa from git. Last time I tried (using tutorial from http://www.mesa3d.org/ - ./autoconf.sh && make && sudo make install) I got error while running the game saying "Access Violation".
(In reply to comment #14) > I can't build mesa from git. Last time I tried (using tutorial from > http://www.mesa3d.org/ - ./autoconf.sh && make && sudo make install) I got > error while running the game saying "Access Violation". We can't help you with that without more information. Ideally a gdb backtrace of the crash, or at least the full output.
(In reply to comment #15) > We can't help you with that without more information. Ideally a gdb > backtrace of the crash, or at least the full output. Right. Since there is no other feedback after 3 years, I'm closing this bug.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.