Object delay.....

[scottige]

Are there any clever fixes for the objects lagging 3 frames behind when positioning next to another object ?

Is there any plans to include imediate update style updates in a forthcoming patch or have the extension itself ported ?

[DavidN]

The problem occurs because of movements being handled after events that reposition objects. I put an article up on the Wiki detailing this: http://www.clickwiki.info/index.php/...inked_together

Basically, make sure any events dealing with movements come before those that set positions.

However, there was going to be a fix for this in build 242, but something went a bit wrong with it - now the lagging problem can be found no matter where your events are. I've found two very unlikely fixes for this:

1. Put a String or Counter object in the frame. (No, I don't know why either.)
2. If the lagging objects are counters, display them as background.

Here's a thread with an example:

http://clickteam.com/center/showflat.php/Cat/0/Number/17625/an/0/page/0#Post17625

[scottige]

I've tried all sorts of ways.

Some work better than others but I've not been able to totally erradicate it.

I even tried moving both objects on the same event using the same co-ords but they were out or synch still.

I know it's a known problem but you can normally find good work arounds for most bugs.

I know it's strange but some bugs are just accepted as the way it is.
It's a bit of a shame.
This was discussed in beta so I won't go into it again but imediate update was a perfect solution so it is possible.

I have a "Glow" object over a gun on a space ship but if you move more than a pixel at a time it lags behind wiggling all over the place.
I had to remove it in the end as it looked naff.

Hopefully it will be addressed in a patch.

[Nifflas]

Well, there was two nice solutions in the last post. Since it is the nature of mmf, rather than a bug, I doubt it will be fixed. Just create an invisible object, and assign the movement to it. Link all other ones to the invisible object. It will look perfect, there will only be a 2ms lag between the visible and invisible object at 50fps. It's reasonable.

[DavidN]

Apparently it has been fixed - just that there was a problem with the fix as well, and we'll see it in build 243.

[Nifflas]

Oh? Neat <img src="/center/images/graemlins/smile.gif" alt="" /> I didn't think it was a bug / would be changed. I always looked it as being the mmf nature.

[scottige]

[] Since it is the nature of mmf [/]

That's what I was meaning by an accepted bug <img src="/center/images/graemlins/smile.gif" alt="" />.
People see it as "Just the way mmf is" and not a bug because it's been like that forever.

That posted example does seem to do the trick, would just be nice not have to work around.