What it does
Object3DPhysicsAngularVelocity writes to a 3DPhysics object: it sets rather than reads. It takes objID (an integer), angX (a float), angY (a float), angZ (a float) and initialSpeed (a float), and returns nothing. That is the first of 2 forms. objID is the id of a 3D object, the one LoadObject returned: it is how the call knows what to act on.
Syntax
1
Object3DPhysicsAngularVelocity(objID integer, angX float, angY float, angZ float, initialSpeed float)2
Object3DPhysicsAngularVelocity(objID integer, vectorID integer, initialSpeed float)Parameters
| Name | Type | In forms |
|---|---|---|
| objID | integer | all |
| angX | float | 1 |
| angY | float | 1 |
| angZ | float | 1 |
| initialSpeed | float | all |
| vectorID | integer | 2 |
Every form returns
nothing
Example · generated
Form 1, with every argument
object = LoadObject("assets/media.obj")Object3DPhysicsAngularVelocity(object, 1.0, 1.0, 1.0, 1.0)DO Sync()LOOPForm 2, the short one
object = LoadObject("assets/media.obj")Object3DPhysicsAngularVelocity(object, 1, 1.0)DO Sync()LOOPLoadObject is there to give the call something to act on; Object3DPhysicsAngularVelocity is the line that matters. The DO … LOOP is not decoration: a classic BASIC program ends the moment it runs out of lines, and Sync() is what draws the frame.