Bug 86130

Summary: Some textures are not rendering correctly in apitrace but are fine while capturing
Product: Mesa Reporter: Benjamin Bellec <b.bellec>
Component: Drivers/Gallium/r600Assignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium CC: b.bellec, jfonseca
Version: git   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Example of a broken weapon texture

Description Benjamin Bellec 2014-11-10 22:07:37 UTC
Created attachment 109249 [details]
Example of a broken weapon texture

I captured a Serious Sam 3 trace with apitrace. The game is correctly rendered when capturing. But when retracing with qapitrace, most of the time the weapons textures are completely broken, see the screenshot in attachment for a preview.

I posted this issue on the apitrace mailing list, where José Fonseca give me some advice and provided some patch I tested, but no patch or tips were able to solve the problem. My discussion with José has many details, you should look here :
http://lists.freedesktop.org/archives/apitrace/2014-November/001011.html

I have this issue with a Radeon HD5850 (CYPRESS) and a HD4850 (RV770) too. But not with a GeForce GT210 (NVA8). I have no other card to test.

I'm currently using Mesa 10.3.2 but also tested with 9.0 without better results.

I provided several (api)trace to José on the mailing list, you could find them on the thread pointed above.

I'm available for more details or test.
Comment 1 Marek Olšák 2014-11-11 13:26:27 UTC
Can you test Mesa master?
Comment 2 Benjamin Bellec 2014-11-11 14:18:19 UTC
(In reply to Marek Olšák from comment #1)
> Can you test Mesa master?

Done, no better results.

Note that all my tests have been done with R600_DEBUG=nohyperz
Comment 3 GitLab Migration User 2019-09-18 19:17:56 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/532.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.