http://bugs.winehq.org/show_bug.cgi?id=23676
Summary: Arcanum essentially unusable due to graphics errors Product: Wine Version: 1.2 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: alex.richardson@gmx.de
When playing Arcanum, the issue shown by the screenshot happens as soon as you attempt to scroll the view. It seems that it only happens when scrolling to the top, left right and down seem to be fine.
I know this did not happen with older versions of Wine ~1 year ago.
For testing purposes there is a demo of the game available here: http://www.terra-arcanum.com/downloads/
If you need any other information please tell me, I'm quite new to reporting bugs in Wine.
http://bugs.winehq.org/show_bug.cgi?id=23676
NSLW lukasz.wojnilowicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lukasz.wojnilowicz@gmail.co | |m
--- Comment #1 from NSLW lukasz.wojnilowicz@gmail.com 2010-07-20 13:36:13 --- If that didn't happen in older wine then it's regression. If so you must do regression test to find commit which broke wine. How to do this is at http://wiki.winehq.org/RegressionTesting
BTW. Where are screen-shots you mentioned?
http://bugs.winehq.org/show_bug.cgi?id=23676
NSLW lukasz.wojnilowicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|lukasz.wojnilowicz@gmail.co | |m |
http://bugs.winehq.org/show_bug.cgi?id=23676
--- Comment #2 from Alex Richardson alex.richardson@gmx.de 2010-07-20 15:49:23 --- Created an attachment (id=29728) --> (http://bugs.winehq.org/attachment.cgi?id=29728) screenshot showing error
http://bugs.winehq.org/show_bug.cgi?id=23676
--- Comment #3 from Alex Richardson alex.richardson@gmx.de 2010-07-20 15:52:59 --- It seems the screenshot was too big and I didn't notice, here a scaled down version.
The problem with finding the regression is that since it last worked, I updated my distribution and I guess quite a lot of things changed since then. I tried it with various wine versions down to 1.1.36, but they didn't work, maybe its even older. It worked when I changed from openGL renderer to gdi but then the game was so incredibly slow it no good. Should I use backbuffer or fbo for testing purposes?
http://bugs.winehq.org/show_bug.cgi?id=23676
moylanj@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |moylanj@gmail.com
--- Comment #4 from moylanj@gmail.com 2010-07-26 22:37:17 --- I am running Ubuntu 10.4 x86-64 and wine wine-1.2 from the wine repo, and have similar problems. More to the point it is INCREDIBLY ssssslllllloooooowwwww.
(I have 4GB DRAM, 4GB swap, AMD Catalyst 10.6 and a Mobile 4850 512MB GDDR3...)
other then the glacial "speed" the game seems to run fine...
*oops* I have also patched it with the unoffical res patcher to my native LCD screen size of 1680x1050 but I can't really see this causing these godawful slowdowns...
http://bugs.winehq.org/show_bug.cgi?id=23676
--- Comment #5 from moylanj@gmail.com 2010-07-26 23:04:01 --- ...forgot to mention also have video corruption as shown in the screen cap...
http://bugs.winehq.org/show_bug.cgi?id=23676
--- Comment #6 from Alex Richardson alex.richardson@gmx.de 2010-07-27 05:06:44 --- I noticed that the screen corruption disappears if you start Arcanum with the command line parameter -no3d, however then it is insanely slow when running in windowed mode (parameter -window, only with the unofficial patch). But it is playable in fullscreen mode (wine 1.2)
http://bugs.winehq.org/show_bug.cgi?id=23676
GyB gyebro69@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gyebro69@gmail.com
--- Comment #7 from GyB gyebro69@gmail.com 2012-01-14 09:35:51 CST --- Are the reported problems (screen corruption,slow performance) still present with a recent Wine version (1.3.37 or newer)? Arcanum v1.0.7.4 (without unofficial patches) runs without those issues here, using Wine-1.3.37 and a Nvidia gfx card.
http://bugs.winehq.org/show_bug.cgi?id=23676
--- Comment #8 from Alex Richardson alex.richardson@gmx.de 2012-03-28 17:16:59 CDT --- Still happening on 1.5.0. If I add -no3d it works, although CPU usage is much higher then.
I tried both with and without increased resolution, -window with a wine virtual desktop and fullscreen, and I always get those graphics errors.
Also after alt-tab escape key presses are not recognised anymore, but I guess I should open a new bug for that.
Video driver is fglrx.
Is there any log I can attach which would help? I.e. what do I have to set WINEDEBUG to?
http://bugs.winehq.org/show_bug.cgi?id=23676
Fernando Martins fernando@cmartins.nl changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fernando@cmartins.nl
--- Comment #9 from Fernando Martins fernando@cmartins.nl 2012-03-30 13:42:55 CDT --- Arcanum works fine for me. I have GoG version, nvidia drivers 260.19.06, wine 1.5.0
http://bugs.winehq.org/show_bug.cgi?id=23676
--- Comment #10 from Alex Richardson alex.richardson@gmx.de 2012-03-30 14:19:09 CDT --- Maybe an issue with fglrx then.
The corruption only happens when I scroll upwards, scrolling in other directions works fine. When some area gets redrawn due to animations that part of the screen is fine. It seems the screen fails to repaint sometimes when scrolling upwards
http://bugs.winehq.org/show_bug.cgi?id=23676
vv222 vv221.web@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |vv221.web@gmail.com
--- Comment #11 from vv222 vv221.web@gmail.com 2013-09-20 14:58:46 CDT --- I ran into this bug with Wine 1.6. Adding the -no3d switch as a workaround still works.
Arcanum GOG 2.0.0.15 + UAP 091225 ATI Radeon HD 6670 - radeon 7.2.0 - mesa 9.1.6 Debian Sid amd64 up-to-date
http://bugs.winehq.org/show_bug.cgi?id=23676
--- Comment #12 from vv222 vv221.web@gmail.com 2013-09-20 16:54:34 CDT --- The bug still happens with Wine 1.7.2, on the same configuration.
https://bugs.winehq.org/show_bug.cgi?id=23676
--- Comment #13 from Austin English austinenglish@gmail.com --- This is your friendly reminder that there has been no bug activity for over a year. Is this still an issue in current (1.7.37 or newer) wine? If so, please attach the terminal output in 1.7.37 (see http://wiki.winehq.org/FAQ#get_log).
https://bugs.winehq.org/show_bug.cgi?id=23676
mariusz.libera@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mariusz.libera@gmail.com
--- Comment #14 from mariusz.libera@gmail.com --- I can confirm this bug is still present in wine 1.7.37. Scrolling up causes graphical corruption. I have Arcanum from GOG. My graphics card is Intel HD3000 Sandybridge, Mesa 10.4.5.
https://bugs.winehq.org/show_bug.cgi?id=23676
Tim Savannah kata198@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kata198@gmail.com
--- Comment #15 from Tim Savannah kata198@gmail.com --- Hey guys, I can confirm that this is still happening, HOWEVER, there is a way around it for some people.
I have one of them laptops with an intel for standard graphics and an nvidia card which can be enabled for 3D (nvidia optimus).
What I find is that this happens when I just run wine directly, but NOT when I use "optirun wine Arcanum.exe" (this will launch arcanum using the geforce card for display, not the intel card).
When I run it through the nvidia card (and thus nvidia's libGL), I do NOT get the issue. But when I run it through the intel card and mesa's libGL, I DO get the issue.
This leads me to believe that the issue is likely with mesa's libGL, and not wine.
I get the same results using BOTH wine's implementation of dx9, and microsoft's (using the dx9 dll's as "native"), which again suggests that the issue is not within wine but mesa.
Prior to 1.9.22 I was getting a rolling warning on the console, something about "stub! texture blit not supported in software mode" I'd look up the exact message but it's gone now ( I guess was implemented between 1.9.21 -> 1.9.22 ? )
So... anyone else got the nvidia driver and can confirm it works? Anyone on just plain mesa can confirm it doesn't work? That would then support my theory.
Now as to what to do about it.... ya got me!
https://bugs.winehq.org/show_bug.cgi?id=23676
--- Comment #16 from Tim Savannah kata198@gmail.com --- Given that I can both reproduce it working and not working... if you guys think there's some way that we can handle it within wine. It COULD BE that maybe we're doing something invalid in the wined3d layer, that nvidia's libGL handles one way and mesa's handles another.
Or maybe the difference could be a feature support, i.e. maybe the nvidia card supports some extension that is being used, let's just say "GL_NV_path_rendering" (I'm picking one out of thin air that nvidia supports but mesa does not. Not saying that function is in any way related).
If we have a conditional like:
if supports(GL_NV_SOMETHING) { .. do it this way .. } else { ..emulate that function ... }
our "emulate that function" code could be broken.
I can provide a trace of wined3d, would that be the most useful thing?
https://bugs.winehq.org/show_bug.cgi?id=23676
--- Comment #17 from Tim Savannah kata198@gmail.com --- Created attachment 56022 --> https://bugs.winehq.org/attachment.cgi?id=56022 wine d3d trace using mesa
This is wine d3d trace using mesa.
https://bugs.winehq.org/show_bug.cgi?id=23676
--- Comment #18 from Tim Savannah kata198@gmail.com --- Created attachment 56023 --> https://bugs.winehq.org/attachment.cgi?id=56023 wine d3d trace using nvidia
This is the wine d3d trace using nvidia
https://bugs.winehq.org/show_bug.cgi?id=23676
--- Comment #19 from Tim Savannah kata198@gmail.com --- So I gathered trace of wined3d.
Here's what I do
1. start wine 2. a 2d menu pops up, I click "single player" then "load game", then push a button to load the game
3. Game loads, I walk around and scroll the camera.
Scrolling the camera is the issue.
On mesa, the textures don't seem to scroll with the camera sometimes, they just repeat. This causes a "blurring" effect. It's less obvious in grasslands but in cities with buildings it's easy to see the texture repeat instead of scroll. Almost like it's moving the texture, but not clearing the old position.
On nvidia, everything works dandy.
https://bugs.winehq.org/show_bug.cgi?id=23676
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #20 from winetest@luukku.com --- Do you think it's wine bug or driver bug?
https://bugs.winehq.org/show_bug.cgi?id=23676
--- Comment #21 from Tim Savannah kata198@gmail.com --- I am not sure, but I suspect it's a bug in wine.
https://bugs.winehq.org/show_bug.cgi?id=23676
WineBuG winebugs140@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winebugs140@gmail.com
--- Comment #22 from WineBuG winebugs140@gmail.com --- Could someone add a link to the demo, please? https://archive.org/download/ArcanumDemo/ArcanumDemo.rar
Maybe the name of the bug report should reflect that this is the problem with scrolling?
https://bugs.winehq.org/show_bug.cgi?id=23676
Julien Machiels iamtimscampi@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |iamtimscampi@gmail.com
--- Comment #23 from Julien Machiels iamtimscampi@gmail.com --- I added the demo link to the consolidated retail version of the game to make future testing easier for people (I merged all the minor versions, as there shouldn't be any difference in compatibility between the last retail version and the unofficial patch. GOG is still its own separate version, due to the compatibility changes they make).
I'm currently compiling a new report for the GOG version on 2.15-staging with NVidia proprietary on Xorg 1.19.3 and couldn't reproduce this.
I'll post it, then make a report for the demo and post again if I can reproduce it there.
https://bugs.winehq.org/show_bug.cgi?id=23676
Beta Version betaversiondot@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |betaversiondot@gmail.com
--- Comment #24 from Beta Version betaversiondot@gmail.com --- Created attachment 60271 --> https://bugs.winehq.org/attachment.cgi?id=60271 terminal output
Same problem with corrupted graphics on wine-3.0-rc6 with RX580/Mesa-17.2.5. -no3d flag fixes the issue but have big impact on performance.
https://bugs.winehq.org/show_bug.cgi?id=23676
Florence Birée flo@biree.name changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |flo@biree.name
--- Comment #25 from Florence Birée flo@biree.name --- Hello,
Same problem here, on Debian sid with wine-3.5 (Debian 3.5-1).
My graphic card: Intel Corporation HD Graphics 5500
The -no3d switch fix the bug, also with performances problems.
https://bugs.winehq.org/show_bug.cgi?id=23676
Nikita Lebedev nest.stuff@yandex.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nest.stuff@yandex.ru
--- Comment #26 from Nikita Lebedev nest.stuff@yandex.ru --- I can confirm the problem exists with Intel HD 4000. No flags are helping. Elementary OS 0.4.1 Loki, Wine 1.6.2
https://bugs.winehq.org/show_bug.cgi?id=23676
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #27 from joaopa jeremielapuree@yahoo.fr --- Unfortunately, the bug is still there with wine-4.8. Can an administrator put the link of the demo at the URL place? https://archive.org/download/ArcanumDemo/ArcanumDemo.rar
https://bugs.winehq.org/show_bug.cgi?id=23676
arsidze@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |arsidze@gmail.com
--- Comment #28 from arsidze@gmail.com --- I can confirm that this bug is still here. I'm running Ubuntu 18.04, WINE version 3.0.2, Intel HD 3000 with MESA drivers; the game is ran through PlayOnLinux.
As others have mentioned, the issue seems to be scrolling *up*. Here's a short imgur gallery showcasing the effect: https://imgur.com/a/seK0tF0.
The -no3d and -doublebuffer effects do not solve the issue for me.
Interestingly enough, when running 'wine Arcanum.exe -no3d -doublebuffer' from a terminal, the window is very quickly filled with this output:
0009:fixme:d3d:surface_cpu_blt Filter WINED3D_TEXF_LINEAR not supported in software blit
https://bugs.winehq.org/show_bug.cgi?id=23676
--- Comment #29 from Beta Version betaversiondot@gmail.com --- Cant reproduce this bug with wine-5.0.
https://bugs.winehq.org/show_bug.cgi?id=23676
--- Comment #30 from Beta Version betaversiondot@gmail.com --- Ok, so, for me this bug doesn't happens with vanilla Arcanum version 1.0.7.4-hotfix taken from GOG.com. This bug happens only after installation of UAP (Unofficial Arcanum Patch) taken from http://terra-arcanum.com/drog/uap.html and it happens even if i don't install HiRes Patch, that comes with UAP.
In terminal output there is one new line with UAP installed:
002b:fixme:d3d:state_linepattern_w Setting line patterns is not supported in OpenGL core contexts.
Maybe this is relevant to that screen corruption bug?
https://bugs.winehq.org/show_bug.cgi?id=23676
Kevin Meyer billy65bob@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |billy65bob@gmail.com
--- Comment #31 from Kevin Meyer billy65bob@gmail.com --- I felt like replaying Arcanum, so I had just installed the game, the unofficial patches, and the highres patch. I believe the High-Resolution patch since 2009 disables the command line arguments, so -doublebuffer is always enabled, and -no3d no longer engages the game's own software renderer. You now need to toggle those settings in the patch's ini.
I can reproduce the screen corruption when scrolling left; up, right, and down all work fine. I also get the same 2 warnings as the others. Mine doesn't look quite the same as Alex, as there's a lot of bright colours that don't belong being copied into the screen too.
I also notice that setting the OffscreenRenderingMode registry key to 'backbuffer' removes almost all of the corruption; It introduces a new issue where a lone critter's shadow is rendered green for an update when you open and close the pause menu.
I'm only guessing here, but I suspect that when scrolling leftwards with the 'FBO' mode, the data is being moved left-to-right rather than right-to-left, causing parts to get overridden and for rubbish to get copied in. Alex was probably seeing the same phenomenon, but it was going top-to-bottom instead. I don't really know enough about ddraw to guess further.
At the very least, I can also confirm that the game on native windows doesn't exhibit any such issues with the patches applied.