Thanks a lot for your replies. Unfortunately, it hasn't solved the problem (thanks jcl for cleaning my code, though - I've amended it to how you suggested). The 'traps' section in the manual just says to create the new object *after* the object to which it's connected is moved, but I've done that. Also, there is no lag when I just join the origins, it's only when the origin of the new object is connected to the vertex of the other. In fact, the lag is only really noticable when jumping, but it is especially bad then... Thanks again, any more suggestions?

-

[This message has been edited by Ambit (edited 27 March 2001).]

Anyone? Any ideas would be really appreciated, I still haven't got rid of the lag... If anyone has linked a model using ent_vertex without any lag, you would be a veritable god if you could share the knowledge...

Thanks!!

You say that it shows when you jump? Could it be gravity related?

Have you disected your Jump script?

quote:

---

Originally posted by jcl:
Only beginners must use wait() inside while(). According to your forum status you are an expert. So you have now my permission to use while() without wait().

---

Hey jcl... Can I have permission too??

------------------
Thou shall not be afraid, for he who lies, fries. Most of the time.
--Logan Smith--

ASallade - thanks, that's a good idea, I'll examine that - maybe the movement.wdl is affecting it somehow.

Let me know if it works, I'll need your help next time

I've now messed around with the player movement script quite a lot, and can't see anything in the jump script that should be causing the lag... Any more ideas much appreciated...

Hallo Ambit,

I don't have any solutions, but I have an example that professionals have also similar problems. I just played the demo of GOTHIC: when my player runs around and jumps with a torch, the torch lags behind his hand!

I think, that it can't work with ent_vertex, because the cpu or whatever has to compute the relationships between the positions of the origin and the vertex everytime. It costs time over time to compute it. But it costs no time to hold the two origins of two entities in the same position, because the only has to be moved in an absolutly identical way. Maybe, this is stupied from an experts sight, I think it is the reason and one looses his time trying it again and again.

Achim

Hi Al,

Thanks for your input - sounds feasible (though I haven't played Gothic). I really hope that's not the case, though... Actually, the only reason I really need to get this working is because I wanted to use a hitbox system for a fighting game, so that each character would have an invisible box at his fists and feet that could be used to compute collisions. Even with the lag this might work, but it just wouldn't be so accurate. Maybe I should just rethink my strategy for controlling the collisions and reactions, though...
Cheers,
Ambit