If I understand your description correctly then 100 X / 150 Y would describe a pixel located 25 pixels (centred) above the top edge of the square.

Plan B is to reduce the number of action buttons to two, keeping directional input at two as well, and having a button at the top right corner of the screen{where the power indicator resides at presen

Oh, you mean the slideshow on the top. I'll try and see what I can do.

Yes but rarely both? I guess the front (top) page where you can scroll left and right kind of throws me off.

(Quote)

GameSalad is pleased to present to our community the "official" GameSalad templates designed and developed by GameSalad's own expert, in-house game development team. Emulating the g

I've tried doing this from ipad template (1024x768) -landscape, and tested on iphone 5.. Not quite as cut n dry… it does a fairly good job at maintaining everything in screen.. but noticed the top and

When you are in Preview mode, when you want to get a screenshot, click on the camera icon top right. Then you'll be given options: save the screenshot, set the shot as the project screenshot, and/or s

edit- I see that it scrolls vertical if you hit the top buttons...

Curious as I have an iPAD project/template.. and surprisingly - I can test it on iphone5 relatively well but the top and bottom 100 or so pixels are cropped out - I was surprised it got even as much a

Put the pause button on its own layer and make sure you uncheck "scrollable" for that layer. That will keep the pause button in the same location on the screen.

That's my issue...I have tested.....it's not working crop top or crop side....lose controls or scores actors....something is always screwed up....my question was.....can I publish ONLY for iPhone 5 or

been open for over 6 hours. I haven't tried the destroy all actors approach yet, I'm hoping that version 0.11 fixes the problem, till then I may not need to worry about it since the game plays fine.

** My Actors testing are on Top Right if it matters **

I'm not sure why you jumped to "in the history of gamesalad" but as I said, this is my common practice:I either build a single scene or use multiple scenes. While I haven't destroyed

I've always thought that would be really useful, being able to destroy an actor from 'outside' of that actor.

That's up to you. Depending on the type of game, I either build a single scene or use multiple scenes. While I haven't destroyed actors as suggested, I may do this next time around.(Quote)

I read in a thread on here, that if you have many scenes for levels, the further you progress, the higher the ram usage. Some proposed that you destroy all actors from previous scenes before moving on

Does this mean if I have a 12,000 pixel length level, that anything beyond 500 from you will disappear? It hasn't happened in the first level, but whenever I got to the second level, a lot of things t

Top Secret render of a prototype (Image)