Here's your .capx, with automatic car following and drift lines.

The Follower's AI is quite dumb, but it does its job and doesn't consume much memory.

Download .capx

cristiart

You can simply add an array, and add an action when the SweetAlert2 is closed:

[Array]: Load from JSON: SweetAlert2.GetLastValue.

glerikud

Just looked through your .capx.

Awesome! Thanks! Short code, big result.

Sorry, but what exactly are you using Word2 for?

And what do you mean by "preset"? Do you mean the possibility to create scrollers whenever you want?

99Instances2Go if they weren't deleted by ZephyrKing

Might be possible.

But yeah, if you still got the autosave files, you are saved.

—

i re-attached the limbs to the body on a order where you wold be able to cut them off without worrying to much about the body flying away

Yeah, managed to do that too, but I was wondering why you have to do that since the "Remove all joints" action is supposedly removing "all joints that are connected to or from an object". If that was the case, it wouldn't matter where you start the joint right?

And thanks for explaining the image point 0 - center of mass issue!

(by the way, the .capx still doesn't work in r239..)

—

Nevermind, managed to download it. Thanks for your help!

Providing your .capx would make this a lot easier.

Go to "file" -> "Save as single file"

And upload that to somewhere (preferably dropbox) and provide the shared link, please.

what do you mean? The link to the .capx is there

Sorry, somehow read over that.

Um...

It looks like the actual project is missing...

See this (sorry for German language. "name | size | packed size | ..."):

Usually, there is a [projectname].caproj and [projectname].uistate.xml in there too.

Those two are missing. Everything else is there, animations, event sheets, ...

I have no idea why that is. Maybe a anti-virus program thought that might be a virus, no idea.

Anyways, let's go on how to fix this.

I'm in no way capable of interpreting the.caproj and .xml 100% correctly, but it looks like it's just two xml's with project info, nothing relevant.

I'd say what you can try is to create those two file manually, fill in what you know or remember of your project, add the two files to your .capx and try to open it again.

Here are the file's contents with what I extracted from one of my projects:

[projectname].caproj

[projectname].uistate.xml

Create the two files from scratch, paste my contents and edit it to your project's information.

Remember to name the two files accordingly.

Since you need the plugin's names and id's of the plugins you used in your project for the .caproj, you might need to ask the plugin developers for help there. Or you can try to find those two values by searching in the .js files in the plugin's folder.

If everything fails, you might wanna call to Ashley , maybe he can help you with reconstructing the two files.

(All assuming that those two files are the only things that are missing)

—

aimAngle > 0 ? aimAngle : (18+(18-abs(aimAngle)))[/code:vqkqin9w]
Actually, that looks complicated, but what it does, is simple.

The thing is:
In my .capx, I use the [b]angle expression[/b] to determine the way the turret has to look and, thus, which animation frame to use.
A problem with the [b]angle[/b] expression is that it doesn't return the angle from 0-360, but from 0-180 and from -180-0.
Look at this (notice how the angle goes negative and decreases when it should stay positive and increase):
[img="http://i.giphy.com/3o6ZtcK4c943yreacM.gif"]

Now, to use the variable [i]aimAngle[/i] for the animation frames, it needs to have the range 0-360 (because the animation frames go from 0 to 36), not 0-180 & -180-0.

That's why I need to convert [i]aimAngle[/i] to a positive value each time it is below 0 (i.e. negative and not usable).
(in my .capx, the 18 actually stands for 180 degrees. Since [i]aimAngle[/i] is already the normal angle divided by 10, it's 18 in the code. But I'll refer to 180 in the following since everything else is easier to understand then)

Since you now know what the [b]?[/b] does, I'll only look at [b](180+(180-abs(aimAngle)))[/b]
which is the conversion from everything from -180-0 to 180-360.

[u]Let's take an example:[/u]
[i]aimAngle[/i] is -170.
We need it to be 190 (according to what I mentioned above).
Initial code looks like this:
 [b](180+(180-abs(-170)))[/b]

First of all, we need to make the negative [i]aimAngle[/i] positive. We do so by using [i]abs[/i].
Now, [i]aimAngle[/i] is positive and we have this: [b](180+(180-170))[/b]
Now, we substract [i]aimAngle[/i] from 180 to get the rotation that needs to be done to go from 180 to the [i]aimAngle[/i] we want (190).
That leaves us with this: [b](180+10)[/b]

And there we go: 190 is the result, exactly what we want.

I hope, I was clear enough.
[b]Got any more questions? PM me, please, so we don't have to spam this thread with off-topic stuff. ;)[/b]

I have a different approach to set the distance between the distance.

I made the distance relative to the word's length, using this:

(Download .capx)

why you do :

WAIT 0.5*loopindex seconds

and

ScrollingBox |Set text tokenat(Word,count,"")

WAIT 0.5*loopindex seconds:

This sets the distance between the words. If WhosWho removed that condition, the words would spawn immediately, all at once, all on top of each other. The lower 0.5, the bigger the distance.

ScrollingBox | Set text tokenat(Word,count," ")

To understand this, you first need to understand the expression tokenat.

tokenat separates a string into multiple pieces by using a separator. Here, the separator is " ", because words are separated by a space.

WhosWho takes the initial sentence and splits it up into the single words by using tokenat.

He then takes the appropriate word by using "count" as an index to find the correct token.

Clear?

If not, just ask WhosWho again.

Btw: Good job, WhosWho considering that you are new to C2!

Can't open the project since I'm still using r239. Got some issues with the download. (Currently in a location with bad internet, connection breaks with files larger than 30mb)

Could you edit your post and add a screenshot of what you changed?

______________

just disable the joint from the body

Yeah, but that would disable all joints connected to the body, not only the arm..

I guess by "weirdness when stretching the body sprite", you are referring to blurry edges when scaling?

If that's the case, there is a solution to that: replace the body sprite with a tiled background. That's all.