javascript
/
three.js
spogulis no https://github.com/tazdij/three.js.git


			
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252
							<!DOCTYPE html>
<html lang="en">
	<head>
		<meta charset="utf-8">
		<base href="../../" />
		<script src="list.js"></script>
		<script src="page.js"></script>
		<link type="text/css" rel="stylesheet" href="page.css" />
	</head>
	<body>
		<h1>[name]</h1>
		<div>
			<p>All objects by default automatically update their matrices if they have been added to the scene with</p>
			<code>
var object = new THREE.Object3D;
scene.add( object );
			</code>
			or if they are the child of another object that has been added to the scene:
			<code>
var object1 = new THREE.Object3D;
var object2 = new THREE.Object3D;

object1.add( object2 );
scene.add( object1 ); //object1 and object2 will automatically update their matrices
			</code>
		</div>

		<p>However, if you know object will be static, you can disable this and update the transform matrix manually just when needed.</p>

		<code>
object.matrixAutoUpdate  = false;
object.updateMatrix();
		</code>

		<h2>Geometries</h2>
		<div>
			<h3>[page:BufferGeometry]</h3>
			<div>
				<p>
					BufferGeometries store information (such as vertex positions, face indices, normals, colors,
					UVs, and any custom attributes) in [page:BufferAttribute buffers] - that is,
					[link:https://developer.mozilla.org/en-US/docs/Web/JavaScript/Typed_arrays typed arrays].
					This makes them generally faster than standard Geometries, at the cost of being somewhat harder to
					work with.
				</p>
				<p>
					With regards to updating BufferGeometries, the most important thing to understand is that
					you cannot resize buffers (this is very costly,	basically the equivalent to creating a new geometry).
					You can however update the content of buffers.
				</p>
				<p>
					This means that if you know an attribute of you BufferGeometry will grow, say the number of vertices,
					you must pre-allocate a buffer large enough to hold any new vertices that may be created. Of
					course, this also means that there will be a maximum size for your BufferGeometry - there is
					no way to create a BufferGeometry that can efficiently be extended indefinitely.
				</p>
				<p>
					We'll use the example of a line that gets extended at render time. We'll allocate space
					in the buffer for 500 vertices but draw only two at first, using [page:BufferGeometry.drawRange].
				</p>
				<code>
var MAX_POINTS = 500;

// geometry
var geometry = new THREE.BufferGeometry();

// attributes
var positions = new Float32Array( MAX_POINTS * 3 ); // 3 vertices per point
geometry.addAttribute( 'position', new THREE.BufferAttribute( positions, 3 ) );

// draw range
drawCount = 2; // draw the first 2 points, only
geometry.setDrawRange( 0, drawCount );

// material
var material = new THREE.LineBasicMaterial( { color: 0xff0000, linewidth: 2 } );

// line
line = new THREE.Line( geometry,  material );
scene.add( line );
				</code>
			 	<p>
					Next we'll randomly add points to the line using a pattern like:
				</p>
				<code>
var positions = line.geometry.attributes.position.array;

var x = y = z = index = 0;

for ( var i = 0, l = MAX_POINTS; i < l; i ++ ) {

    positions[ index ++ ] = x;
    positions[ index ++ ] = y;
    positions[ index ++ ] = z;

    x += ( Math.random() - 0.5 ) * 30;
    y += ( Math.random() - 0.5 ) * 30;
    z += ( Math.random() - 0.5 ) * 30;

}
				</code>
				<p>
					If you want to change the <em>number of points</em> rendered after the first render, do this:
				</p>
				<code>
line.geometry.setDrawRange( 0, newValue );
				</code>
				<p>
					If you want to change the position data values after the first render, you need to
					set the needsUpdate flag like so:
				</p>
				<code>
line.geometry.attributes.position.needsUpdate = true; // required after the first render
				</code>

				<p>
					[link:http://jsfiddle.net/w67tzfhx/ Here is a fiddle] showing an animated line which you can adapt to your use case.
				</p>

				<h4>Examples:</h4>
					[example:webgl_custom_attributes WebGL / custom / attributes]<br />
					[example:webgl_buffergeometry_custom_attributes_particles WebGL / buffergeometry / custom / attributes / particles]


			</div>

			<h3>[page:Geometry]</h3>
			<div>
				<p>
					The following flag control updating of various geometry attributes. Set flags only
					for attributes that you need to update, updates are costly. Once buffers
					change, these flags reset automatically back to false. You need to keep setting them to
					true if you wanna keep updating buffers. Note that this applies only to [page:Geometry]
					and not to [page:BufferGeometry].
				</p>
				<code>
var geometry = new THREE.Geometry();
geometry.verticesNeedUpdate = true;
geometry.elementsNeedUpdate = true;
geometry.morphTargetsNeedUpdate = true;
geometry.uvsNeedUpdate = true;
geometry.normalsNeedUpdate = true;
geometry.colorsNeedUpdate = true;
geometry.tangentsNeedUpdate = true;
				</code>

				<p>
					In versions prior to [link:https://github.com/mrdoob/three.js/releases/tag/r66 r66] meshes
					additionally need the <em>dynamic</em> flag enabled (to keep internal typed arrays):
				</p>

				<code>
		//removed after r66
		geometry.dynamic = true;
				</code>

				<h4>Example:</h4>
					[example:webgl_geometry_dynamic WebGL / geometry / dynamic]<br />
			</div>

		</div>


		<h2>Materials</h2>
		<div>
			<p>All uniforms values can be changed freely (e.g. colors, textures, opacity, etc), values are sent to the shader every frame.</p>

			<p>Also GLstate related parameters can change any time (depthTest, blending, polygonOffset, etc).</p>

			<p>Flat / smooth shading is baked into normals. You need to reset normals buffer (see above).</p>

			<p>The following properties can't be easily changed at runtime (once the material is rendered at least once):</p>
			<ul>
				<li>numbers and types of uniforms</li>
				<li>numbers and types of lights</li>
				<li>presence or not of
					<ul>
						<li>texture</li>
						<li>fog</li>
						<li>vertex colors</li>
						<li>skinning</li>
						<li>morphing</li>
						<li>shadow map</li>
						<li>alpha test</li>
					</ul>
				</li>
			</ul>

			<p>Changes in these require building of new shader program. You'll need to set</p>
			<code>material.needsUpdate = true</code>

			<p>Bear in mind this might be quite slow and induce jerkiness in framerate (especially on Windows, as shader compilation is slower in DirectX than OpenGL).</p>

			<p>For smoother experience you can emulate changes in these features to some degree by having "dummy" values like zero intensity lights, white textures, or zero density fog.</p>

			<p>You can freely change the material used for geometry chunks, however you cannot change how an object is divided into chunks (according to face materials). </p>

			<h3>If you need to have different configurations of materials during runtime:</h3>
			<p>If the number of materials / chunks is small, you could pre-divide the object beforehand (e.g. hair / face / body / upper clothes / trousers for a human, front / sides / top / glass / tire / interior for a car). </p>

			<p>If the number is large (e.g. each face could be potentially different), consider a different solution, such as using attributes / textures to drive different per-face look.</p>

			<h3>Examples:</h3>
			[example:webgl_materials_cars WebGL / materials / cars]<br />
			[example:webgl_postprocessing_dof WebGL / webgl_postprocessing / dof]
		</div>


		<h2>Textures</h2>
		<div>
			<p>Image, canvas, video and data textures need to have the following flag set if they are changed:</p>
			<code>
				texture.needsUpdate = true;
			</code>
			<p>Render targets update automatically.</p>

			<h3>Examples:</h3>
			[example:webgl_materials_video WebGL / materials / video]<br />
			[example:webgl_rtt WebGL / rtt]

		</div>


		<h2>Cameras</h2>
		<div>
			<p>A camera's position and target is updated automatically. If you need to change</p>
			<ul>
				<li>
					fov
				</li>
				<li>
					aspect
				</li>
				<li>
					near
				</li>
				<li>
					far
				</li>
			</ul>
			<p>
				then you'll need to recompute the projection matrix:
			</p>
			<code>
camera.aspect = window.innerWidth / window.innerHeight;
camera.updateProjectionMatrix();
			</code>
		</div>
	</body>
</html>