I don't usually like to just hand people capx's, but I think in your case, it will benefit you to try and learn from some of the things I've changed..

A few notes:

There is no need to put "every tick" everywhere. Any event that is not a trigger (with the little green arrow) happens every tick.

Also, every tick means 60 TIMES A SECOND.. so you can imagine that creating objects 60 times a second is not going to work well, performance-wise..

and lastly, I think you should do some research on C2's "picking" system.

Anyway, I hope you can learn from this:

https://drive.google.com/open?id=0B1Aaz ... lpjd2dNMTA

If you have any questions, feel free to respond here or PM me.

Somehow I got sucked in to investigating this.. It definitely happens to me too.. AMD Radeon 6800 if it helps..

I started playing around.. and this thing makes no sense..

I deleted everything from wertandrew's project except debugbox (sprite), limelight font (spritefont), and the playerwindows (sprite) (-- no 9-patches left!) and the bug is still there.

Deleting either the debugbox or the spritefont makes it go away.

OR

Taking the set color effect off of either of them makes it go away.

OR

Adding another effect to either of them also makes it go away.

So anyway.. not sure I've helped any, but it seems to me the 9-patch is irrelevant.. If it might help, here's the capx super simplified (no 9-patch) and still bugged: [link removed in lieu of new one]

EDIT: I just reopened that file and now it's not bugged.. so maybe it only stayed bugged after deleting all the stuff..

EDIT again: I went through my delete objects test again, but this time I left one more spritefont in.. the saved file still contains the bug (super simplified, no 9-patches). the "makes it go away" list above still applies, except that when deleting the playerfont spritefont, you don't see that it's fixed until you save and reload.. so confusing.

Here it is: https://drive.google.com/open?id=0B1Aaz ... UdBVEZxM2s

I think you need to simplify/take a few pieces out and see if it's still happening. If it is, I'd make a bug report.

Recreate the problem in as few events as possible (leave out the sliders and dictionary stuff and try running without a function). If it still happens, I'd say it's a bug. If it doesn't, you'll have a much better idea as to what's causing it..

Phew! Here's mine:

http://ludumdare.com/compo/ludum-dare-3 ... &uid=39200

http://ludumdare.com/compo/ludum-dare-3 ... &uid=39200

Having some fun with R0j0's mode7 plugin and a limited colour palette!

I'm in!

I have done some persistent world stuff with it using the FireBase plugin, (which I believe is pretty similar to photon). If you're just wanting a persistent world and aren't too dependent on split-second updates, it's definitely doable and not too insanely difficult. The split-second updates is probably doable, too, but as far as I can tell, it's insanely difficult..

That said, multiplayer is very head-twisting whether or not you have actual coding experience and I'd recommend making sure you have a very firm grasp on C2 and whatever plugin you decide to use before I'd even attempt it.

That is some pretty lighting!

I don't usually hand over capxs without explaining them, but I'm tired, and I'm sure you'll get it when you look at it.. so here ya go! <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

https://drive.google.com/open?id=0B1Aaz ... VFMdWlqRHc (download button in the top right corner)

Really lovely work!

If I had any money, I'd hire you for sure!

Maybe one day...

There are 5 games on Scirra.com...

Well said. I almost completely agree with you. But agreeing doesn't give us anything new to talk about.. so...

Well.. he said he had worked around the ONE problem (you kinda gave it a few labels, but it's still the same problem) that is caused by that. and it really isn't very hard to work around, so I didn't mention it. but yes, it does come with that problem.

I don't think either use is more proper than the other without being specific as to what the intended result is. In my mind, using lerp the way you suggested seems extraneous when there's so many built in ways to have things move or change size at a constant rate, which, I think, is why most people here in C2 land are using it for the smootherism.

I mean.. obviously the smoothing is not by accident.. tons of games and applications (big and small) use it that way.

Using it 'every tick' outside of ticks where you actually need it is obviously a whole other issue and would apply to either method..

That's only 2 cents from me. That's all I've got to spare (the exchange rate is not great...)