- 20 2月, 2011 10 次提交
-
-
由 Mr.doob 提交于
Object3D::matrixNeedsToUpdate ⟶ Object3D::matrixNeedsUpdate
-
由 Mr.doob 提交于
-
由 Mr.doob 提交于
-
由 Mr.doob 提交于
Renamed examples.
-
由 Mr.doob 提交于
-
由 alteredq 提交于
-
由 Mr.doob 提交于
-
由 Mr.doob 提交于
Figured out why Canvas/SVG wasn't rendering... someone changed camera.near/far to camera.zNear/zFar :P
-
由 alteredq 提交于
Still with weird error reports in Firefox (though it work despites them).
-
由 alteredq 提交于
This is lifted from greggman's ThreeD http://code.google.com/p/threedlibrary/ Also modified ribbons example to show how to use this.
-
- 19 2月, 2011 2 次提交
-
-
由 alteredq 提交于
It provides a lean way how to render TRIANGLE_STRIP primitives: needs just n+2 vertices for n triangles (one Ribbon = one strip). There are no faces, no indices, everything is rendered in one simple drawArray call. Vertex colors are supported, normals not yet.
-
由 alteredq 提交于
- removed unnecessary normal matrix computation in hierarchies (this is already done in renderer) - removed unnecessary enabling of attribute arrays in every frame (it's enough to do it when shader program is created) - depth test is now only set if it changed
-
- 18 2月, 2011 1 次提交
-
-
由 alteredq 提交于
- getters/setters are no more in Vector3 - object hierarchies thus don't use "isDirty" - this was completely killing performance for anything that was touching a lot of Vector3 like creation of meshes and dynamic buffers - even without this, performance of hierarchies went up (a lot) - objects do not get passed renderer anymore - camera was almost also removed, but this is useful for LOD (though there may be some cleaner way to do this?) - material ids are now unified, this makes "geometry.sortFacesByMaterial" faster (thus scene init / GUI blocking is shorter) - all WebGL examples should work now (render-to-texture has weird lights and in some camera control feels different) - CanvasRender still broken, despite many efforts :( - currently only points and lines work, faces don't show up. I think this may need assistance from mrdoob.
-
- 17 2月, 2011 4 次提交
-
-
由 alteredq 提交于
We have been very lucky - setters / getters were not supported till just 2 hours ago (so fresh, I had to build Closure myself from their repo ;). http://code.google.com/p/closure-compiler/issues/detail?id=249 Also some refactoring plus added hackish animation offset feature.
-
由 alteredq 提交于
-
由 alteredq 提交于
Just one hardcoded shader for the moment. Everything needs to get cleaned / bugfixed / optimized.
-
由 alteredq 提交于
Otherwise things are very much work in progress, expect everything to be broken.
-
- 15 2月, 2011 4 次提交
-
-
由 alteredq 提交于
Work in progress. As with static objects, faster with OpenGL (34 -> 38 fps) and slower with ANGLE (30 -> 27 fps).
-
由 alteredq 提交于
Also fixed subtle bug in `materials_gl` example: face.material => face.materials (since renaming this example was just silently broken)
-
由 alteredq 提交于
-
由 alteredq 提交于
Also fixed quads vertex color bug in WebGLRenderer and did small optimization of face state handling.
-
- 14 2月, 2011 6 次提交
-
-
由 alteredq 提交于
On my notebook WebGLRenderer now 35% faster than WebGLRenderer2 (in OpenGL, in ANGLE it's still 15% slower, go figure).
-
由 alteredq 提交于
Small optimizations: skipped flattening in 3x3 matrix inversion and uploading camera position uniform only for materials where it's used.
-
由 alteredq 提交于
This should affect only use cases with lots of animated objects (unlike current performance tests where object matrices are not updated).
-
由 alteredq 提交于
As for particles, performance should be the same just using less memory.
-
由 alteredq 提交于
Refactored WebGLRenderer to be able to handle MeshShaderMaterial also for Lines and ParticleSystems. It is now object type that determines which type of primitives is going to be used (triangles / lines / line strips / points).
-
由 alteredq 提交于
-
- 13 2月, 2011 3 次提交
-
-
由 alteredq 提交于
That was painful; hopefully since now it should be easier to have it in every WebGL example. It's enough to add one line (ideally as the first thing that gets executed): if ( ! THREE.Supports.webgl ) THREE.Supports.addGetWebGLMessage(); This will add message box with default styling centered near top of the window. Optional parameters "parent" and "id" can be specified for further customization and integration with the document, also message DOM element is returned for easier access. var messageElement = THREE.Supports.addGetWebGLMessage( { parent: container, id: "my_message" } ); By default, message is added to document.body and has id "oldie" (can be styled with CSS).
-
由 alteredq 提交于
Created "THREE.Supports" object, which should centralize this stuff. So far it detects <canvas>, WebGL and WebWorkers; later it could detect for example GPU capabilities. Not sure about name or location, but it's pretty tiring go through all examples when something changes, so it should be somewhere in the library. Code duplication is bad: even html snippets with error message should be centralized somewhere, so that when new browsers arrive we wouldn't have to keep changing them in many places.
-
由 alteredq 提交于
-
- 12 2月, 2011 10 次提交
-
-
由 alteredq 提交于
There shouldn't be performance difference, just less memory used (indices were not used anyways).
-
由 alteredq 提交于
WebGLRenderer now as fast as WebGLRenderer2.
-
由 alteredq 提交于
Many balls demos now noticeably faster ;)
-
由 alteredq 提交于
-
由 alteredq 提交于
Also doing less matrix multiplications (though this just seems to have shifted bottleneck elsewhere).
-
由 Mr.doob 提交于
-
由 alteredq 提交于
-
由 alteredq 提交于
-
由 alteredq 提交于
-
由 alteredq 提交于
-