- June 4, 2013 at 8:37 pm #31297
I’m wondering if someone else is having the same problem. When I try to attack a depth texture to a framebuffer on an apple device it works just fine but when I try to do the same with the PVRFrame binaries from the SDK 3.0 or 3.1 it fails. I’m using the 64bits libraries.
Anyone else having this bug ?June 5, 2013 at 8:41 am #37386
I’ve tested the 3.1 SDK version of PVRVFrame with our ShadowMapping Example (which uses the GL_OES_depth_texture extension), and it works correctly for me. I’ve also checked the source for PVRVFrame’s device profile list, and all of them seem to support the extension.
- What OS are you using on your development machine?
- What GPU do you have in your development machine?
- Which Profile do you currently have selected in the PVRVFrame GUI application (found in (SDK_DIR)/PVRVFrame/Tools/PVRVFrameGUI/)?
- Can you explain how the depth texture bind fails? Does glCheckFramebufferStatus return with GL_FRAMEBUFFER_COMPLETE after the binding? Does glGetError return any error codes?
JoeJune 5, 2013 at 2:39 pm #37387
I check the example that you are talking about and I figured out that the problem is to attach a pack depth and stencil buffer (GL_UNSIGNED_INT_24_8_OES). Attaching a simple depth buffer work just fine. For the question you were asking:
1. Windows 7
2. AMD Radeon HD 6900 Series
4. It returns GL_FRAMEBUFFER_UNSUPPORTED
I was not aware about the profile. I’m currently using the dll with my application. Does PVRVFrame is setting something in the registry to set the DLL profile !?June 6, 2013 at 3:17 pm #37388
PVRVFrame does not support OES_packed_depth_stencil or EXT_packed_depth_stencil. This is why GL_FRAMEBUFFER_UNSUPPORTED has been returned for your configuration.
All of our utilities store application state information in .plist files rather than using the Windows registry.