(Quote)

Change Attribute: distanceToMouse to (distance to mouse using magnitude) Rule: If (distanceToMouse) > 50 move in direction: (vectorToAngle...) at speed of (distanceToMouse/2)

Encouraged to see how fast you guys are fixing things! Custom collisions are gonna be huge for our upcoming title!

I know I can spawn a "shadow" actor and constrain its position related to the blue actors, but how can I make the shape of the shadow change when my light is shooting from a differen

the COF is set via the Physics->Friction attribute. However, there is a bug that causes the value to be scaled smaller than it should be, so that a COF of 1 matches a Physics->Friction

I'm sorry I'm not as a good a tester as other people, but all of my collisions are tag based and square. Just throwing in a backup on this.

If we publish with this build, we still get the improved performance from this new feature, and the next build will turn it off until it's a switchable attribute in the creator?

I'm not seeing any issues with square collisions in my tests. Anyone have something they can point at to help us see the issue?

I'm probably going to hold off on updating until the bugs have been worked out. The projects I'm currently working on include a lot of square collisions and it seems GS is having some issues at the mo

Just checked out puck it collisions are for sure messed up. Seems to be with square actors.

I don't wanna badmouth stuff like polygonal collisions - it's cool that we get a new feature after years of waiting - but there has been little progress for professional devs or studios for years now.

Some of my behaviors are acting a little wonky. I have an attribute set up so that when game.startgame is true, accelerate to self.maxspeed. I have some controls that change the rotation of the car as

Presumably this is already known, but custom collisions do not function in HTML5.

Awesome! Gonna try it out now, can't wait to use custom collisions.

I found a template by @RThurman that shows how to do a kinetic scroll. I like the way it works but am trying to make some slight changes. The expression is constrain self.linearmotion.y to (max(0, g

Not only that but you will get false positive collisions where you don't expect them if you try to make actors on non-scrollable layers collide with actors on scrollable ones. See this bug: http://bug

Edit: I forgot that you could do this. Make a game integer attribute game.Finished or something, or use an already made one.

Make a self attribute called ON/OFF

The user can display a number(0-100) by input on keyboard. It is a integer attribute that is being displayed.

(Quote)