no i am doing the entirely fun process of handling everything regarding objects within lua
actually it looks like there's weird stuff going on with how mmf runs collisions; i made a quick test app that had the same "late" collision problem i'm having now
however, after screwing around with it, apparently the collisions are actually being called "on time", but most actions seem to run a frame later... or something. pasting however DOES paste at the point the moving object first touches the stationary one
so anyway, you'll notice that the falling object
pastes immediately when it collides (EDIT: apparently it doesn't, but it DOES paste at that position a frame later), but the stationary objects don't change their transparency until a frame later... but both actions are being called by a collision event, so they should both happen within the same frame
so there's 2 things i can think of that's going on here:
1. mmf calls collision events on frame n but you don't see the effects until frame n+1 (gay; these are triggered conditions are they not)
2. it caches object data during a collision and instead of calling collision events on frame n, calls them on frame n+1 with that data (the other one seems more likely)
This post has been edited by Xgoff on Jun 8 2009, 12:21 AM