Every HaxeFlixel written game I've come across keeps the device from sleeping, except my own games.

Even though the permissions show "Prevent phone from sleeping" my games still go to sleep.

So what's the secret to keeping the screen on?

Thanks.

EDIT: I should maybe mention this is on Android 5

I figured out the problem.

If you look at the callback functions for the buttons in the OptionsState you'll notice they all use a fade transition to get back to the MenuState.

The callbacks in the MenuState don't so the sounds don't get a chance to play before the state is destroyed in the switch.

If you simply add fade transitions to the callbacks in the MenuState the problem is solved.

Basically, don't destroy the state you're in before the sounds have had a chance to play.

I worked my way through that tutorial as well and I have no button sounds on the MenuState in any target I've built for: Neko, Flash, Android and HTML5.

@DleanJeans Thanks, but I don't think that's it. It happens with an empty project.
I've been googling it and it seems to be a flex sdk issue with no actual solution.

Hi, when I build a flash game through FlashDevelop the stand alone debug player launches as it should but plays my game at 30 fps.

If I then launch the game manually the same debug player runs it at 60fps.

I also tried building the game through Sublime Text and it runs the game through the debug player at 60fps so It's definitely a FlashDevelop issue.

Is there some setting in FlashDevlop which forces the 30fps.

I would like to stick with FlashDevelop but this issue is really annoying.

Thanks Fyfff but it's not really about centering the image but more about maximizing the play area without any of it getting cropped off and also without having black bars.

Technically the letterboxing/pillarboxing is there but it's filled in with the oversized background image.

The Unity plugin that I linked to does exactly that, but unfortunately, it's looking to me like this may be the most complicated part of the HaxeFlixel framework. Over my head at least.

Hi, I gave your code a try and it works just as the images you linked above show, but if you look at your makeGraphic call for the background, you're creating a background that's the same size as the target resolution and then drawing it at 0,0 so there is no centering needed.

If you replace the makeGraphic call with a loadGraphic call and use a bitmap image that's larger than the target res, you'll see that it's not being centered in the way the blog post I linked to above describes. It's still just drawing it at 0,0.

Maybe we have different expectations. I found a blog post for a Unity plugin here that does a much better job of explaining what I was hoping your code would do.

Give it a quick read and see if we're talking about the same thing.

Thanks.

@Twonty2 I gave your code a try but it doesn't seem to work.

Using a phone with a 480x320 resolution I created a background image with dimensions 500x340.

My expectation was that the image would be centered in the screen with all 4 edges being clipped, but instead the top/left edge of the image was drawn at screen coors. 0,0 and only the right and bottom edges were clipped.

Was my expectation wrong?

Looking at the first 2 images you posted my expectation does not appear to be wrong.

Could you post the project files for your test app so I can compare your code to mine?

Thanks.

@Twonty2 I'll give it a try this weekend. I don't have a minute to spare till then.

I think that ultimately the scaling system described in this blog post is what we need to be able to achieve in HaxeFlixel but I don't think it can be done with the currently imposed scaling system.