good scam

Discussion and feedback on Construct 2

Post » Fri Apr 26, 2013 6:13 pm

Here I leave one level of my game ... 30 fps and iphone is unplayable, in firefox is perfect.
https://www.dropbox.com/s/4ujb4nb3ebztlcm/as.capx
B
11
S
4
G
1
Posts: 410
Reputation: 2,752

Post » Fri Apr 26, 2013 6:32 pm

It runs at about 30 FPS on Chrome for Android and 55 FPS+ on an iPad 2 (I turned on letterbox scale to make it fit the mobile screens). That's a good result for a mobile game (30 FPS should be your target). Tip: you have an opaque background, so set the 'Clear background' project property to 'No' to make things slightly more efficient.
Scirra Founder
B
359
S
214
G
72
Posts: 22,952
Reputation: 178,600

Post » Fri Apr 26, 2013 7:17 pm

[QUOTE=Ashley] It runs at about 30 FPS on Chrome for Android and 55 FPS+ on an iPad 2 (I turned on letterbox scale to make it fit the mobile screens). That's a good result for a mobile game (30 FPS should be your target). Tip: you have an opaque background, so set the 'Clear background' project property to 'No' to make things slightly more efficient.[/QUOTE]
Not give me any solution, changing the background will not go better :(
B
11
S
4
G
1
Posts: 410
Reputation: 2,752

Post » Fri Apr 26, 2013 7:49 pm

Runs at 28-30 frames on my Nexus 7 and Chrome.
Even runs at 32-35 frames on my Sony Arc S with default browser.
B
6
S
1
Posts: 16
Reputation: 464

Post » Sat Apr 27, 2013 1:13 am

some notes
I'm also a begginer, but saw some stuff that you could improve while glancing at it:

On design:
1.- for the red character: Use a container for the eyes
2.- for the red character: For the jump use image points or use EaseTween.
3.- For the whole project: use Powers of two in the sprites.
4.- Use PNG8 for the background
5.- Sprite 11 is a waste of blank space, clone the empty star three times, use a simple 2x2px black tile with 30% opacity as background.

On code:
6.- Use delta time, you have lots of actions using time. That will help on frameratesss.
7.- Also, use Groups, your code needs it, a lot.
8.- And Functions, they can pass variables and data.
9.- And Families, you are using lots of single events for destroying any block. Example on how to fix this: Assign instance variable ID "destroyOnClick" to anything that you want to be destroyed on click, and create a Group for that.
10.- Why use WebGL if iOS doesn't support it?
11.- The code is ALL the time checking and updating the End Screen (just remove the forest background to see what I mean).
12.- Hide the End Screen btw., and only show it or create it when the red thing is over the Goal block.

Your code can be improved, don't give up.California2013-04-27 01:23:01
B
18
S
5
G
4
Posts: 568
Reputation: 5,079

Post » Sat Apr 27, 2013 1:33 am


You've also got pixel rounding off, and have lots of sprites (including background images) with collisions enabled that don't need it.

As well, your animations play too often. Personally, I would make them wait a while (ideally randomized) after blinking before triggering the animation again.

Probably minor things but everything helps.
B
8
S
2
Posts: 63
Reputation: 1,223

Post » Sat Apr 27, 2013 2:34 am

^ Yep, forgot to mention those two, thanks Dormi

Also, Distribute things in layouts, don't use only one layout.
B
18
S
5
G
4
Posts: 568
Reputation: 5,079

Post » Sat Apr 27, 2013 11:04 am

Thanks @California, but half of the things you say I do not understand how. I'm tired of this game, I think I'm going to discard.
B
11
S
4
G
1
Posts: 410
Reputation: 2,752

Post » Sat Apr 27, 2013 11:14 am

Start small, make a short and simple prototype. With experience you get better.

Nobody made a big game from get go.
B
62
S
21
G
12
Posts: 1,910
Reputation: 13,155

Post » Sat Apr 27, 2013 11:22 am

Making games is hard. It's a lot less hard with Construct 2, but you still have to put in the work if you want a good game.

A lot of California's suggestions are actually things that the "best practices", "performance tips" and "mobile performance tips" tutorials recommended -- the tutorials you said you'd already followed earlier in the topic.


No offence intended, but surely now you can see that it wouldn't be fair for Scirra to have to refund your money; your problem aren't because the software isn't capable but because you're too lazy to actually do the work necessary to optimise your game.


If you want to fix your game we're here to help, but you will have to do the work. Ask us about any of the specific suggestions you don't understand and we can help you with more detailed information.

Do you want to fix your game, or do you just want to give up?
B
24
S
5
G
2
Posts: 104
Reputation: 3,136

PreviousNext

Return to Construct 2 General

Who is online

Users browsing this forum: BBaller1337 and 16 guests