In case anyone has a solution to this, here's the video of the Up^2 trying to render the knight.
As you can see the scene, which is an OBJ and the debug line draws all work find, so it probably isn't my setting up of the shaders thats the issue.
And here's the same code running on a raspberry
I really wish I knew why this was happening, I'm pretty sure its a screw up in the data formatting but until I have time to dump a listing of the VBO's on both systems to compare I won't be sure. For now I have to put it on the back burner, as I have lots of other stuff to do, if you are running any of the demos on an intel based board, let me know if you have problems? I may just be specific to the Up^2.
As you can see the scene, which is an OBJ and the debug line draws all work find, so it probably isn't my setting up of the shaders thats the issue.
And here's the same code running on a raspberry
I really wish I knew why this was happening, I'm pretty sure its a screw up in the data formatting but until I have time to dump a listing of the VBO's on both systems to compare I won't be sure. For now I have to put it on the back burner, as I have lots of other stuff to do, if you are running any of the demos on an intel based board, let me know if you have problems? I may just be specific to the Up^2.
Brian Beuken
Lecturer in Game Programming at Breda University of Applied Sciences.
Author of The Fundamentals of C/C++ Game Programming: Using Target-based Development on SBC's
Lecturer in Game Programming at Breda University of Applied Sciences.
Author of The Fundamentals of C/C++ Game Programming: Using Target-based Development on SBC's