Skip to main content

PewPew 1.4 and PewPew 2 1.2 submitted to the app store



I finally submitted to the App Store updated versions of PewPew and PewPew 2! Both versions now support the iPad's and the iPhone 4's resolution.

Most changes are in PewPew 2:

  • There's an improved Chapter One: among the things I did was adding visual feedback showing destructible objects were reacting to the players' bullets, so the players would know those objects were destructible . More importantly, I've corrected the bug where the game denied the completion of a level when a player died just after completing the level's objectives, but before the transition back to the menu.
  • There's the long awaited Chapter Two ! It took a really long time to create because it's containing a lot of new enemies, and the levels are more complex than in the first chapter.
  • I now display the best times for the campaign levels.

  • I've added a new infinity mode that you unlock by completing the chapter Two. This mode is very different from the existing ones since you actually control 2 ships. It took a while to adjust the difficulty progression because I am actually not a very good player at this game mode =). It's tough to adjust the gameplay for players that are going to be much better than you.

  • I've slightly improved user interface. I've made the buttons prettier because I've always felt the old buttons (just a rectangle) were boring. Also I've removed the explosions in the backgrounds since they just weren't justified, and in my opinion reduced the purity of the menus.
I've also re-done the website. The client side is done in GWT while the server side is in python. One of the visible change is that the high scores now include the colors of the nicknames :-)


Now that I think about it I was quite productive. I really hope you all like the new stuff. My goal is to make PewPew 2 the best twin joystick game on the App Store, so I am going to keep on working on it.
Labels:

Comments

  1. sebhDecember 1, 2010 at 12:41 AM

    Good work!
    Still now volumetric lines for high-end hardware? ;)

    ReplyDelete

Post a Comment

Popular posts from this blog

PewPew Live's look in a nutshell

Occasionally someone will asked how I obtained the PPL look. In a nutshell: Draw everything with lines, including the text and the various icons. It's a lot of work, but besides looking unique it creates a consistent appearance which is a thing that a lot of indie games struggle with. The lines are screen-space projected lines with miter joins. Draw the lines with additive rendering. This means that if a red and green line overlap, the overlap will be yellow. There are a few things not drawn with additive rendering (like the background of buttons to improve readability), but they are exceptions. Add bloom. There's lots of different bloom implementations. Nowadays I use a bloom that is similarly to the one in  blender's eevee . If you see banding, use dithering. Optional: Add even more post-processing like (very slight) chromatic aberration, lens dirt, scan lines, curved monitor, and vignette. No post-processing, just lines Bloom! Ignore the missing bloom at the top All the...
Post a Comment
Read more

A general state rollback technique for C++

I wanted to write this post for a while. It describes a C++ technique to implement rollback in the context of multiplayer games that I feel is quite interesting and useful. The tl;dr is: don't bother serializing individual objects, just rollback all the memory. Rollback-based multiplayer I've been working on a multiplayer version of PewPew, and for reasons that are outside of the scope of this post, I chose to implement multiplayer with deterministic lockstep and rollback. The basic idea behind rollback-based multiplayer is that the inputs of players are replicated to all the players. Whenever a player receives the inputs of another player, the state of the game is rolled back to the point where the input happened and fast-forwarded back to the present so that the state shown to a player takes into account the inputs of the other players. Because history is being re-computed, some events get undone. For example, it's possible a player saw themselves taking a bonus, but aft...
2 comments
Read more

Ridiculously cheap depth of field effect for lines

I'm working on PewPew's sequel, for which I've revamped the graphics. Instead of drawing lines directly using OpenGL, each individual line segment is made up of two triangles whose vertexes are computed with shaders. Getting lines in 3D space to be properly displayed on a 2D screen is not trivial. In PewPew's sequel I use the screen-space projected lines, a technique very well described in the  Drawing Lines is Hard  post. The upside of drawing the lines yourself is that you are fully in control, which allows you to implement nice things such as joints, perspective, and even simulate depth of field. https://en.wikipedia.org/wiki/Depth_of_field Usually depth of field (DoF) in video games is implemented using a post-processing step that blurs the pixels with an intensity that is a function of the depth of the pixels. When we are rendering lines, we can approximate DoF directly when rendering the lines by having the vertex shader increase the width of lines and r...
1 comment
Read more