2 2D-Game Ideas

[Sauer2]

BTW: I tried another way, because Vsync didn't work for me. See: http://lists.libsdl.org/pipermail/sdl-l ... 09681.html

[qubodup]

@sauer2 It's impossible to tell. Perhaps this video, which should have no recording lag, will help you compare: http://www.youtube.com/watch?v=BsbB5lc-r-E

[Sauer2]

This seems to work, since this approach aims at fixing the fps count.
BTW: What is that on the beginning and the ending? Looks like you were running the game on a cell phone or stuff...

[qubodup]

uh.. no idea. I didn't even bother to check the video after uploading.

weird encoding problems..

[Sauer2]

Well, they could get obsolete, due to this patent crap.

Anyway, I made 3 blocks "falling" up. What do you think, is the speed acceptable?

[qubodup]

Anyway, I made 3 blocks "falling" up. What do you think, is the speed acceptable?

It does seem good. Although the first few times the player might miss them (they are not slow . It depends on the severity of missing them and how hard the game is supposed to be.

[Sauer2]

Actually they're meant to be missed. I mean, collecting rocks?

[Sauer2]

Things like player movement (mouse based) collision detection and the life bar are working.
EDIT: Fixed a bug in collision detection. Primitive, but it works..

[Sauer2]

The final prototype is done. I don't think, I'll put more efforts into it, because I'm lacking time and motivation. Forks are welcome, though.

http://github.com/Sauer2/falling

[qubodup]

what happen? why is it gone?

[if my statement makes no sense, github might have had some problems]

[Sauer2]

I removed the repository and the account, because I don't have time now for another project. But that shouldn't be a problem, since you have a copy of that repository.

EDIT: Damnit, it's an old version, still with that memory leak in the image loading procedure. Well, apart from that, the new code, especially the miserable hardcoded sample level and the collision detection was crap anyway.

[qubodup]

*shakes head*
that's not how you do open source.

[Sauer2]

Well, that's true.
On the other way, there is nothing you could learn or use or fork from the code (and I don't want to spoil someone ):
1. No proper build system
2. Messy and comments missing
3. Everything specific (image sizes, etc) hardcoded, proper animationsystem missing
4. On second thought, it isn't usable on webOS, too, since they are using a mixture between SDL 1.2 and 1.3, waiting for 1.3
5. Name convention is only half available
6. I guess, someone experienced could that done that in 3 days, thus better rewrite it
7. Movement and timing
8. Art is still available at opengameart.org, even the cooler remix

[MCMic]

Your links on OGA are broken since you removed the project :-/

[qubodup]

code: http://github.com/qubodup/falling (don't know how much was lost)
sprites: http://opengameart.org/content/falling-game-sprites

[Sauer2]

@McMic: Yeah, sorry for that, all in all not the best idea I ever had.