http://bugs.winehq.org/show_bug.cgi?id=7411
bartgenuit(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #25542|0 |1
is obsolete| |
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7411
bartgenuit(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #25541|0 |1
is obsolete| |
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7411
--- Comment #31 from bartgenuit(a)gmail.com 2010-01-04 15:43:17 ---
(In reply to comment #30)
> Oh, it's my turn to apologize if my comment was harsh - it wasn't intended to
> be negative towards you posting this here, although it was negative against
> unclear collection bugs like this one.
>
> The best place to post info is in a new bug report, or even better: search if
> there are any bugs related to PoP:SoT, check if they describe the same issue,
> or one that seems similar, and post them there. If non exist, open a new bug.
:-) That's about the procedure I followed, leading to this thread as the most
fitting (from my naive point of view). So I'll best open a new one then.
Thanks!
Oh, and your comment did not strike me as harsh, I just expected people might
be getting quite tired of postings in the wrong threads (which is a common
problem around the nets), so I tried my diplomatic tone..
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7411
--- Comment #30 from Stefan Dösinger <stefandoesinger(a)gmx.at> 2010-01-04 15:31:23 ---
Oh, it's my turn to apologize if my comment was harsh - it wasn't intended to
be negative towards you posting this here, although it was negative against
unclear collection bugs like this one.
The best place to post info is in a new bug report, or even better: search if
there are any bugs related to PoP:SoT, check if they describe the same issue,
or one that seems similar, and post them there. If non exist, open a new bug.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7411
--- Comment #29 from bartgenuit(a)gmail.com 2010-01-04 15:22:38 ---
(In reply to comment #28)
> err:d3d_shader:pixelshader_update_samplers No texture bound to sampler 3, using
> 2D isn't fglrx related. Furthermore such "hey, this, this, this and this app
> are failing on this driver" type of bugs are hard to keep track of. Since there
> is most likely not one specific thing we can change to fix all problems on
> fglrx at once I think it is better to open separate bugs reports for any other
> remaining issue.
>
> The logic here changed a bit in the last year or two. A while ago it was like
> "oh, this guy is running fglrx, we should essentially close the bug as WONTFIX
> or INVALID", so they were burried in "this driver sucks" bugs like this one
> here. Nowadays fglrx is decently solid that it is worth looking at bugs in
> detail rather than reflexively blaming any issues on the driver.
Well, okay, I'm sorry to have posted it here then, I'm a newbie and don't now
where to post it elsewhere. But I would like to supply any information that
might help solve the issue. Could you give me any pointers where to post this
information so it can be useful to people?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7411
--- Comment #28 from Stefan Dösinger <stefandoesinger(a)gmx.at> 2010-01-04 15:18:02 ---
err:d3d_shader:pixelshader_update_samplers No texture bound to sampler 3, using
2D isn't fglrx related. Furthermore such "hey, this, this, this and this app
are failing on this driver" type of bugs are hard to keep track of. Since there
is most likely not one specific thing we can change to fix all problems on
fglrx at once I think it is better to open separate bugs reports for any other
remaining issue.
The logic here changed a bit in the last year or two. A while ago it was like
"oh, this guy is running fglrx, we should essentially close the bug as WONTFIX
or INVALID", so they were burried in "this driver sucks" bugs like this one
here. Nowadays fglrx is decently solid that it is worth looking at bugs in
detail rather than reflexively blaming any issues on the driver.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7411
--- Comment #27 from bartgenuit(a)gmail.com 2010-01-04 15:10:33 ---
(From update of attachment 25542)
It seems indeed there is an error with d3d_shader. Might this explain the
artifacts?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7411
--- Comment #25 from bartgenuit(a)gmail.com 2010-01-04 15:05:23 ---
Created an attachment (id=25541)
--> (http://bugs.winehq.org/attachment.cgi?id=25541)
Artifacts in PoP:SoT on ATi+FGLRX
This is an example of glitches I encounter when playing PoP:SoT. Setup:
ATi Mobility Radeon HD 3470 + FGLRX driver + Ubuntu 9.04 + Wine 1.1.35.
I suspect it might be because of shading problems and FGLRX.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.