summaryrefslogtreecommitdiff
path: root/doc/classes/RigidBody.xml
diff options
context:
space:
mode:
Diffstat (limited to 'doc/classes/RigidBody.xml')
-rw-r--r--doc/classes/RigidBody.xml11
1 files changed, 5 insertions, 6 deletions
diff --git a/doc/classes/RigidBody.xml b/doc/classes/RigidBody.xml
index f3acd443b7..a1aa479ea1 100644
--- a/doc/classes/RigidBody.xml
+++ b/doc/classes/RigidBody.xml
@@ -1,17 +1,16 @@
<?xml version="1.0" encoding="UTF-8" ?>
-<class name="RigidBody" inherits="PhysicsBody" category="Core" version="3.0-stable">
+<class name="RigidBody" inherits="PhysicsBody" category="Core" version="3.1-dev">
<brief_description>
Physics Body whose position is determined through physics simulation in 3D space.
</brief_description>
<description>
This is the node that implements full 3D physics. This means that you do not control a RigidBody directly. Instead you can apply forces to it (gravity, impulses, etc.), and the physics simulation will calculate the resulting movement, collision, bouncing, rotating, etc.
- This node can use custom force integration, for writing complex physics motion behavior per node.
- This node can shift state between regular Rigid body, Kinematic, Character or Static.
- Character mode forbids this node from being rotated.
- As a warning, don't change RigidBody's position every frame or very often. Sporadic changes work fine, but physics runs at a different granularity (fixed hz) than usual rendering (process callback) and maybe even in a separate thread, so changing this from a process loop will yield strange behavior.
+ A RigidBody has 4 behavior [member mode]s: Rigid, Static, Character, and Kinematic.
+ [b]Note:[/b] Don't change a RigidBody's position every frame or very often. Sporadic changes work fine, but physics runs at a different granularity (fixed hz) than usual rendering (process callback) and maybe even in a separate thread, so changing this from a process loop will yield strange behavior. If you need to directly affect the body's state, use [method _integrate_forces], which allows you to directly access the physics state.
+ If you need to override the default physics behavior, you can write a custom force integration. See [member custom_integrator].
</description>
<tutorials>
- http://docs.godotengine.org/en/3.0/learning/features/physics/physics_introduction.html
+ http://docs.godotengine.org/en/3.0/tutorials/physics/physics_introduction.html
</tutorials>
<demos>
</demos>