[Bug 28321] New: D3D: Out of adapter memory, wrong thread problem

http://bugs.winehq.org/show_bug.cgi?id=28321

Summary: D3D: Out of adapter memory, wrong thread problem
           Product: Wine
           Version: 1.3.27
          Platform: x86-64
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

I've bought new graphics cards. At first, I've bought AMD Radeon HD6870 which
I've returned already. Now, I have GFX560.
Both showed problems which can be seen in attached logs. Half-Life 2 is pretty
much the only game that runs. The others do either crash immediately or later
on due to various reasons eg. DirectX problem =~ out of adapter memory.
At first, I thought it is some kind of driver issue, as ATi/AMD never had good
reputation in hw driver field, yet GFX560 shows the every same symptoms. I used
to have GFX260 prior to this upgrade and I had no problems what so ever.
Yes, I've deleted ~/.wine, it didn't help. I've actually played HL2 previous
weekend. Running apps as % wine X -novid -dxlevel 90 -width 1280 -height 1024;
didn't help either.

I'm just wondering whether this is hardware issue or software issue eg. wine
doesn't have support for DX11 cards or whatever.

If more info or anything else is needed, let me know.

Thank you!

[Bug 28321] D3D: Out of adapter memory, wrong thread problem

http://bugs.winehq.org/show_bug.cgi?id=28321

--- Comment #1 from [e-mail] 2011-09-09 04:29:16 CDT ---
Created an attachment (id=36289)
 --> (http://bugs.winehq.org/attachment.cgi?id=36289)
Trine debug output

Attached debug output of Trine.

[Bug 28321] D3D: Out of adapter memory, wrong thread problem

http://bugs.winehq.org/show_bug.cgi?id=28321

Rico  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #36289|application/octet-stream    |text/plain
          mime type|                            |

[Bug 28321] D3D: Out of adapter memory, wrong thread problem

http://bugs.winehq.org/show_bug.cgi?id=28321

--- Comment #2 from [e-mail] 2011-09-09 09:05:00 CDT ---
I've tried Warsow, which is native, and it works without any problems.

[Bug 28321] D3D: Out of adapter memory, wrong thread problem

http://bugs.winehq.org/show_bug.cgi?id=28321

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
            Version|1.3.27                      |1.3.28

--- Comment #3 from [e-mail] 2011-09-10 04:48:07 CDT ---
Changing to version 1.3.28

[Bug 28321] D3D: Out of adapter memory, wrong thread problem

http://bugs.winehq.org/show_bug.cgi?id=28321

Dmitry Timoshkov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|[e-mail]    |
            Version|1.3.28                      |1.3.27

--- Comment #4 from Dmitry Timoshkov  2011-09-12 02:14:46 CDT ---
Don't do that.

[Bug 28321] D3D: Out of adapter memory, wrong thread problem

http://bugs.winehq.org/show_bug.cgi?id=28321

--- Comment #5 from [e-mail] 2011-09-12 03:18:57 CDT ---
Yep, sorry for that :\

I've also tried wine-1.3.24(which I've compiled some time ago) and GTA2 which
works in this version, but does not in 1.3.27/1.3.28. Now, don't get me wrong.
There are still some issues that are reminiscent of problems mentioned above.

[Bug 28321] D3D: Out of adapter memory, wrong thread problem

http://bugs.winehq.org/show_bug.cgi?id=28321

--- Comment #6 from [e-mail] 2011-09-18 04:18:35 CDT ---
Just to add more info:
X.org server version: 1.9.5 (10905000)
nV driver version: 280.13
GNU/Linux distribution: Slackware64-current (x86_64)

btw card is being reported as NVIDIA 8300 GS, which I'm sure is not correct.

[Bug 28321] D3D: Out of adapter memory, wrong thread problem

http://bugs.winehq.org/show_bug.cgi?id=28321

--- Comment #7 from [e-mail] 2011-09-25 13:12:58 CDT ---
Same with wine-1.3.29.

[Bug 28321] D3D: Out of adapter memory, wrong thread problem

http://bugs.winehq.org/show_bug.cgi?id=28321

--- Comment #8 from [e-mail] 2011-09-26 13:07:51 CDT ---
Created attachment 36572
  --> http://bugs.winehq.org/attachment.cgi?id=36572
GFX560 patch v1 - add PCI ID for GTX560 and make it default return value

Ok, so the problem is with GTX560 not being recognized by wine. I've tried to
hack around in 'dlls/wined3d/directx.c' and 'dlls/wined3d/wined3d_private.h'
and defined GTX560(btw there is wrongly defined GTX560 as TI which is not).
However, I've, or wine, failed to correctly recognize graphics card. Only when
I've replaced default return value, which is 8300GS, it works.
No, it does not, because it is default value of function. Could somebody from
developers help me with this one? I though, and I still think, expanding
enumeration of nVidia cards is the way to do it. What I don't understand is why
wine doesn't recognize graphics card even with correctly provided PCI ID.

Patch is attached.

[Bug 28321] D3D: Out of adapter memory, wrong thread problem

http://bugs.winehq.org/show_bug.cgi?id=28321

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #36572|0                           |1
        is obsolete|                            |

--- Comment #9 from [e-mail] 2011-09-27 00:31:58 CDT ---
Created attachment 36577
  --> http://bugs.winehq.org/attachment.cgi?id=36577
GFX 560 patch - adds PCI ID and defines properties of GFX 560, shifts GFX560TI
to be trully TI not GFX560; patch against wine-1.3.29

I've tested it again and correct graphics card is being returned this time.

I propose to add "UNKNOWN CARD" into enumeration as well and document it, so
users of wine know what's going on and what to do => report back their graphics
card and PCI ID, so it can be added. 
Assumption of backwards compatibility, with 8300GS and some-default-AMD
graphics card, fails for nV GFX560 and AMD HD6870. And I don't think these are
going to be only two.

It also would be great to have a tool or way to display detected graphics card,
sound card and what not eg. in wine. Because there aren't many ways you can do
it except thanks to some games, namely Crysis 2 and its jabber "your card X is
not supported". I found out there is a problem with my sound card as well which
is going to be harder to figure out than this one.
What I'm trying to say is to make it easier for wine user to check whether his
hardware is detected in wine as it should be. His graphics is GFX560 and not
8300GS, for example.

[Bug 28321] D3D: Out of adapter memory, wrong thread problem

http://bugs.winehq.org/show_bug.cgi?id=28321

Damian Ivanov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #10 from Damian Ivanov  2011-11-05 00:56:59 CDT ---
I think this patch is in 1.3.32 
Isn't it?

[Bug 28321] D3D: Out of adapter memory, wrong thread problem

http://bugs.winehq.org/show_bug.cgi?id=28321

--- Comment #11 from [e-mail] 2011-11-05 01:52:10 CDT ---
Yes, it looks that way. So this one can be closed as fixed.

Just for the record, it is PCI ID for GIGABYTE N56GOC-1GI ~
http://www.gigabyte.eu/products/product-page.aspx?pid=3881#ov

Thanks.

[Bug 28321] D3D: Out of adapter memory, wrong thread problem

http://bugs.winehq.org/show_bug.cgi?id=28321

Bruno Jesus  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |[e-mail]
         Resolution|                            |FIXED

--- Comment #12 from Bruno Jesus  2011-11-05 06:52:05 CDT ---
Original reporter says it's fixed.

http://source.winehq.org/git/wine.git/commit/485571539f5c27a5bd391ae69e436d7...

[Bug 28321] D3D: Out of adapter memory, wrong thread problem

http://bugs.winehq.org/show_bug.cgi?id=28321

Bruno Jesus  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
      Fixed by SHA1|                            |485571539f5c27a5bd391ae69e4
                   |                            |36d774f8b9276

[Bug 28321] D3D: Out of adapter memory, wrong thread problem

http://bugs.winehq.org/show_bug.cgi?id=28321

Jerome Leclanche  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #13 from Jerome Leclanche  2011-11-05 07:33:27 CDT ---
(In reply to comment #9)
> It also would be great to have a tool or way to display detected graphics card,
> sound card and what not eg. in wine.

This is functionality supposed to be implemented in dxdiag. There's a
super-basic implementation of it (with no gui); if you're interested in
improving it, by all means :)

[Bug 28321] D3D: Out of adapter memory, wrong thread problem

http://bugs.winehq.org/show_bug.cgi?id=28321

Jerome Leclanche  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|-unknown                    |directx-d3d

[Bug 28321] D3D: Out of adapter memory, wrong thread problem

http://bugs.winehq.org/show_bug.cgi?id=28321

--- Comment #14 from [e-mail] 2011-11-12 01:50:40 CST ---
(In reply to comment #13)
> This is functionality supposed to be implemented in dxdiag. There's a
> super-basic implementation of it (with no gui); if you're interested in
> improving it, by all means :)

Cool. However, there are two things. The first is wine should stop reporting
GF8300, or whatever, and start reflecting on a fact it doesn't know what
graphic card user has. 
It seems to be better if it did report something like: "Unknown graphic card.
See wiki for problem No.123". Then user would launch his favorite web search
engine, looked up for "wine problem 123" which would take him to wiki page with
description what to do:
* how-to get PCI ID - lspci, or nvidia-settings, I don't know how about AMD
* how much memory graphics card have - a lot of ways how to find out
* manufacturer/model/whatever
* file bug at winehq or send all above to the mailing list

Wine could also write some of above eg. PCI ID into console, because it has
this information available at that point.

As for the thing you've mentioned, I feel it is quite pointless without
changing the first. As for GUI, I'm personally fine with CLI application.
Anyway, please, point me in the right direction and I'll check it out.

Thanks.

[Bug 28321] D3D: Out of adapter memory, wrong thread problem

http://bugs.winehq.org/show_bug.cgi?id=28321

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #15 from Alexandre Julliard  2011-11-18 13:05:01 CST ---
Closing bugs fixed in 1.3.33.