Construct 0.99.7 (unstable) released

Yeah the collision bug is fixed in the next version i believe.

Excellent work as always

Fixed? That actually sounds like a neat idea, but why not leave it strictly optional?

Sounds neat, but doesn't work how you might think. It prevents you going up a slope at all really. Though what you're thinking it does, could be done with events I would think.

python is totally broken now

I just released a fix for the old python problem

but now even a simple python command like

sprite.angle = 0

crashes the runtime

I will file a bug report too but thought I should mention it here too.

I found a new runtime bug with the physics custom collision.

CAP can be dowloaded here: http://dl.dropbox.com/u/1727838/collision%20bug%202.cap

Screenshot showing what happens:

Something is wrong for sure, but I fixed it pretty easily. I just deleted all the points and re-drew them and it worked fine.

Still, it shouldn't mess up in the first place so, yeah... bug.

Something is wrong for sure, but I fixed it pretty easily. I just deleted all the points and re-drew them and it worked fine.

Still, it shouldn't mess up in the first place so, yeah... bug.

I think at a certain number of points it will break. The game I'm working on has some large objects that need a bunch of points, so right now I have to break them up.

I think at a certain number of points it will break. The game I'm working on has some large objects that need a bunch of points, so right now I have to break them up.

Could be. I made a mini-golf prototype a few builds ago that used one large custom collision mask for the whole level. I should load it up in 0.99.7 and see how it handles it.

Edit:

Seems fine. There's a whole crapload of points on the object and it appears to be working normally:

http://dl.dropbox.com/u/529356/pingolf_v0.2.cap

The Box object named "collisionmask" is the one with the custom mask on it. Click and drag the ball to shoot it. If it becomes unresponsive (a bug in my events that I never bothered to fix) then hit R on the keyboard to reload.

Anyway, it could be that your mask was bugged for another reason...? Maybe when you hit Close it just didn't save the mask properly or something. Anyway, I'm sure the devs can figure it out.