1) Use native OpenGL You can achieve rendering of line thicknesses with a workaround by setting your browser to use native OpenGL instead of ANGLE. You can read here on how to do this on Chrome. Keep in mind that you will experience performance differences if you swap to native OpenGL. EDIT: The master MrDoob … Read more
As SceneJS author I thought I’d throw this in if it helps: SceneJS is specialised towards fast rendering of large numbers of individually articulated objects, without game engine effects like shadows, reflections etc. In other words it’s aimed at requirements of CAD, medical anatomy, engineering visualisations, things with 1000’s of nuts and bolts, organs etc. … Read more
This code will print GPU infos an will list all info you can have with the performance object of this browser (there is no standard for the BOM so it changes for each browser). <html> <body> <canvas id=”glcanvas” width=”0″ height=”0″></canvas> <script> var performance = window.performance || window.mozPerformance || window.msPerformance || window.webkitPerformance || {}; document.write(“<br>”); for … Read more
WebGL is “OpenGL ES 2”, not plain OpenGL (the ES stands for ‘for Embedded Systems’). So there’s the first difference. OpenGL ES is essentially a subset of OpenGL. In addition, WebGL is almost the same as OpenGL ES 2, but has some subtle differences, explained in the link you provide. There’s not much to add … Read more
http://learningwebgl.com/blog/?p=11 (dead link as of Nov 2018, backup: https://web.archive.org/web/20180615095219/http://learningwebgl.com/blog/?p=11) Yes, I could recommend Light House 3D: http://www.lighthouse3d.com/tutorials/glsl-core-tutorial/ It’s not that complex, just focus on the code written on Learning webGL. I wouldn’t recommend working with some other library/engine at the start. Learn basics and later use libraries to speed up your coding. Learning webGL is … Read more
NOTE: three.js now supports THREE.RectAreaLight. This answer pertains to legacy versions of three.js. Your approach of using the point that maximizes the dot product is fundamentally flawed, and not physically plausible. In your first illustration above, suppose that your area light consisted of only the left half. The “purple” point — the one that maximizes … Read more
Based on my very limited understanding of what you’re trying to implement, it seems you would need to take the location of the intersection between the eye vector and the interior plane it hits, then trace it back to the light. To trace back to the light, you would first have to check if the … Read more
The excellent Three library has, in fact, a mechanism for detecting the following: WebGL support File API support Workers support For WebGL, particularly, here is the code that is used: function webgl_support () { try { var canvas = document.createElement(‘canvas’); return !!window.WebGLRenderingContext && (canvas.getContext(‘webgl’) || canvas.getContext(‘experimental-webgl’)); } catch(e) { return false; } }; That code … Read more
The state of which Vertex Attribute Arrays are enabled can be either bound to a Vertex Array Object (VAO), or be global. If you’re using VAOs, then you should not disable attribute arrays, as they are encapsulated in the VAO. However for global vertex attribute array enabled state you should disable them, because if they’re … Read more
In the most general sense, no. OpenGL and Direct3D only allow one index per vertex; the index fetches from each stream of vertex data. Therefore, every unique combination of components must have its own separate index. So if you have a cube, where each face has its own normal, you will need to replicate the … Read more