Asking other users to circumvent license restrictions is not allowed. Closing.

Or put them in a separate event sheet. That's what I do.

There are also free sprites and game art on the web, some of it is even free for commercial use.

daehawk : seeing your code, it seems like you use many events to do the same thing. Also, the way your events are setup, everything is being evaluated on every single tick. It may cause issues later not only as far as performances are concerned (on lower end devices), but it can also provoke bugs.

While running some events every tick can cause performance problems on some platforms if the events are intensive enough (collision detection is more intensive than checking a variable, for example), running events every tick, by itself, will not cause bugs. There's a misconception going around that using every tick is bad, but it's really not.

Use 'on any touch start' instead of 'on touched boxes.' That will be more accurate, since the event will run even if the user misses a box by a little bit.

Give the family a variable, 'selected.' Then all objects in the family have that variable. Have events like this:

On any touch start

Pick nearest boxes to touch.x, touch.y

If distance(touch.x, touch.y, boxes.x, boxes.y) is less than whatever amount

• set family variable 'selected' to 1

If boxes variable 'selected' = 1

• set boxes position to touch.x, touch.y

On touch 0 end

• set boxes variable 'selected' to 0

If you're not sure how picking works, I suggest going through the starter tutorials if you haven't already.

What you're looking for is the 'pick nearest' condition, and you can use it with a family for all your boxes like so:

On touch

Pick nearest boxes to touch.x, touch.y

If distance(touch.x, touch.y, boxes.x, boxes.y) is less than whatever amount

That will ensure that only one instance is picked, and only if it's close enough to the location touched. If your sprites require a non-centered hotspot, than you can use a 'grip' sprite as you mentioned in the same way.

No worries, I understand the frustration of trying to communicate across languages, and can empathize with no much being available only in a language you don't know (so many of those Japanese-only games, for example).

There are several Brazilian members on this forum (undoubtedly more than I'm aware of, as not all users mention their homeland) and I've never seen anyone look down at them or treat them negatively because of it (which totally wouldn't be allowed here if it were to happen), so you can feel at ease here.

And in case it wasn't clear from the language barrier, if you do get into a conversation with someone who speaks your language, feel free to continue your posts in both languages in your post one after the other, formatted like so:

Konichiwa.

Hi.

Still in the pipeline.

If that contributes, it's not the main cause. My computer only has one monitor.

JuniorTabanez Calling me lazy for not using google translate is the same as calling yourself lazy, because you don't want to use it either. This is an English forum. Being on a forum means you have to abide by the rules, and one of those rules is users speak in English. We cannot effectively moderate if we need to copy and paste messages one by one to translate. It would be extremely impractical considering how many posts are made if even a small fraction of them weren't in English. In addition, moderating this forum is not the only thing I have to do. Calling me lazy is just plain rude and simply isn't true. If I was truly lazy I wouldn't be a moderator, as it's not even a paying job. So please refrain from calling me lazy and abide by the forum rules.

I don't know what you mean by 'oh laziness' and 'let the lazy.' Are you calling me lazy?

That's odd, C2 doesn't have any motion blur at all. Motion blur is an expensive and/or difficult shader technique. Are you sure what you're experiencing isn't the pixel response time of your monitor? My previous monitor had a very good pixel response time, and had no blurring at all. Then I got a new one which has much better color and contrast, but a much worse pixel response time, and now objects 'smear' a bit when moving quickly.

Also, are you sure the stuff you're making is at 100% opacity? If clear background is off, and there's only 1 layer at 90% opacity, then you'll get a bit of ghosting (the previous image remaining partially visible).

Do you have screen video capture software? Fraps has a free version if you don't. Could you capture video of both something you made with this problem and something played also on your computer that's fast and doesn't have the problem? Even capturing just a screenshot of the effect would help to determine what it is. If you can't capture the effect, it's most likely your monitor.

As for the screen tearing, I notice I get tearing in Firefox but not chrome. Chrome has a flag that you can set to use vsync or not, but you should check your video card's settings, as I think some computers have override settings on a per-application basis, meaning setting chrome's flag might not fix it because the control panel is set to override it.