I have a question about the command TIME.
I know you use TIME to adjust your code to make the game run relatively the same speed on different machines BUT!, when exaclty should you use it?

This comes about from me working on 2 diffent PC's, 1 has an INTEL815 inegrated video chip set & runs much slower then my Gforce2mx machine.

I'm still doing my car code & I've been using TIME liberally through the code but I think it may be causing problems.

Look at this pseudo code:
//----------------------------------
Accel = Keyforce.X * 0.75;
Drag = Speed * TIME * 0.005;
Speed = Speed + TIME * (Accel - Drag);

Temp.x = Speed * TIME * 0.5;
Temp.y = 0;
Temp.z = 0;

Distance = ent_mov(Temp,nullvector);
//----------------------------------
Is it ok to use TIME in 3 places or should I only use it in the line;
Temp.x = Speed * TIME * 0.5;

I'm also using TIME multiple times throughout my steering & gravity code.

Should it only be used ONCE within every movement you want. I ask this as things end using TIME multiplied by itself 3 times thoughout the codes cycle.

Now I ask this because the when I change the resolution on the Intel815 machine the speed of the car changes, it has readouts of speeds & gravity & such, & they change depending on the resolution I run in.

Any ideas appreciated...

I am currently having some problems with TIME also, read this forum: Swaying Code Problem.... I still am working on the problem but the forum is still going and i have no idea what i am doing.
-matt

shovel,

I have not yet done exhaustive testing across multiple platforms, but I always make a point of doing all my calculations first with the regular numbers and formulas.

Then, just before the move, rotate, or whatever statement, I vec_scale my vector by time and then apply it. This has worked great for me so far.

-WildCat

Thanks Wildcat, your info is good for movement vectors but there are times when you are doing calculations that don't use vectors.
I might have to revisit my code and see if the outcome I want can be served by using the vector method you describe.

I think you are on the correct track in that you only apply the TIME once per movement.

Anymore than this seems to cause problems.

I am no time correction expert (actually, I am having my problems with it), but if you don't use vector, I think you could do it just and only before every wait(1) instruction. I think this could work because the problem is all in the duration of the frame cicle.