two problems with GL tracing
Reported by Carl Witty | July 20th, 2010 @ 06:09 AM
I used http://scenejs.wikispaces.com/Logging+WebGL+Calls to track down the problem on ticket #124. Very nice!
However, I had to make two changes to the tracing code to get it to work for me. I've attached a patch with the changes.
The first change was to comment out printing the contents of WebGLFloatArray objects that get passed to webgl. Chrome was giving errors like "WebGLFloatArray has no method .get()" (that's not the exact wording). Simply commenting out the code is presumably not the right fix; on the other hand, if you're sending a 20,000 element array to webgl, printing the whole thing might not be the best idea anyway. Maybe it should abbreviate (print only the first 10 and last 6 elements if it has more than 16 elements, for example). (Those numbers were carefully chosen so that it would print the entirety of a mat4.) The second change was to add a test for undefined where there was already a test for null. I didn't try to understand the code there; I just saw in the debugger that arg was undefined.
Comments and changes to this ticket
-
lindsay.kay (at xeolabs) July 22nd, 2010 @ 03:36 AM
- State changed from “new” to “resolved”
- Milestone order changed from “0” to “0”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
SceneJS provides easy access to WebGL through a simple and declarative JavaScript API. The SceneJS API is functional, which enables its scene definitions to be really compact and expressive, while hooking into other JavaScript code just that little bit more smoothly.
Carl Witty
lindsay.kay (at xeolabs)