Is there a way to reduce the wobble on elastic out? I understand it's based on distance, but I'd like my objects to come into the screen and have a slight wobble upon reaching their destination.

At the moment they almost fly right of the screen again. Can I "tighten" that elastic band?

Also, when I have them at their destination, and then I change it, they smoothly travel to their destination with no wobble. However, when I tell them to go back to the previous destination, they're all wobbly again.

Not fully grasping this plugin.

I still don't understand the force and impulse section.

Say I want to have an object spawn randomly on my layout and then launch itself at a random impulse value toward a random location on the layout...

Can anyone tell me what do I use to do that? Rect or Polar?

And what does offset mean? I'd like to make the shift over to this, rather than standard physics, but this one part doesn't seem too user friendly.

newt Thanks, but yeah... I guess I have to keep doing what I'm doing. Due to memory issues, I needed to split my game up into multiple projects. I just wanted to be able to export them as something other than "Index.html"

Not to worry! Thanks for the ideas!

newt That's an interesting idea... so then, the game would look for sub folders. Not sure whether or not that would have a knock on effect to the data.js and the C2runtime.js though... They'd still be pointing at the original, I'd have thought.

Hi all,

Does anyone know of a way to have the game automatically export the game as something other than index.html?

I've had to split my project up into multiple html files due to a memory issue, and I have to go through an annoying process of changing all the file names. I hope there's a way, as it'll save me hours of work.

I don't even remember this... so probs not.

Are you thinking of something that would dump everything in memory between loading layouts?

I was under the impression that everything that would not be needed for the next layout was purged.

I'm thinking of something that is an action, so it can be triggered at the start/end or middle of layouts. As far as I'm aware, it's not purged much, if at all. Local variables have been known to show incorrect figures if the same name is used for 2 different layouts/event sheets. Someone recently mentioned that objects in previous layouts are still "active" in the debug section... though I can't confirm that.

Well it depends on if the "console" is made to allow it.

As far as I am aware, it has functions that permit the action to flush storage and request memory garbage collection, but nothing seems to happen. I can't tell if it's C2 refusing to allow that to happen, or the console just doing a half-hearted attempt.

I'm still saying that the best would be to give the developers memory loading and dumping controls with a warning that it's an advanced feature, don't use it if you don't know what you are doing. The engine does a great job managing the memory, but in rare cases some control is needed.

Yup! Construct 2 does a great job most of the time, but in cases like this, I'd love to have a little extra control. Construct 2's all about loading at the start and having the rest of the game pretty much instant. I'd like to have the ability to load on demand, and remove when not required.

Going to give this a friendly bump, seeing as I've asked for this 3 times now, and been pretty much ignored each time.

I just want to know if it's a simple addition or not and whether it'll make an appearance.

Hi there!

I recently had a strange experience with my latest game that was released on a console.

Although I was testing it regularly, when I finally had everything in, about 30 minutes into testing, the console would fill up with memory, and the game would crash.

I spoke to the console devs about it and they said it wasn't their fault, and I spoke to Ashley, and he said it wasn't C2s fault, however, he did suggest it was possible to create an action that would force a memory dump, but was hesitant because it wasn't a sought after feature.

I'm just wondering how hard it would be to include it. In the end I had to break every single one of my layouts into its own project. This is now a chore to maintain and a nightmare to set up. On top of this, my loading times went from 1 second to about 10 (as it needs to shut down one project and then load the next from scratch).

If it's quite simple, I'd really appreciate this being included. The console devs don't seem interested in improving things on their end, so I need to rely on Scirra.

Any chance of this happening?

Unfortunately I couldn't open your capx as I'm still on the stable... but I managed to get this bullet angle idea working quite well.

270-(angle(0,0,cos(270-Self.Bullet.AngleOfMotion),sin(270-Self.Bullet.AngleOfMotion))/2)

I believe it is based on your code for cos and sine to determine the difference in angle. Then I divide it by 2, and I get the correct angle the player should be.

There are a couple ways to do this.

One is to take the locations of the points of the collision polygon and calculating the point of collision and angle of the surface in contact by using the Separating Axis Theorem. It's a bit more technical to do but it gives exact results:

Another simpler way is to check for collisions around an object and averaging out the offsets to get a angle. Here's one that does that when one object is a ball:

Sadly my collision polygons will effectively be a smoothed shape, comprising of approx 8 points.

I've attached an example of my current method. Hopefully this isn't too taxing for the cpu. The object shoots a bullet that detects the angle of the surface and feeds it into the angle of the main sprite.

However, the problem is now that when the object deflects off at (let's say) a 90 degree angle, the main sprite sets itself to 90 degrees where I'd want it to set itself to 45 degrees.

https://onedrive.live.com/redir?resid=FB21E2766119D2EA!76224&authkey=!AHhzj8Ufzmfbm3c&ithint=file%2ccapx

It's just a quick and dirty way of determining a surface angle... and apparently not a very good one.

Might you know of a way to improve on this method?

Not sure I follow. When I'm on the green level, I pass overthe particles and they start. Then I leave the level and come back to the green one again, and the particles are still going.

Do you mean quit the game and then go back?