So, I've been working on a Breakout game based on this.

Here is a screenshot of a decent-working version:


And here is a screenshot of one that freezes on a white screen when exiting and then resets the calc:


I would like some help as to why it is freezing. Also, it sometimes replaces the first few colors of the side bars with bright red, if that info helps any.

You can find my source here.

Also, if you notice, the flashing tiles are supposed to explode all the ones surrounding it, and if it explodes another flashing one, it's supposed to continue until it runs out of flashing tiles. Every time I try to implement this, though, it just freezes the calc and I'm forced to exit CEmu altogether. Any advice on this would be nice as well.

All help is appreciated!

Edit:
Here's a gif with the red lines and resetting at the end:


I'm pretty sure my errors have to do with my function to "explode" the surrounding tiles. I'm just not sure why.

The first main problem I see is in this function:


Code:


There's no bounds checking. Thus you will be writing random data to who knows where.

That's probably what is causing all the issues, so if you fix that, it should be fine. Good luck, this is looking really cool Also, it might be better to have the sides colors be a global or declared as static, as it has to allocate room for it on the stack which is kind of wasteful

Looks pretty good! It's really smooth.

Thanks! I got it fixed now (also updated the code on github):




Thanks!

I tried getting the chain reaction thing working, but I couldn't do it. It either just wouldn't happen, or it would freeze the calc (no debug menu, though). I tried nesting the function inside istelf, which I don't even know if that's allowed. If anyone could help with that, it would be cool.

Edit: Also, if you guys have any suggestions for better ball/tile collision (with detecting each side and changing velocity accordingly), I'm all ears.

Oh, DX-Ball!! This is a very nice game, and in the past I played it too much
I remember me that I once made this in Processing, but without colors.
Anyway, ball/tile collision was the hardest part for me, and that is why I don't succeeded it. An idea for the chain reaction is this in pseudocode. Use a very simple stack:

Code:

I hope this works and good luck on finishing this!

Thanks! But I'm not quite sure how I could implement this in my code. Could you explain how it works for me? What is "explodes.push(neighbor.position)" and what is the purpose of the "explodes[]"?

Ok, I will try it in more pseudocode

Code:

Hope this is better

Okay, I'm still having trouble, though I do understand it now.

Here's my function in C so far:

Code:


The problem is that with what you're suggesting, it would involve adding values to the array and making the array bigger, which, in c, is a pain in the butt. If anyone who's good with C could point me in the right direction with this function, it would be greatly appreciated.

*bump*

Could someone help me figure out how to make this recursive:


Code:


Everything I try seems to freeze the calc. :/

That section of code works, though? How deeply are you recursing? Is it possible you were overflowing the stack?

Yeah, probably.
Well, this is how I'm implementing the chain reaction:

Code:


Or something like that. I don't expect that implementation to work super correctly, but I still cannot get it to keep from freezing the calc.

I wonder if you could have an array somewhere with a list of tiles to explode, each frame you'd run through the array once adding the next set of tiles to explode. This way they wouldn't all explode at once and it'd have a chain reaction sort of feeling to it. It'd also be a bit lighter on the stack. Also, should setting the tile to zero be included in the innermost if statement? It should probably also be done before the call to TileExplode, otherwise the tile isn't reset until you've finished running through the entire board, and it's probably getting stuck in a loop as it checks one tile then the next then the original tile and the next tile, since they're never set to 0.

Seems like this did the trick! Big thanks to you!

I guess there are some issues with my implementation, but it's a start:


For some reason, it's also deleting some other tiles than the ones that it's supposed to.

Here is my implementation:

Code:


Also, there's a dramatic speed increase when a lot of the tiles have been destroyed. Any advice on how to regulate that speed?

Edit: Changed to better gif with less frame skipping.

Can you send me the download so I can try the game?

It's not really playable yet. Sorry.

Now that I've got the SDK working again, I've looked at this again. I'm still looking for some help with collision detection (as in, which side of the block is the ball hitting?) if anyone has any input. Also, could anyone help me in regulating frame-rate? There's the animation that needs it and also when there are less blocks on the board, it starts getting faster. I appreciate any input.

*bump*

In my quest to revive some of my old projects, I thought I could breathe some life into this one. This time, I'm using tilemaps for each level, and so far the performance is much better. I haven't implemented the animated blocks or the "explosions" yet because I'm trying to get the collision detection to work properly first. Right now, this is the behavior I am getting:



I've tried so many different ways of detecting collision, but I can't seem to get it to function as it should. Here is my current code:


Code:


I've tried rearranging things, turning the 'else if's into just 'if's (which gave me other misbehavior), and adding other conditions to the if statements. Nothing I've tried gives me the right behavior, and now my brain is fried from all these attempts. If anyone could offer some help/advice, I would really appreciate it! While I cannot figure this out myself, I will be working on my other revived projects in my free time.