You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The program compiles and runs, but no mesh is visible in either ofMesh or ofVBOMesh mode. To get the program to run, I had to change skip = 1 to skip = 20.
hi @bakercp , if you set in draw() ofBackground(120); and comment out
img.bind()
img.unbind()
you can see the geometry rendered (all black because without texture). but you have to move a bit the camera...
i think the problem now is the texture binded. but i reserve to do other test with a light source to see how is rendered.
@kalwalt I just confirmed your findings regarding img.bind() / img.unbind() on the RPi. I'm going to write some simple tests to check texture binding. I'll post results here.
Greets all. I tested ofVboMesh and ofMesh using simple examples (a single triangle) and was unable to bind an image, even after adding the tex coords to the mesh, etc. I also tried throwing some light on it with ofLight in GLES1 mode. When the textures were unbound, the mesh was illuminated correctly. When the texture was bound, just black.
Thus, I'm thinking that there may be some gles implementation problem in the of mesh code?
i guess you are not using normalized tex coordinates? gles doesn't support arb textures so you need to use 0..1 tex coords. ofBox detects gles and does that. i guess all the examples that use textures will need some ifdefs
Activity
bakercp commentedon Dec 4, 2012
This original exception was happening because easycam (which uses events) was failing. Easycam is now fixed, but the VBO is still failing.
bakercp commentedon Dec 4, 2012
The program compiles and runs, but no mesh is visible in either
ofMeshorofVBOMeshmode. To get the program to run, I had to changeskip = 1toskip = 20.kalwalt commentedon Jan 3, 2013
hi @bakercp , if you set in draw() ofBackground(120); and comment out
you can see the geometry rendered (all black because without texture). but you have to move a bit the camera...
i think the problem now is the texture binded. but i reserve to do other test with a light source to see how is rendered.
tested with the latest commits and GLES2.
bakercp commentedon Jan 9, 2013
@kalwalt I just confirmed your findings regarding img.bind() / img.unbind() on the RPi. I'm going to write some simple tests to check texture binding. I'll post results here.
bakercp commentedon Jan 9, 2013
Greets all. I tested ofVboMesh and ofMesh using simple examples (a single triangle) and was unable to bind an image, even after adding the tex coords to the mesh, etc. I also tried throwing some light on it with ofLight in GLES1 mode. When the textures were unbound, the mesh was illuminated correctly. When the texture was bound, just black.
Thus, I'm thinking that there may be some gles implementation problem in the of mesh code?
kalwalt commentedon Jan 9, 2013
yes but ofBoxExample(and the multilightexample) works instead. Also this example has:
why this works good?
bakercp commentedon Jan 9, 2013
@kalwalt that is a wonderful question :)
arturoc commentedon Jan 10, 2013
i guess you are not using normalized tex coordinates? gles doesn't support arb textures so you need to use 0..1 tex coords. ofBox detects gles and does that. i guess all the examples that use textures will need some ifdefs
bakercp commentedon Jan 10, 2013
@arturoc you're brilliant.
Fixed with 2ccffce.