Posts Tagged ‘SDL’
This will be my 6th Ludum Dare so far and I’m going back to the basics with the tools.
I’ve been working for a while on a basecode specifically for Ludum Dare, but unfortunately (mainly due to my own lazyness) it is not in the shape I was hoping it to be for this event. It is lacking few major featuers (like audio) and the sprite system has been hacked together in the last few hours so its far from state-of-the-art and likely to be buggy. Anyhow, I’ll give it a go and try to work on it for these few hours there still is before the compo starts and see if I can get the code to even compile on Windows as I haven’t tried that yet even once (in theory it should as I’m not using any Linux specific libraries, but since when has anything been that easy).
Audio: TuxGuitar, SFXR, Audacity
I just submitted my Flappy Jam game (For more information on the Flappy Jam, click me!) and it’s turning out to be pretty interesting! I am actually really proud of this game, as this was one of the first times I have taken more than a few days on a game. The main gameplay is just jumping over some randomly generated spikes. Really. It’s simple, but so was Flappy Bird. That was the point of this jam.
All in all, it was a lot of fun to make, I got to get better in a lot of areas and actually explored a lot of stuff.
It’s not super flashy, but I am actually pleased with the art.
Some things I learned how to do from this jam:
- High scores saved to a file, keeps scores after player closes game.
- Improved randomized spawning systems.
- More reliable and less buggy “scrolling effect”.
I reused the speaker icon asset from my last LD game! Woo! Reuse of assets!
Here is what the death screen looks like, as you can see, it has detected that my amazing score of five was greater than the score in the file (I set it to zero, for the demo.) and tells the player that they beat their score by showing the player a very fancy medal. I designed this system in about two days, without any prior experience with “long term” score capturing options. Pretty darn neat if you ask me.
Anyway, I thought I’d just share that with you guys.
I used the T-Rex C++ engine I made, with OpenGL (SDL_OpenGL) to draw everything, SDL for window and input management, MMSystems for the sound (I’ll get SDL_mixer working, someday.), glut for the text (I’ll get SDL_ttf working, someday.), and SOIL for texture loading!
So, I have been learning C++ for some four to five months now. Last Ludum Dare, I used C++ to make a text adventure game. That was the first ‘official Ludum Dare’ game I made with C++, and I was pretty happy with it. This game had no graphics or sound, and that’s because I didn’t know how to program those at the time. This LD, I made a game with graphics and sound, personally, I think it’s pretty cool I was able to learn these skills in just four months.
Or, as I put it in a post on the second of October; “I am still learning more and more about C++ and OpenGL, so maybe next LD I will have sound and graphics. Who knows.” I am proud that I was able to make something playable in OpenGL and SDL in the span of just 48 hours that also had sounds and graphics. Thank you, everyone.
I will still be doing a post-mortem after the voting ends, I just thought I could share this cool experience with you guys.
This is my third Ludum Dare.
I’ll be using SDL + OpenGL. I also have a small code base I use which can be found here https://www.wuala.com/pigletor/Share/base.zip/?key=laURNwCgnAkU
Anyway, good luck everybody
Something I am coming to learn well is being proud of the work that I do in games. I have quite a catalogue of 15-20 projects I consider ‘playable’, probably five of which I am proud to be called the father of. My latest project, a building block based game, is a game I am very proud of. It is one of the most visually pleasing games I have ever made, and the gameplay is calming. I look forward to the next Ludum Dare.
Thought I should share that with you guys.
Hey guys! Just finished up an amazing Jam where the point is to link a button in your game to a charity of your choosing. You may have heard of it as we have all been talking about it for a few weeks now here on LD. Anyway, my game is called MINIMALISTIC TURBO and I am very proud of how this turned out. This was my first game with a menu, sounds, actual graphics, and I really am just really glad with how it turned out. I think what I enjoy most is the tight controls, gameplay, and how there are very few bugs, no really, I gave this to my testers and they couldn’t find anything that was actually a bug. A few small tweaks, but no game breaking faults. This is pretty big, if you remember my last LD game, a text adventure that was pretty buggy and more often than not break for testers. I am still pretty proud of the text adventure, it was really big for me at the time and still is pretty complex, anyway, that just shows how much I have grown.
Something else I added in this game were sounds I haven’t really had any experience with sound in games, I mean, I had played around with some stuff, but this was my first game that really embraced that and did it well.
I am a little bit unhappy with how my text ended up on the main menu, the taglines at the top are different lengths, and I couldn’t figure out a clean and quick way to center it because I am using outdated OpenGL and GLUT. if I could learn how to do textures soon that would be more than helpful. .-. I tried to get SOIL to work DURING the Jam, and well, that didn’t really work. However; I didn’t try too hard on that. I learned about getting burned out and sticking on a problem a while ago, in a Mini-LD. (Pro-Tip: When stuck on a problem, find a kludge, make a note, move on, come back to it later.)
Anyway, all in all, I am really proud I was able to do this, and I hopefully helped the Red Cross along the way.
Wanna play my game? You can look for it here, or download the game.
Use the hashtag #MINIMALISITC_TURBO to tweet about my game! Or, follow me on the twittertwaters (@powderblock) for live tweeting late night fun.
So we finished our Second Ludum Dare! It feels great
Boy was this one FRUSTRATING
But we learned SO much……
-POST – MORTEM-
First the things that went WRONG
-1. LIMIT THE AMOUNT OF BETA SOFTWARE USED-
Heres the first thing I did wrong. I am running on a OS 10.9 beta. I am writing my code in Xcode 5 beta
Besides all of the crashing, one night I hit a total dead end bug in Xcode where I could not distribute my app. I almost QUIT the dare.
-2. MAKE SURE IF YOUR STREAMING/TIME LAPSING THAT ITS SET UP AND WORKING BEFORE THE JAM-
I spent too long trying to make sure my stream was exactly the right way, plus because of rule 1, it kept crashing, total productivity bust
-3. PREPARE YOUR TOOLS/CODE BASE/LIBRARIES BEFORE THE JAM-
This jam I switched over to SDL for the first time. I hit so many little snags that were simply because SDL works different, a number of times my productivity stopped was because SDL would be handling Floats as Integers, and leaking memory when it renders text, or flat out dropping sound because of an extra curly bracket.
Things that went RIGHT!
-1. Work with friends-
Luckily I had the support from two close friends of mine. Both of which worked with me in the previous jam, but had dedicated time this jam to help. Having three people working on the game felt nearly perfect. The conversations were always motivating and productive. Also having two other people critique your code/sound/music/art is always great. A number of times Id find myself implementing something , and because of lack of sleep/reality/food one of my friends would remind me that what I did looks or sounds RIDICULOUS
-2.Have a Plan-
My friends and I prepared better for this jam. Last jam we did not realize the theme was announced so soon, so we scrambled after work to get together. Not this time, we were together as soon as the theme was announced and spent a good 3 hours whipping up ideas. I have a HUMONGOUS white board that worked so well in capturing and reducing our ideas to the very best ones. We could then get down to work, and glance at the checklist of things we needed to do on the whiteboard.
-3. Share often -
Try to have people test your game as soon as you can, some of the weird little things you know about the games rules or how it plays may not be apparent to others. You have to develop a sense of “communication” to your player , and there is no better way than to see how another player plays your game.
Overall, I feel extremely accomplished having finished a second dare. This time the pieces fell together much better than before. We had the idea down the first night, then got cranking the next two days. My friends and I discovered new talents and developed some since the previous jam. We look forward to finding out when the next jam is, and now I can’t wait to try some of your games!
—Don’t forget to try our game FSCK! Bit needs your help!—-
Hey, I am getting all of my tools in order and working on a few different little projects to get setup for LD and I have ran into a problem, I have never good with sound. Like at all.
I don’t even know how to get sound playing and I am scared if I ever did, it would be unstable enough to make the game unplayable for some people. This brings me to a another topic, what is the best language (in your opinion, to you) for making sound?
I had minor success in Unity with sound, but in ‘dem hardcore languages I have never been able to get it working. (I tried Python, C++ w/ SDL, etc.)
Any help on the matter is appreciated.
About time I got around to writing a post mortem for my entry, here goes!
Curiosity is a little ambient exploration game written in the ooc programming language. You can play the game here if you’re interested.
In the UK, Ludum Dare starts and ends at 3AM. I decided to stay up into the early hours of Saturday, and fell asleep with minimalism floating around in my head. I think I had a dream about a game idea, but unfortunately I couldn’t remember it.
I thought about a game that starts of super minimalistic, and gets progressively more detailed and lush as the player progresses. Of course, this was silly and vague. In such a short space of time just having a finished project is a challenge, but I hope the game resembles my intentions a little.
I admit I didn’t really like the theme at first – any game made in 48 hours is going to be minimal, so minimalism seemed to be a wildcard. I changed my mind once I got started.
My graphics software hasn’t changed since the last time I entered. Even though I’m 5 major versions behind now, and running it 2 operating systems ahead of what it was developed for, Fireworks is still my general purpose graphics editor of choice. Having .png as the native project format is really handy, along with the variety of non-destructive image processing options.
I’d heard good things about Ogmo Editor, and watched a tutorial on using it in FlashPunk. Considering this was my first time using it in a project, it worked amazingly! When designing the world, I tried to make sure there was more than one way to solve each challenge (though not everyone who played the game noticed this). Some people said the game reminds them of the Knytt series, which is very cool to hear! Nifflas was certainly a source of inspiration for me.
A few people found the game too difficult, but I don’t think there were any major flaws in my level design this time. My old entry for LD21 had lots of blind jumps, no checkpoints, and you could fall off the world by going left. I’ve definitely improved in that respect! Personally I thought the difficulty level was fine, especially after playing some other awesome yet insanely hard entries.
My choice of language, ooc, served me incredibly well! It’s a modern object-oriented language that compiles into C99, and therefore works on any platform with pthreads and a C compiler. I picked it up in the last few months, created quite a lot of bindings to existing C libraries, and have been working on a FlashPunk inspired game engine called Vamos using SDL 2.0’s hardware accelerated rendering API, which I used to create this entry.
The majority of development issues were all tackled before the compo started, so I had a pretty smooth ride on my own framework. The day before, I bound a small XML library (MiniXML) to ooc, so I was able to parse Ogmo Editor’s level data. On the first day I remembered I still hadn’t implemented depth-sorted rendering, and that ate up a little bit of time, but was quite painless.
The main problem was that my game engine didn’t have sound effects. I’d been trying to write my own audio mixer before the compo (without relying on SDL_mixer), but it had huge latency and I couldn’t figure out how to avoid sounds being synchronized to the buffer size. The music playback (which uses stb-vorbis for decoding) was working fine, and I found a hacky solution last-minute to create smooth crossfades between tracks. That hopefully compensated for the lack of sfx.
This has always been a strong point for me. I wanted to include just as much musical content as last time, which meant I had to make 4 tracks! In my last entry, my soundtrack was ruined for some people by streaming/stuttering issues. That wasn’t a problem this time, because I was making a desktop game.
I’m primarily a Renoise user now (though SunVox is still awesome, and I highly recommend it if you’re looking for a free music program). I’ve got a nice collection of free VSTs and samples and had fun creating some ambient songs and soundscapes. It gave me a nice break from the intense coding!
I’m really happy with how this turned out! I’ve since made some Linux binaries, and it also runs nicely on OSX (though I don’t have a mac to test or package it). I’d love to develop Vamos further and make some more ooc games in the future.
I’d also like to thank everyone for their encouraging feedback so far. Thanks guys, and well done on all your finished projects!
It’s been a full year since my last LD… ::sigh:: But it’s great to do it once again!
This time I made Runaway Money, a party game about being invisible and stealing money. Sounds kinda fun, right? Does it also sound kinda strange that a multiplayer game would use invisible players? Yeah, me too. I had to think a while to make sure it was possible.
As it turns out, it is and it’s pretty fun. Give it a try with your friends!
Ludum Dare END
SUBMISSION: Cave Runner
And so ends my first Ludum Dare. It was a challenging experience, especially since I didn’t have as much time to work on it than I had originally hoped. My plans changed a lot throughout the competition. I’d like to highlight the biggest changes.
- My original plan was to submit my game into the 48 hour competition, but I ended up needing more time, so I submitted it to the 72 Jam instead. I hope to make an entry to the 48 hour competition next time.
- I did not add sound. This had to be cut in order to meet the 72 hour deadline.
- I code generated shapes rather then art. I made this decision after the theme was announced, since to me it showed minimalism.
- I chose to make an infinite runner game instead of a roguelike. I ended up making this change almost as soon as the theme was announced, since I felt I could achieve this, and my top objective was to get something I could submit.
- I ended up using OpenGL as well as SDL, since I knew it would fit well with my level generation. I did not know how to do this in SDL, and with a little research I realized it would require one of the extra SDL libraries. This could have been a bad decision, since I didn’t have any experience making a game with OpenGL, but I believe I learned a lot because of this decision.
This wraps up my thoughts so far. I might make another post after I get the results back. I’m hoping to get at least 2’s or 3’s, and maybe get some insight from comments.
This is going to be my first Ludum Dare. I’m pretty nervous.
Here are my choice for tools, libraries, etc. so far:
- Language: C++
- IDE: Visual Studio Express 2012
- Libraries: SDL
- Art: GIMP
- Platform: Windows
My goal for this competition is just to complete a game, and keep it simple. I want to work on scope control and focus. It will be a plus if I get any decent scores. I’m going to be spending most of my time until the start time making sure I can quickly bash out the basic code for setting up the windows, rendering, update, etc.
Here’s my game plan from the start time so far:
- Friday Night – Saturday Night
- Get basic program up and running [window, rendering, update, fps control, input].
- Create a basic game state control [nothing too complicated].
- Get something moving based of of input.
- Plan the game elements I want to implement.
- Break the game elements into there gameplay atoms, and check the scope of the game.
- Start implementing the high priority gameplay atoms, such as movement, attacking, GUI, etc.
- Get the core gameplay implemented.
- Start polishing the game, and looking for bugs.
- Add more/extend features if QA is finished early enough.
- Finish quality control at least 2-3 hours before the end time.
My current idea is to create a dungeon crawler style game, assuming it works with the theme. My priorities for the game are as follows:
- Core Gameplay
- Basic Art
- Extended Gamplay
- Polished Art
I will be hosting my game on my website here:
Not sure if it’s going to be something.
I did not prepare at all compared to the previous contests.
I’ll copy one of the following repositories as basecode:
Obviously I will throw away the existing games and only use the technology utils part of the code.
If I feel like it I might use SFML and C++ without any basecode except from my eternally unstable monster of a serialization library.
Set sail for fail!
Hello, this is my first Ludum Dare; I’m hoping to hack a little game in C with SDL. I’m going to either procedurally generate graphics or make some quick pixel arts in gimp.
Good luck to everyone
Oh, I cannot tag my post with ‘C’, each time I try the tag is magically transformed into ‘C++’ (actually I wonder if anybody else is going to use plain C :P)