Firework 2011 - New Years Game!

[CZ Games]

I was making this game with help of my partner, dino0040 and was planning to finish it before New Years Eve but I came across an error. I am using temp. sprites. I do NOT want any graphics for this game. If you want to help just PM me and I'll see.

So you are a firework and you move left and right while you are soaring into the air. You must collect orbs which they give you points, I know, very original. You must avoid birds, and if you see another firework you must tap it, which will burn it out so you stay in the limelight!

At this time I do not want suggestions because i have a lot planned, but i put a halt in development when I got the error. If you have a suggestion go ahead and leave it but keep in mind i might have already planned that.

The error is a vram flood. Too many sprites or something, it seems to occur when you have 90 points. The objects ARE being deleted. I am mostly sure because i have the if object in location action set to a certain line on the Y axis and X as the objects current location. "[X]". then start block, delete obj, end block.

Firework 2011.nds

Demo 1

(365.56 KiB) Downloaded 114 times

[James]

i have the if object in location action set to a certain line on the Y axis and X as the objects current location. "[X]". then start block, delete obj, end block.

Use 'If Variable' to just check '[Y]'; that's more efficient. Don't check a specific value of Y - if an object moves at 2 pixels per frame (e.g. [VY] of 2), and starts at an odd number, it will never reach 192 - it will go 191, 193 ...

Better to check if the [Y] is greater than 192 rather than equal to it (or apply this to your situation).

If you die, you don't always return to the menu. I die when the bird appears, I have to suddenly use the stylus to kill the other rocket. I would let the player move the rocket with the stylus too (set [X] to Stylus.X - 32), D-Pad controls and Stylus don't work well together at all.

Remove the anti-aliased pink from around the sprites; it's very visible.

You can use anti-aliasing on sprites but make the background black, because your background doesn't change.

[mangopearandapples]

Killing the birds is so fun.

[CZ Games]

Remove the anti-aliased pink from around the sprites; it's very visible.

You can use anti-aliasing on sprites but make the background black, because your background doesn't change.

I am using temp. sprites.

[CZ Games]

Use 'If Variable' to just check '[Y]'; that's more efficient. Don't check a specific value of Y - if an object moves at 2 pixels per frame (e.g. [VY] of 2), and starts at an odd number, it will never reach 192 - it will go 191, 193 ...

Better to check if the [Y] is greater than 192 rather than equal to it (or apply this to your situation).

I did this really thinking it would work but it didn't. Could i PM you the .dsgm?

[James]

It's really as simple as this:

If that doesn't solve it, the problem must be elsewhere.

[CZ Games]

It's really as simple as this:

Help.png

If that doesn't solve it, the problem must be elsewhere.

actually i used greater than or equal to but wouldn't that still be fine? I guess the problem must be elsewhere, but where?

[James]

actually i used greater than or equal to but wouldn't that still be fine?

Yes; it's absolutely fine. The problem is naturally going to be where you're creating and deleting objects - if the game starts OK then something is happening to put too much in the VRAM.

I suppose what you can try is cutting down on the actual object creation. It may not be that objects are not being deleted; it may be that there is too much data in the first place. However, this does not account for the error happening at around the same time every time - that certainly indicates that progressively, objects are not being disposed of and memory keeps filling up.

You can PM me the .DSGM if you wish and I will do some debugging. I can, for example, print out the instance numbers on the top screen to see if things are actually being destroyed. I will show you how to do that.