I was able to update two existing iOS apps as well as an Android app, all with the beta version. Yes, the attribute thing is annoying, but it did work, so I give GameSalad props for having something

I tried the updated web version , the error console killed it for me i have many places where i constrain and add "+ scene.camera.origin.x " and it gives me an error ,its really slow

I am using build 1.25.81. You indicated that adding a new attribute would make all the attributes show up. That did happen in the general attribute window. However, in my app I have attributes that ar

You need to add (and delete) an attribute for the menus to appear, I think, that's the workaround.

less.This happened after they introduced custom collisions. Newer android devices can handle GS games better. GS has excellent performance with ios/mac games but it needs more love when it comes to a

make a game level attribute:

so when Game.AdTimer = 120, reset to 0 and a Boolean attribute becomes true... and the Change Scene with Interstitial Ad activates.... unfortunately the timer is quite special and does not let GameSal

I first created a ratio attribute.

Game Attribute 'A'

* Add "change attribute" and "change table value"e to the short cut on the top ( whenever you guys got it working) Again, these should be orange to reflect their gr

I'm changing a scene.color attribute. The scenes background color. I have to use a change attribute. And doing that doesn't give me a color wheel option. Only a change scenec. Color. To red or blue o

if i want to change a actors color with a change attribute. All i get is red/blue/green/alpha options.

Most of my bugs relate to an attribute. I try and resolve but sometimes I declare that attribute “corrupt”. Make a new one and just redo that part of the logic.

That's the nature of software development, whether in GS or otherwise. If you are making a larger project, always name your rules and attributes as well as you can, even if that means a longer name. I

It should work just fine ? It's always worked fine for me, maybe you left the control camera behaviour in the actor (so it had both the constrain to camera origin and the control camera behaviour ?) .

(Quote)

(Quote)

You can constrain the camera origin offset (X and Y) to the player without having the use a separate actor.

(Quote)

You could put your camera in a separate actor, and then constrain that to players X with an offset.