hi, first post
i have a couple of problems that i can't solve;
1- when pasting objects onto backdrops in TGF inside a fastloop, does it always cause an illegal op, or is it just me (i know i can get around this by using MMF btw, but i dont have the full version).
2- ordering of events, say i have moving objects that push other objects, if the LAST event in the whole program updates the position of the object being pushed, why do they appear to be overlapping slightly, no mater how accurate the event is, or regardless of whether i use 'always' or even a heap of fast loops. isn't the screen rendered once at the end of each event list iteration?
Iím not pasting more than 256 objects I know, Iíve tested it without the loop with counters, just inside a loop it crashes, plus its destroying the objects, so thereís never more than 5 on the screen, but its doing a LOT of pasting so I solved it by toning down the loop speed <- should've tested that before .
It was still crashing at far less than 256 looped pastes before, at first I missunderstood what you said but thanks for the tip I never knew that...
And secondly Iím not using built movements, its custom movement, Iím making springing platforms that have inertia that bounce of each other, but they always slightly overlap (or severely overlap dependin on on the speed), so I'm still baffled, and all the examples here of moving platforms and whatnot are imperfect.
About the second question, it overlaps because you tell the object to move a certain number of pixels per loop or whatever, instead use a fastloop a certain number of times (how fast you want it) and make the object move 1 pixel per loop
Yeah I know I know, Iím well overdue for an upgrade, Iíll wait for MMF2 I think, thereís (what I think is) a good reason why I hav'nt upgraded to MMF, but judging by some of the other posts here, I think peaople will yell at me if I say why
And klikmaster, it (everything) only moves 1 pixel per loop, thatís how I do all my movements, it doesn't make a difference, neither does the order of events, which is what i orignially thought shouldv'e fixed it. I.e logically speaking if the LAST event moves an object to the position of another object (which has moved 1 pixel in a previous event) shouldnt it appear pixel perfect? But it doesn't, thatís the problem. I'm sure I'll figure it out in the end, my games getting a bit to complex i think, thanks for your insightss fellas.
i dont wanna give away my game code obviously, see if the last event updates the position of something it shouldnt it always be in front of (or in line with) the other object, because its moved the same distance? the second bit is dodgy i know, but why does it overlap
ARg! I got it dont worry, that examples all wrong and stupid, I should've known better, thanks for your tips Tigerworks, I just didnt think to reorder the conditions in the events rather than the events themselves, I just assumed I had it right and never checked it again, o well