[Bug 38218] New: Corrupted Colors in Call of Duty World at War Single and Multiplayer

https://bugs.winehq.org/show_bug.cgi?id=38218

Bug ID: 38218
           Summary: Corrupted Colors in Call of Duty World at War Single
                    and Multiplayer
           Product: Wine
           Version: 1.7.38
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

corrupted colors in faces, rocks and other things in call of duty world at war
single and multiplayer modes

is wine 1.7.28 appears ok, for both wine test used lastest nvidia beta drivers,
clean prefix for both

[Bug 38218] Corrupted Colors in Call of Duty World at War Single and Multiplayer

https://bugs.winehq.org/show_bug.cgi?id=38218

[e-mail] changed:

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

[Bug 38218] Corrupted Colors in Call of Duty World at War Single and Multiplayer

https://bugs.winehq.org/show_bug.cgi?id=38218

Sebastian Lackner  changed:

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

--- Comment #1 from Sebastian Lackner  ---
So everything worked well with 1.7.28? This means it is regression, and it
might be very useful to run a regression test, see
http://wiki.winehq.org/RegressionTesting for more details.

Please also attach a screenshot (so we can understand better how exactly the
color corruption looks like) and terminal output from the game, for both 1.7.28
and 1.7.38.

[Bug 38218] Corrupted Colors in Call of Duty World at War Single and Multiplayer

https://bugs.winehq.org/show_bug.cgi?id=38218

--- Comment #2 from [e-mail] ---
(In reply to Sebastian Lackner from comment #1)
> So everything worked well with 1.7.28? This means it is regression, and it
> might be very useful to run a regression test, see
> http://wiki.winehq.org/RegressionTesting for more details.
>
> Please also attach a screenshot (so we can understand better how exactly the
> color corruption looks like) and terminal output from the game, for both
> 1.7.28 and 1.7.38.

This is some screens with problem, at simple seek seems very similar to farcry
3 color errors

http://i.imgur.com/JTVdVT9.jpg

http://i.imgur.com/sNaLmQ3.jpg

http://i.imgur.com/SJlHWpk.jpg

http://i.imgur.com/hK4QH87.jpg

http://i.imgur.com/zGljef2.jpg

http://i.imgur.com/hzhKvgc.jpg

http://i.imgur.com/EYeoWgD.jpg

http://i.imgur.com/NOjII1U.jpg

http://i.imgur.com/bYQKuci.jpg

http://i.imgur.com/fGXpByt.jpg

[Bug 38218] Corrupted Colors in Call of Duty World at War Single and Multiplayer

https://bugs.winehq.org/show_bug.cgi?id=38218

--- Comment #3 from Andrey Gusev  ---
What version of the game?

[Bug 38218] Corrupted Colors in Call of Duty World at War Single and Multiplayer

https://bugs.winehq.org/show_bug.cgi?id=38218

--- Comment #4 from [e-mail] ---
(In reply to Andrey Gusev from comment #3)
> What version of the game?

Steam version

[Bug 38218] Corrupted Colors in Call of Duty World at War Single and Multiplayer

https://bugs.winehq.org/show_bug.cgi?id=38218

Andrey Gusev  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #5 from Andrey Gusev  ---
A duplicate.

*** This bug has been marked as a duplicate of bug 37750 ***

[Bug 38218] Corrupted Colors in Call of Duty World at War Single and Multiplayer

https://bugs.winehq.org/show_bug.cgi?id=38218

Andrey Gusev  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED
                 CC|                            |[e-mail]

--- Comment #6 from Andrey Gusev  ---
Closing.