[Assassin's Creed]Transparant ground in Kingdoms

Berillions · Post by **Berillions** » Wed Jun 15, 2011 2:35 pm

Hi,

There is a problem with this game since many versions of wine.
The game runs completly without problem but there is a graphical bug when the
character is in the Kingdoms.

In the 4 city : Damas, Jerusalem, Acre and Masyaf, there isn't this problem,
the ground is visible correctly.

This is the log (output console) :
http://bugs.winehq.org/attachment.cgi?id=35141

This is a screen with the graphic bug :
http://bugs.winehq.org/attachment.cgi?id=35142

Thanks for your help

Post by **DanKegel** » Wed Jun 15, 2011 11:11 pm

Please, when posting links to attachments from bugzilla,
also post a link to the bug they're attached to.

Berillions · Post by **Berillions** » Thu Jun 16, 2011 10:42 am

Sorry Dan,

This is the link to the bug in Bugzilla :
http://bugs.winehq.org/show_bug.cgi?id=27480

Berillions · Post by **Berillions** » Sat Jun 18, 2011 3:24 pm

There isn't a solution for this problem ?
Because it seems to me that there is the same problem for F.E.A.R and F.E.A.R.2 with the latest wine version : http://bugs.winehq.org/show_bug.cgi?id=27145

jjmckenzie · Post by **jjmckenzie** » Sat Jun 18, 2011 7:14 pm

On 6/18/11 1:24 PM, Berillions wrote:

There isn't a solution for this problem ?
Because it seems to me that there is the same problem for F.E.A.R and F.E.A.R.2 with the latest wine version : http://bugs.winehq.org/show_bug.cgi?id=27145

Again, we have to tell you that as simple as some things look from the
User standpoint, it takes time to build, test and verify that code does
exactly what we want it to, without breaking other functions and
programs. I'll give you an example and Dan can verify. I have been
working on several RichEdit functions for the last three years. Not one
of the solutions has been accepted by Alexandre for various reasons.
These are realitively easy to implement. There has been work ongoing on
the graphics engine to solve a problem for over seven years. Solving
this may help solve many of the graphics reports. Again, nothing is
simple when you are dealing with a complex program and it takes time.

James McKenzie

Berillions · Post by **Berillions** » Sun Jun 19, 2011 2:39 am

I understand James but in fact, I wanted to know if someone had an idea where come from the problem.

For FEAR 1/2 bug, it's a regression but for Assassin's Creed, the bug exist since the version 1.1.X of wine so i don't think that it's a regression. (And i don't error message in the console so i don't know how to find the cause)

jjmckenzie · Post by **jjmckenzie** » Sun Jun 19, 2011 11:25 am

On 6/19/11 12:39 AM, Berillions wrote:

I understand James but in fact, I wanted to know if someone had an idea where come from the problem.

For FEAR 1/2 bug, it's a regression but for Assassin's Creed, the bug exist since the version 1.1.X of wine so i don't think that it's a regression. (And i don't error message in the console so i don't know how to find the cause)

I understand that. Many graphics bugs are awaiting the proper
implementation of the DIB engine (currently underway and should be
recorded in bug 421.) Then troubleshooting can commence for those
issues blocked by that bug. This problem may or may not be one of
them. I don't track graphics issues closely, except that Bug 421 is
stopping the implementation of a MacOSX native Wine interface per
reports on the Development mailing list.