http://bugs.winehq.org/show_bug.cgi?id=33362
Bug #: 33362 Summary: Dragon Age Origins texture replaced by black Product: Wine Version: 1.5.27 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: scrimekiler@yahoo.fr Classification: Unclassified
Created attachment 44138 --> http://bugs.winehq.org/attachment.cgi?id=44138 Screenshot of texture bug
I tried Dragon Age Origins with a lot of different Direct3D settings in wine registry, but still one problem remaining : textures are sometimes replaced by black shapes, like missing texture...Sometimes it's only the armors or cloth from vendors or characters who are replaced by black but sometimes it's like 50 % the game textures.
Currently using wine 1.5.27 and Dragon Age Origins 1.5
http://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #1 from Austin English austinenglish@gmail.com 2013-04-10 12:42:22 CDT --- Please attach terminal output.
What graphics card/drivers?
http://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #2 from scrimekiler@yahoo.fr 2013-04-11 05:27:34 CDT --- (In reply to comment #1)
Please attach terminal output.
What graphics card/drivers?
Nvidia GT 630, proprietary drivers 313.26
http://bugs.winehq.org/show_bug.cgi?id=33362
Xavier Vachon xvachon@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xvachon@gmail.com
--- Comment #3 from Xavier Vachon xvachon@gmail.com 2013-06-30 23:52:41 CDT --- I don't seem to have this in current wine (1.6-rc4). If you still have this problem with the latest version of wine, could you provide us an example of a scene where we can reproduce this, ideally in the prologue of the game? Thank you.
http://bugs.winehq.org/show_bug.cgi?id=33362
Someone scrimekiler@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Platform|x86 |x86-64 Version|1.5.27 |1.6-rc4
--- Comment #4 from Someone scrimekiler@yahoo.fr 2013-07-12 11:47:06 CDT --- (In reply to comment #3)
I don't seem to have this in current wine (1.6-rc4). If you still have this problem with the latest version of wine, could you provide us an example of a scene where we can reproduce this, ideally in the prologue of the game? Thank you.
Bug still there with wine 1.6_rc4, gentoo 64 kernel 3.8.10
You can repoduce that bug in Denerim on the market, the cloths oh the vendor become black when you go near them. I'll add some screenshots to show it better
NOTE : This bug seems to disappear with USEGLSL=disabled, which is not default wine settings.
http://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #5 from Someone scrimekiler@yahoo.fr 2013-07-12 11:53:45 CDT --- Created attachment 45206 --> http://bugs.winehq.org/attachment.cgi?id=45206 with texture bug : no texture on character cloth on left
http://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #6 from Someone scrimekiler@yahoo.fr 2013-07-12 11:54:49 CDT --- Created attachment 45207 --> http://bugs.winehq.org/attachment.cgi?id=45207 Same screenshot without the bug : texture is displayed (orange dress)
http://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #7 from Someone scrimekiler@yahoo.fr 2013-07-12 11:56:08 CDT --- compare attachment 45207 and attachment 45206 to see what the bug does
http://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #8 from Xavier Vachon xvachon@gmail.com 2013-07-12 13:05:36 CDT --- Just went around the Denerim market close to the vendors and tried pretty much all the conversation options over there, the textures are there and they work well.
Arch linux X64 nvidia 319.32 Physx installed through winetricks
http://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #9 from Someone scrimekiler@yahoo.fr 2013-07-13 05:10:51 CDT --- (In reply to comment #8)
Just went around the Denerim market close to the vendors and tried pretty much all the conversation options over there, the textures are there and they work well.
But maybe you use custom settings ? Do you have GLSL enabled or disabled ? what about the other Direct3D settings ? Something is considered as a bug if you have to set a lot of custom registry keys to make it work.
Physx installed through winetricks
PhysX is already on dragon age cd :)
http://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #10 from Xavier Vachon xvachon@gmail.com 2013-07-13 10:01:18 CDT --- (In reply to comment #9)
(In reply to comment #8)
Just went around the Denerim market close to the vendors and tried pretty much all the conversation options over there, the textures are there and they work well.
But maybe you use custom settings ? Do you have GLSL enabled or disabled ? what about the other Direct3D settings ? Something is considered as a bug if you have to set a lot of custom registry keys to make it work.
Physx installed through winetricks
PhysX is already on dragon age cd :)
I haven't modified anything in the registry, so I use wine's default settings.
http://bugs.winehq.org/show_bug.cgi?id=33362
Claudio sick_soul@yahoo.it changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sick_soul@yahoo.it
--- Comment #11 from Claudio sick_soul@yahoo.it ---
I see this as well, with Nvidia Geforce GT 650M, wine-1.7.12-141-gaa22a3c.
At the beginning of the Ostagar Tower Scenario, there are explosions on the fortress' walls which scatter debris around. The texture on the debris is often replaced by black boxes.
StrictDrawOrdering = enabled,
all the rest at default settings.
http://bugs.winehq.org/show_bug.cgi?id=33362
Felix Yan felixonmars@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |felixonmars@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=33362
Joni L-H jonilh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jonilh@gmail.com
--- Comment #12 from Joni L-H jonilh@gmail.com --- This bug is still in 1.7.19 USEGLSL=disabled seams not to help. It is a bit random for me however. And seams to be more prone to happen in outdoor zones. Seams to get worse with playtime.
Linux Mint 17 64bit 32bit Dedicated WinePrefix Source Steam NVIDIA GeForce 770 2GB (Driver 337.25 from xorg-edgers)
https://bugs.winehq.org/show_bug.cgi?id=33362
TestSubject sirbubbles01@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sirbubbles01@gmail.com
--- Comment #13 from TestSubject sirbubbles01@gmail.com --- This is still an issue on wine 1.7.30, with glsl disabled and an nvidia 660 with 331.89 drivers. Seems to happen when detailed textures are being loaded when you get close to a character and does not seem to depend on play time, I get it after starting the game fresh. A reload of a save sometimes fixes it.
https://bugs.winehq.org/show_bug.cgi?id=33362
roger@mailinator.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |roger@mailinator.com
--- Comment #14 from roger@mailinator.com --- We need backtrace of the game, when it happens. Just start the game from console and paste the debug here as txt file.
https://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #15 from TestSubject sirbubbles01@gmail.com --- Created attachment 50010 --> https://bugs.winehq.org/attachment.cgi?id=50010 log of Dragon Age Origins, black textures on character clothing
Attaching log of wine 1.7.12. I got the black textures by just approaching a few soldiers in Ostagar. With wine 1.7.8, I do not have the same trouble.
https://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #16 from roger@mailinator.com --- If that's so then it's regression bug. See winehq FAQ about regression testing.
The log shows out of memory errors. The earlier version didnt show those errors?
https://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #17 from TestSubject sirbubbles01@gmail.com --- (In reply to roger from comment #16)
If that's so then it's regression bug. See winehq FAQ about regression testing.
The log shows out of memory errors. The earlier version didnt show those errors?
Seems I may have been wrong. It most certainly does. I'm not sure why I managed to play the game for several minutes and not see black textures before now. It also led to the game freezing up and eventually crashing.
https://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #18 from Someone scrimekiler@yahoo.fr --- This bug is still happening in wine 1.7.33 and wine-staging-1.7.33
It still happen at the same location of the game : Denerim Marrket District.
https://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #19 from Someone scrimekiler@yahoo.fr --- This bug happpens with both StrictDrawOrdering enabled and disabled.
Errors are a bit similar to https://bugs.winehq.org/show_bug.cgi?id=26898
But functions are not the same :
"err:d3d:wined3d_debug_callback 0xa09ea60: "GL_OUT_OF_MEMORY error generated. Failed to allocate memory for texture.". err:d3d_texture:texture2d_prepare_texture >>>>>>>>>>>>>>>>> GL_OUT_OF_MEMORY (0x505) from glTexImage2D @ /var/tmp/notmpfs/portage/app-emulation/wine-1.7.33-r4/work/wine-1.7.33/dlls/wined3d/texture.c / 937 err:d3d:wined3d_debug_callback 0xa09ea60: "GL_INVALID_VALUE error generated. Size and/or offset out of range.". err:d3d_surface:surface_upload_data >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from glCompressedTexSubImage2DARB @ /var/tmp/notmpfs/portage/app-emulation/wine-1.7.33-r4/work/wine-1.7.33/dlls/wined3d/surface.c / 1542"
https://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #20 from Someone scrimekiler@yahoo.fr --- With CMST enabled it leads to crash with "(0) : fatal error C9008: out of memory - malloc failed"
(sorry for so much separated posts, I didn't notice all of this at the same time)
https://bugs.winehq.org/show_bug.cgi?id=33362
Nicholas O'Connor nrfoconnor+wine@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nrfoconnor+wine@gmail.com
--- Comment #21 from Nicholas O'Connor nrfoconnor+wine@gmail.com --- I just hit this bug myself (Human Noble start, the clothing of the two guests your mother entertains), and the nature of it reminds me of a similar bug that happens when you don't use native d3dx9 in TES4 Oblivion (bug #20074).
I'm applying "native, builtin" overrides to all d3dx9 DLLs for daorigins.exe in winecfg (I don't know which one DA Origins actually uses), I'll report back if this fixes the problem or not.
https://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #22 from Nicholas O'Connor nrfoconnor+wine@gmail.com --- Hello again, no such luck. 1.7.43, nvidia-drivers 352.09 on gentoo-sources 4.0.4.
https://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #23 from Nicholas O'Connor nrfoconnor+wine@gmail.com --- Everyone turn your graphics settings down, you'll be able to play longer without hitting the bug. You should also report whether or not the bug hits you at all after turning them down and any oddities in your wine configuration.
This bug is also being discussed on wine-staging's bugzilla (https://bugs.wine-staging.com/show_bug.cgi?id=335, affected games in this instance are Skyrim and Fallout NV), current working theory is either a memory leak or functions like IDirect3DDevice9::GetAvailableTextureMem being emulated incorrectly (starting at 0, which is incorrect since your window manager is also taking some graphics memory)
https://bugs.winehq.org/show_bug.cgi?id=33362
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1
--- Comment #24 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Nicholas O'Connor from comment #23)
Everyone turn your graphics settings down, you'll be able to play longer without hitting the bug. You should also report whether or not the bug hits you at all after turning them down and any oddities in your wine configuration.
This bug is also being discussed on wine-staging's bugzilla (https://bugs.wine-staging.com/show_bug.cgi?id=335, affected games in this instance are Skyrim and Fallout NV), current working theory is either a memory leak or functions like IDirect3DDevice9::GetAvailableTextureMem being emulated incorrectly (starting at 0, which is incorrect since your window manager is also taking some graphics memory)
Notice that GL_OUT_OF_MEMORY means that libGL isn't able to allocate system memory, usually because the process filled up its addressing space. That has nothing to do with video memory accounting.
Unless there is an actual memory leak there is not much we can do. Lowering graphic / texture settings might help (as you noticed), manually lowering the amount of video memory reported to the game (e.g. via the VideoMemorySize registry setting) is another possible option.
https://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #25 from Nicholas O'Connor nrfoconnor+wine@gmail.com --- Sorry for late response, I never received an email about this bug for some reason.
(In reply to Matteo Bruni from comment #24)
Notice that GL_OUT_OF_MEMORY means that libGL isn't able to allocate system memory, usually because the process filled up its addressing space. That has nothing to do with video memory accounting.
Why would libGL use system RAM for graphics processing? That makes no sense. In addition, that statement contradicts how the bug behaves on my system, where it has plenty of system RAM to work with (I have 4GB total, DAO only takes up maybe 1.5GB at maximum, my background processes take up ~600MB), but still hits GL_OUT_OF_MEMORY. The only logical explanation is its related to video memory.
It's very much possible that games are actually using the GetAvailableTextureMem function to decide whether or not they should unload something from their memory before loading something else in.
Unless there is an actual memory leak there is not much we can do. Lowering graphic / texture settings might help (as you noticed), manually lowering the amount of video memory reported to the game (e.g. via the VideoMemorySize registry setting) is another possible option.
I tried lowering VideoMemorySize with another game and got numerous GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT errors (and a nice little dialog box that said "Out of memory!" that I couldn't dismiss until I alt-tabbed to the terminal window and hit Ctrl-C, though I'm not certain whether Wine or my game generated that).
Unless everyone else can use that method just fine and it's only me, I do not feel comfortable with that being a recommended solution.
https://bugs.winehq.org/show_bug.cgi?id=33362
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |matteo.mystral@gmail.com
--- Comment #26 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Nicholas O'Connor from comment #25)
Sorry for late response, I never received an email about this bug for some reason.
(In reply to Matteo Bruni from comment #24)
Notice that GL_OUT_OF_MEMORY means that libGL isn't able to allocate system memory, usually because the process filled up its addressing space. That has nothing to do with video memory accounting.
Why would libGL use system RAM for graphics processing? That makes no sense. In addition, that statement contradicts how the bug behaves on my system, where it has plenty of system RAM to work with (I have 4GB total, DAO only takes up maybe 1.5GB at maximum, my background processes take up ~600MB), but still hits GL_OUT_OF_MEMORY. The only logical explanation is its related to video memory.
It might also be related to video memory but that would be surprising (read: all the times I encountered that error it had to do with virtual memory exhaustion). I guess it's still possible.
It's very much possible that games are actually using the GetAvailableTextureMem function to decide whether or not they should unload something from their memory before loading something else in.
Unless there is an actual memory leak there is not much we can do. Lowering graphic / texture settings might help (as you noticed), manually lowering the amount of video memory reported to the game (e.g. via the VideoMemorySize registry setting) is another possible option.
I tried lowering VideoMemorySize with another game and got numerous GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT errors (and a nice little dialog box that said "Out of memory!" that I couldn't dismiss until I alt-tabbed to the terminal window and hit Ctrl-C, though I'm not certain whether Wine or my game generated that).
Sure, another game might have different requirements.
Unless everyone else can use that method just fine and it's only me, I do not feel comfortable with that being a recommended solution.
FWIW at least the user Someone does actually run out of addressing space (as seen from the malloc failing in the CSMT case). From what you're saying, that's not what happens on your system. BTW how are you checking for the memory usage by the game process? What's your GPU model and video memory size?
It might be that there are multiple problems leading to the same result. In your specific case, what screen resolution is set in the game? You could try to lower it and see if that makes any difference for you.
https://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #27 from Someone scrimekiler@yahoo.fr ---
Unless there is an actual memory leak there is not much we can do. Lowering graphic / texture settings might help (as you noticed), manually lowering the amount of video memory reported to the game (e.g. via the VideoMemorySize registry setting) is another possible option.
To lower it ? Do you mean the memory usage of the graphic card is related to the memory usage of the RAM when using wine ?
Everyone turn your graphics settings down, you'll be able to play longer without hitting the bug.
Yes that's actually the only workaround I found yet.
I saw that a similar bugged happened sometimes on windows with the same app...So now I wonder if it's only a wine bug or an App bug...
BTW how are you checking for the memory usage by the game process? What's your GPU model and video memory size?
ps aux | grep exe (or grep wine), free -m...Geforce GT 630, 2 GB graphic memory
Lowering the texture level and game details level make the bug become rare
(It seems setting the VideoMemorySize to the actual value of my graphic card make things worse than not setting it at all, with all apps...But maybe it's only a subjective impression ?)
https://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #28 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Someone from comment #27)
Unless there is an actual memory leak there is not much we can do. Lowering graphic / texture settings might help (as you noticed), manually lowering the amount of video memory reported to the game (e.g. via the VideoMemorySize registry setting) is another possible option.
To lower it ? Do you mean the memory usage of the graphic card is related to the memory usage of the RAM when using wine ?
Not directly and not quite, but something to that effect probably happens. For one, each D3D resource has an associated object which takes some space in system memory. It's not much memory per-object but still. Then it's conceivable that the driver allocates some system memory for each GL resource the game creates. I imagine there isn't a full system-memory copy of each GL texture but, again, there is some memory used for bookkeeping and whatever at each point in time. More importantly, the driver will probably map areas of the video memory into the addressing space of the process and that might very well scale with the amount of GL resources used. Those memory mappings don't use actual system memory but still take away from the usable "memory space" by the process. The details here depend on the specific driver of course. So, by giving the game more "room" for graphic resources, it will might end up using more addressing space and possibly running out of it.
BTW how are you checking for the memory usage by the game process? What's your GPU model and video memory size?
ps aux | grep exe (or grep wine), free -m...Geforce GT 630, 2 GB graphic memory
Are you checking the RSS column or the VSZ one? RSS is the amount of actual memory used but what we're interested into here is VSZ aka the virtual memory / addressing space usage. For a 32-bit process on 64-bit Linux 4GB is all you get. Less than that on a 32-bit OS.
Wine reserves a large portion of the addressing space for all the memory allocations made by the game and the DLLs. The rest is available for native libraries, including libGL. My impression is that, at least in your case, at some point the process addressing space fills up and libGL fails to allocate more memory. You could try to verify that with ps or top.
Lowering the texture level and game details level make the bug become rare
(It seems setting the VideoMemorySize to the actual value of my graphic card make things worse than not setting it at all, with all apps...But maybe it's only a subjective impression ?)
Again, it depends. We should default to 1GB for your GPU. If the increased memory usage resulting from reporting 2GB of VRAM to the game makes it run out of addressing space, then sure. On the other hand there might as well be other games that e.g. require 2GB of VRAM to enable some feature and don't suffer as badly from addressing space exhaustion.
https://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #29 from Matteo Bruni matteo.mystral@gmail.com --- Ah, BTW, one thing you could try if you're using the Nvidia binary drivers is to set the __GL_HEAP_ALLOC_LIMIT environment variable to some value (see the "Limiting heap allocations in the OpenGL driver" section on http://us.download.nvidia.com/XFree86/Linux-x86_64/352.21/README/openglenvva...). I never tried it, it might kill kittens so beware.
https://bugs.winehq.org/show_bug.cgi?id=33362
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #30 from joaopa jeremielapuree@yahoo.fr --- Still a bug in current wine?
https://bugs.winehq.org/show_bug.cgi?id=33362
Markus Kitsinger (SwooshyCueb) root@swooshalicio.us changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |root@swooshalicio.us
--- Comment #31 from Markus Kitsinger (SwooshyCueb) root@swooshalicio.us --- Something interesting worth noting: Windows 10 has a similar issue with this game. It is a lot worse in Wine, however. If my memory serves, Windows 7 had no such issue.
https://bugs.winehq.org/show_bug.cgi?id=33362
tokktokk fdsfgs@krutt.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs@krutt.org
https://bugs.winehq.org/show_bug.cgi?id=33362
--- Comment #32 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with vanilla wine-6.19?
-
wine-bugs＠winehq.org -
WineHQ Bugzilla