Bug 97508 - Rogue Legacy 4th area with corrupted textures
Summary: Rogue Legacy 4th area with corrupted textures
Status: RESOLVED NOTOURBUG
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/nouveau (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Nouveau Project
QA Contact: Nouveau Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-27 12:34 UTC by Karol Herbst
Modified: 2016-08-27 19:35 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
apitrace (11.46 MB, application/x-xz)
2016-08-27 12:34 UTC, Karol Herbst 		Details
screenshot (2.22 MB, image/png)
2016-08-27 12:35 UTC, Karol Herbst 		Details
View All

Description Karol Herbst 2016-08-27 12:34:02 UTC 
attached is an apitrace and a screenshot showing the issue

mesa: git-fb89551
Comment 1 Karol Herbst 2016-08-27 12:34:49 UTC 
Created attachment 126069 [details]
apitrace
Comment 2 Karol Herbst 2016-08-27 12:35:40 UTC 
Created attachment 126070 [details]
screenshot
Comment 3 Karol Herbst 2016-08-27 12:53:09 UTC 
call 240510 is where the corrupted textures are drawn and those are generated in 95901 and 95918
Comment 4 Karol Herbst 2016-08-27 17:55:35 UTC 
it doesn't show the issue on 342e68dc60eebb20ac1be9f47800ee9e604354f0
Comment 5 Ilia Mirkin 2016-08-27 19:35:28 UTC 
After some investigation, this appears to be a game bug. It creates a texture with BGRA4 format, attaches it to a fb, and then tries to render to it. This is not always going to work in GL - you first have to check if a fb is complete. A FB might be incomplete for just about any reason, but format support is a big one.

G80+ hardware supports BGRA4 for texturing but not for rendering. If this support is disabled, the state tracker will instead create a BGRA8 texture to back the BGRA4 GL texture, and rendering to that will obviously be supported.

However the issue is in the application.

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.