Преглед изворни кода

Revert "Docs: Add note about non-uniform scaling to FAQ. (#22810)" (#22818)

This reverts commit 6f93950b56ebb6b2daccaa6bc187502cdfd59e43.
Michael Herzog пре 3 година
родитељ
комит
9eea8cc818
1 измењених фајлова са 0 додато и 10 уклоњено
  1. 0 10
      docs/manual/en/introduction/FAQ.html

+ 0 - 10
docs/manual/en/introduction/FAQ.html

@@ -51,15 +51,5 @@ visible_height = 2 * Math.tan( ( Math.PI / 180 ) * camera.fov / 2 ) * distance_f
 			This could be because of face culling. Faces have an orientation that  decides which side is which. And the culling removes the backside in normal circumstances. To see if this is your problem, change the material side to THREE.DoubleSide.
 			<code>material.side = THREE.DoubleSide</code>
 		</p>
-
-		<h2>Why is non-uniform scaling problematic?</h2>
-		<p>
-			Applying non-uniform vector components like (1, 2, 1) to [page:Object3D.scale] results in so called non-uniform scaling. This type of transformation is only partially
-			supported by three.js since certain methods like [page:Object3D.attach]() do not properly handle it. The most common error appears when an object has a non-uniformly scaled parent.
-			In this case, it is not possible to decompose the object's world matrix which eventually breaks subsequent code.
-		</p>
-		<p>
-			To avoid situations like that in the first place try to avoid non-uniform scaling whenever possible.
-		</p>
 	</body>
 </html>