I'm working on a flight game in javascript. So far, I have terrain, sky, a Nighthawk F-117 (maybe I should have a shoe instead…) and some wonky plane physics.

I'm not sure where the design should go. The hawk was made mostly as a placeholder, because it takes like 10 polys to model it. With that and the sky and the infinite terrain there (both making use of usual perlin noise), the game looks like it would play like Ace Combat. When I started working, I was thinking something more star-foxxy, more space exotica. Not sure where to take it next.

The game uses a software renderer that I wrote earlier this month to participate in JS13K with. It was going to be an awesome FPS and dreams and stuff, but ofc. I didn't have a game made in time for the 13th. :( JS13K is a compo where the challenge is to use max 13k of JS and data in a zipped folder.

The renderer itself uses HTML5 for the canvas and the function putImageData(array_of_pixels). The rest is my code manipulating the pixel array. Beware, JS rasterization of triangles is not very fast (ofc, my code could surely be a lot more efficient). :P The original idea was that I would save bytes using a tiny software renderer instead of WebGL, but now with no space restrictions, I'm using it for no good reason.

I could go on about the graphics engine, but instead I'm going to cut here. I'll just say that, technically, the graphics are closer to N64 than PS1. Please ask if you wonder anything!