Irrlicht Engine

rogerborg wrote:Heh, it appears to be radians per millisecond. I mean, obviously!

We can either comment it as that, or change it to (e.g.) degrees per second in 1.6. Opinions?

Ah-Ha, Venus is now going the correct speed around my Sun, thank you..

Could be units per second...

Hmm. I took Calc III 3 times, you'd think I'd remember this should work...

Perhaps per ms? I dug out some code..




void CSceneNodeAnimatorFlyCircle::init()
{
Direction.normalize();

if (Direction.Y != 0)
VecV = core::vector3df(50,0,0).crossProduct(Direction ...

Could be units per second...

Hmm. I took Calc III 3 times, you'd think I'd remember this should work...



void CSceneNodeAnimatorFlyCircle::init()
{
Direction.normalize();

if (Direction.Y != 0)
VecV = core::vector3df(50,0,0).crossProduct(Direction).normalize();
else
VecV = core::vector3df ...

What exactly is the units for this "speed" value? I tried setting it to 1 guessing it would be one orbit/sec and was wrong.

createFlyCircleAnimator (
center vector3df(x,y,z),
f32 radius=100.f,
f32 speed=0.001f,
direction vector3df(x,y,z)
);

I can create a simple program with basically one shape and an FPS camera. When I try to use the keys, they are printing out in the console that I ran the program from rather than going to the program itself.

I was playing with the tutorials and I managed to get terrain rendered from a height map and draw a texture on it. I then stuck a FPS camera in and walked around my newly created terrain. It seems like the edges of my terrain are growing as I walk towards them so its hardly rendering the entire ...