Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple problems with Chapter 8 fbo_drawbuffers example #51

Open
GoogleCodeExporter opened this issue Apr 20, 2015 · 3 comments
Open

Comments

@GoogleCodeExporter
Copy link

Not all of these are related to errors in the book / code. However, I am 
including them here for the benefit of those who face the same issue.

What steps will reproduce the problem?
1. make the fbo_drawbuffers on linux. It will fail.
2. After fixing the code issues, run the example.
3. The program might output "A GL Error has occured" on the console and the 
smaller ninja in the right top will not show up.

What is the expected output? What do you see instead?
The smaller ninja in the right top should show up, but he is missing.

What version of the product are you using? On what operating system?
Ubuntu 10.04 with Nvidia drivers.



Please provide any additional information below.
Here are steps to fix the code issues (there are many similar issues with other 
examples on linux)
1. In fbo_drawbuffers.cpp, change "marble.bmp" to "Marble.bmp" and 
"NinjaComp.bmp" to "NinjaComp.BMP"
2. In Src/Models/Ninja/sbm.cpp, change #include <gltools.h> to #include 
<GLTools.h>. Make the same change in Src/Models/Ninja/sbm.h

This might be enough to fix this example. However, if like me, you have forced 
your graphics drivers to override application settings for AntiAliasing, your 
little Ninja at the top right be missing and errors printed on the console.

As you can guess, this is fixed by disabling the forcing of AntiAliasing in the 
Nvidia settings.


Original issue reported on code.google.com by [email protected] on 20 Sep 2012 at 1:05

Attachments:

@GoogleCodeExporter
Copy link
Author

[deleted comment]

1 similar comment
@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

This is because the 2 buffers, the default screen buffer and the frame buffer 
we allocated, do not have the same Samples per pixel. When anti aliasing is 
enabled, the default buffer is multisampled.

glBlitFramebuffer throws an error if
1. buffers have different samples and
2. image being copied is being scaled.

Original comment by [email protected] on 20 Sep 2012 at 1:09

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant