We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 2144 - incomplete framebuffer when combining renderer and depth buffer bits
Summary: incomplete framebuffer when combining renderer and depth buffer bits
Status: RESOLVED WONTFIX
Alias: None
Product: SDL
Classification: Unclassified
Component: *don't know* (show other bugs)
Version: 2.0.0
Hardware: x86 Mac OS X 10.8
: P2 normal
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-10 08:42 UTC by Zac
Modified: 2017-08-15 05:26 UTC (History)
0 users

See Also:

Attachments
code sample (2.72 KB, text/plain)
2013-10-11 04:44 UTC, Sam Lantinga 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Zac 2013-10-10 08:42:56 UTC 
http://pastebin.com/NsXjiX6y

This code fails when lines 50 and 65 are both uncommented.
Comment 1 Zac 2013-10-10 08:43:50 UTC 
That said, I don't need the renderer, so I am just not using it and I have no problems, but linkmauvel on irc suggested I post it here.
Comment 2 Zac 2013-10-10 08:44:31 UTC 
linkmauvel says on linux with opengl 3.1 and the same graphics chipset it doesn't have the same problem.
Comment 3 Zac 2013-10-10 08:45:18 UTC 
The specific failure I get is decimal FB status: 36053
Comment 4 Zac 2013-10-10 09:01:20 UTC 
sorry, that's the wrong failure code -- it was framebuffer undefined, not incomplete attachment.
Comment 5 Sam Lantinga 2013-10-11 04:44:40 UTC 
Created attachment 1361 [details]
code sample

Example code, in case pastebin loses the snippet
Comment 6 Ryan C. Gordon 2015-02-19 05:22:21 UTC 
Marking a large number of bugs with the "triage-2.0.4" keyword at once. Sorry if you got a lot of email from this. This is to help me sort through some bugs in regards to a 2.0.4 release. We may or may not fix this bug for 2.0.4, though!
Comment 7 Sam Lantinga 2017-08-15 05:26:15 UTC 
Old bug, many driver revisions ago, closing for now. Please reopen if this issue is still relevant.