irrlicht/tests/tests-last-passed-at.txt

Tests finished. 72 tests of 72 passed.
Compiled as DEBUG
Test suite pass at GMT Sun Dec 31 17:50:49 2023
Add option to allow nodes to ignore the scale/rotation parts of their parents transformation. ISceneNode::setUpdateAbsolutePosBehavior can now control what ISceneNode::updateAbsolutePosition really does. Having only the position and not the rotation/scale of a child node affected by the parent transformation was previously impossible inside the scene-graph. So people always had to break the scene-graph and code it themselves. Old behaviour is default. Extra check for new variable has a small cost, thought new behaviour can actually be faster when it's used. git-svn-id: svn://svn.code.sf.net/p/irrlicht/code/trunk@6432 dfc29bdd-3216-0410-991c-e03cc46cb475 2022-09-29 18:34:37 +02:00			`Tests finished. 72 tests of 72 passed.`
			`Compiled as DEBUG`
Fix tessellation numbers in createCylinderMesh, createConeMesh, createArrowMesh Double tessellation numbers for these 3 functions in your code to get same results as in Irrlicht 1.8 I noticed in last commit those all tessellated semi-circles instead of circles. I just documented it there, but it's annoying as that bug doesn't allow odd numbered tessellation. So for example one couldn't create a triangle pyramid. I considered adding another parameter to describe what this number means, but... just too ugly. And it was always documented otherwise, so this could be considered a bug. Sorry if this changes the look of existing apps. Also cleaned up code in CGeometryCreator::createCylinderMesh. No idea what the idea behind old code was. Aside from creating twice the tessellation numbers. git-svn-id: svn://svn.code.sf.net/p/irrlicht/code/trunk@6581 dfc29bdd-3216-0410-991c-e03cc46cb475 2023-12-31 19:04:15 +01:00			`Test suite pass at GMT Sun Dec 31 17:50:49 2023`
Add option to allow nodes to ignore the scale/rotation parts of their parents transformation. ISceneNode::setUpdateAbsolutePosBehavior can now control what ISceneNode::updateAbsolutePosition really does. Having only the position and not the rotation/scale of a child node affected by the parent transformation was previously impossible inside the scene-graph. So people always had to break the scene-graph and code it themselves. Old behaviour is default. Extra check for new variable has a small cost, thought new behaviour can actually be faster when it's used. git-svn-id: svn://svn.code.sf.net/p/irrlicht/code/trunk@6432 dfc29bdd-3216-0410-991c-e03cc46cb475 2022-09-29 18:34:37 +02:00