So I have been looking into timing and such - and, obviously it's always "use dt for smooth and proper timing in C2" and "behaviours have dt built-in so they are accurate". I built a little test and there's some strangeness afoot - the longer it runs there's both more and more shift from the "reference" every second thing, but also between a behaviour and a simple +dt*X action.

I realise it can be fixed with some extra variables and math, but can that be avoided and reasonable accuracy expected with simple behaviour/dt usage? dt seems to be rounded down to 3 digits and the sum total in 1 second apparently almost never comes down to a clean 1? Or am I doing something wrong?

tictoctic - will you stop asking the creators to remove the free resources they give you? It's quite disrespectful - as several people have told you before custom work is paid, if you get something for free live with it being available to others as well.

Savvy001 - you mean like a vertical scrolling version? Or adding a Y coordinate to the current one (since it's locked to one direction so the "motion blur" makes sense - otherwise it would just be mush)?

Well, anyhow, I have now replaced Racetrack with Racetrack H and Racetrack V for all your racetrack needs

Try low quality, not high - low quality means nothing will mass with your art.

Either way thatserafimkid deserves some kinda of a little medal for that explanation post.

Or you could put them in a group and activate/deactivate the group as needed.

*1

But then it stays the same!

Looks like it's cropped wrong or kinda shifted diagonally within its image frame - quite weird. Are all of them like this? C2 does spritesheet your images when exporting, so something might be going wrong there.

Gone and done.

Somebody

Thanks, I figured eventually he would want to do expert mode and have a whole keyboard set. LOL

"Play this symphony to continue!"

Ther's a "Compare instance variable" picking event for sprites.