OlivierC I'm wondering how you went about the lighting? It's one of the few things left I haven't gotten into yet and I would like to see how it's done :)

But yeah I agree the bulk of it is all pretty basic. I think the trickest part is how to handle text trees and cycles, because what looks good to start with can lead to hell if you get it wrong in just a tiny point. You really need to make sure it's super simple to implement and reliable.

Hey,

I have been trying to get the wgt made on the IDE and am following the tutorial. But I get this message when I try to run it by pressing the blue arrow button:

Initializing the environment for launching the package failed.

error occurred at the below step.

`step context handle`

(Return Code:1005)web ide context - can't find 'target device'

Cannot connect to a target

Please start Emulator in Connection Explorer or check connected real device on your PC

Any idea what's up sosensible ?

Yeah of course, as indicated by 'I use...' ;) You use trigger once, on collision or something like that. That depends on all your other conditions and what you want to do with it. For the second problem I have no idea sorry! I find it pretty annoying myself.

If you use set size to go back to the original then yeah you could just set size to image height/width, but scale is slightly easier. And scale would be slightly easier than my method if it worked that way. I'm not saying scale is incredibly useful, but it does have a use and my method of scaling is super easy anyway.

I use set size to width: self.width*1.1, height: self.height*1.1 for stuff like that. Never had a problem with it so far. And in this case setting scale to a constant size is useful if you want to reset something to its original size after it has been through a number of alterations I guess.

Another issue with LOS is that it seems to only check for line of site to the object's origin. Is this the case or have I just done some silly stuff? It would be great if it could check for LOS with any part of the object. Otherwise you are still probably better off eventing it.

szymek

"...and gives us the ability to have better local file management in addition to cloud." Here's hoping that's the fix I've been waiting for! The black screen issue was a problem in how they managed the memory of certain images.

But yeah it looks all different now, I can't wait to give it a go and see how it fares.

szymek - They sent me an email when they took over and I tried it then. Is 'new' newer than that? Do you have a link to some info? I would really like for it to work, because other than that one fatal flaw it was a dream to use.

szymek - That's the old appMobi right? They seem great, except for the black screen your game will inevitably get. They told me they would soon fix the problem over a year ago I think it was now, and trying it just last month the issue is still there.

szymek - From what I can tell it's a silly idea to pin all your efforts on developing for Ouya, but that the main reason so many games fail to make any money is, well, they are phone games. I don't see why anyone is paying for a console then paying for a game when they could just have it everywhere on their phone instead. This may not be the case as I don't really have an good knowledge of the Ouya library, but from all the game you just listed - and every other game I've heard of on it - this is the case.

So I reckon the only people who could make decent cash from it are people building for other targets (that involve more than a touch screen) and then porting that over. Maybe a really good fighter or something.

ArcadEd - this is great news! But any idea of how to monetise from it? I had used Clay.io in the past for IAP, but just wondering is there's a cleaner way.

arontwose - Yeah that's a good idea! Thanks. Also though, adding layers to all layouts can be a pain, so I usually always have at least 2 spare layers. It'd be nice to have an 'add layer to all layouts' option.

Generally for anything that is across all layouts, like a HUD, you event their positions in instead of manually placing them.

For example: at start of layout: create healthbar on layer "hud", viewportleft("hud"), viewporttop("hud")+25. Then just make sure that is in an event sheet common to all layouts and you're golden.

One thing that can get really bad though is needing to alter a layer's name!