Changeset 2908 for code/branches/questsystem5/src/bullet/BulletCollision/CollisionShapes/btHeightfieldTerrainShape.h

Timestamp:

Apr 8, 2009, 12:58:47 AM (16 years ago)

Author:

dafrick

Message:

Reverted to revision 2906 (because I'm too stupid to merge correctly, 2nd try will follow shortly. )

Location:

code/branches/questsystem5

Files:

• . (modified) (1 prop)
• src/bullet/BulletCollision/CollisionShapes/btHeightfieldTerrainShape.h (modified) (2 diffs)

code/branches/questsystem5/src/bullet/BulletCollision/CollisionShapes/btHeightfieldTerrainShape.h

@@ -30 +30 @@
   center (as determined by width and length and height, with each
   axis multiplied by the localScaling).
-
-  \b NOTE: be careful with coordinates.  If you have a heightfield with a local
-  min height of -100m, and a max height of +500m, you may be tempted to place it
-  at the origin (0,0) and expect the heights in world coordinates to be
-  -100 to +500 meters.
-  Actually, the heights will be -300 to +300m, because bullet will re-center
-  the heightfield based on its AABB (which is determined by the min/max
-  heights).  So keep in mind that once you create a btHeightfieldTerrainShape
-  object, the heights will be adjusted relative to the center of the AABB.  This
-  is different to the behavior of many rendering engines, but is useful for
-  physics engines.
 
   Most (but not all) rendering and heightfield libraries assume upAxis = 1
@@ -100 +89 @@
         btVector3       m_localScaling;
 
-        virtual btScalar        getRawHeightFieldValue(int x,int y) const;
+        virtual btScalar        getHeightFieldValue(int x,int y) const;
         void            quantizeWithClamp(int* out, const btVector3& point,int isMax) const;
         void            getVertex(int x,int y,btVector3& vertex) const;