I want to use c_move to move an entity in metres/second. 1 metres = 0.03125 quants. If skill1 contains the speed (in metres per second), how can I impelment this?

Thanks.

AFAIK, vars/defines are limited to 3 decimal places

DEFINE quant2meter = 0.031;

temp.x = my.speed * quant2meter * time_step;
temp.y = 0;
temp.z = 0;
move_mode = glide;
c_move(my, temp, nullvector, move_mode);

It doesn't seem to work right. I need to make it cover 'speed' number of metres (quants * 0.03125) every real-time second.

I appreciate the help.

So first of all, you want to make your entity move with actually metres (in quants that is) per real time second. The real time second is just a simple calculation via this line:
Code:

---

 
time_step / 16;

---

I would advice you to use time_smooth. If time_step changes suddenly, the speed becomes inaccurate during the next frame, adding to the noticeable jerk. This can be prevented by the time_smooth variable.

Code:

---

  
(constant_speed * (metres_in_quants * (time_step / 16)));

---

I guess this should do the trick. It's a simple theory but you could improve it using physics I guess. This exemple is in figure speech a 'poor man's physics' example

Cheers

Frazzle

mhh maby i have a strange feeling but maby this helps

my.speed * quant2meter *(time_step/time_step)

Thanks everyone.

I got it now. The constant METERTOQUANT is 32, so he is moving MovementSpeed number of 32 quants every second.

Code:

---

my.MovementSpeed * METERTOQUANT * (time_frame / 16);

---

Nice to see, but one question I have is, why you use time_frame ??
Probably because of the potential sudden fps increase/decrease

Cheers

Frazzle

I used it in my RTS for the military clock. I added "(time_frame / 16)" every frame and it looked like a very accurate way of telling the seconds (when converted to an integer), no matter what frame rate. It also worked in this movement code, so I must be doing something right

I guess it is more accurate because it changes with the frame rate, whereas time_step doesn't, expecially with fps_lock active.

with movement, you'll want to use time_step.

with time, (as mentioned by sheefo), you'll want to use time_frame