So today i sat down, and figured out what packages we are going to be using in the challenge. This is what i have come up with so far, and the reasoning's behind the choice.

pySDL2: There are many options out there for handling windows, input, and opengl contexts etc. pygame, pysfml2, pysdl2, pyglet and PyOpenGL glut are just a few. To me the advantages of pySDL2 are that it has the full unrestricted power of SDL2 so multiple windows, OpenGL context creation control. Its being actively developed, and should work on all python implementations on most operating systems since it uses ctypes.

PyOpenGL: I don't really like pyopengl but right now its really the only complete option out there. I have my own but i don't want to use it in this case.

cx_freeze

Some other information, we are going to be trying to implement the game with modern opengl (probably opengl 3.3). So this should be interesting to see how this goes. We have only really used opengl for 3d stuff, so we are going to be expirementing with some stuff until saturday to work out how we are going to do everything.

We are currently planning on doing a 2d platformer with a few twists. I hope our first time goes well!

So after a quite a lot pain and misery. We have created.... a triangle:



At the last minute we said screw it, roll our own opengl binding. We had ran into some a show stopper bug with opengl on Saturday when doing some pre-contest tests.That bug i seemed to have replicated in our binding, now fixed of course.

So from here we need to finish up the shader class, write a matrix math library, and then start on texturing. Hopefully we can be done with that by the end of today.

Thanks, Matthew

P.S. Our github repo is located here: Cubix Github

So today i finished quite a lot considering what i'm doing.

OpenGL Binding Process - Figured out and working
Basic Math Library - Implemented might still have a bug
Shaders System - Implemented and Working


Running properly on the following systems:
Python 2.7 all platforms
Python 3.4 all platforms
Windows
Mac OS X
Linux


We have a bug which seems to be originating from the math library. The orthographic projection matrix may be incorrect, nothing is shown on screen.


Once we get around that issue we plan on moving on to these items:
Texturing
Text rendering
Logging
Configuration System
Game play systems


See everyone tomorrow!

I have made a decent amount of progress today.

The math library is almost fully functional now, just a few bugs in the rotation functions.

I am very very close on having textures working, probably just a small opengl binding issue.

If we can stay on track tomorrow, we hope to start actually turning what up until now has basically been engine work into an actual game.

Here is a quick image just to show things can move!

Thanks, Matthew

So after a lot of beer and headbutting the keyboard we have a physics engine coded completely from scratch, it has aabb, circle collision models and along side it has a quad tree implementation for optimization reasons. Basically right now when two objects collide it outputs the penetration distance and direction, right now all is left to do really is add velocity and objects will be able to repel each other in a very basic way.



So the object highlighted in red is the "player" and when it collides with the objects near it, it spits out the info in that box. The blue lines represent how the quad tree looks for this particular scene. So now that this is done, this leaves us 1 day to make a game, haha... Thanks, Alex

Well here we are 5 minutes before the deadline, and what do we have to show? Well we have a 2d OpenGL game engine...

We really do want to finish thing so we will be working on it until its finished hopefully.
We also have plans to take the engine side polish it up a bit and maybe release it as a library. However that would first require us to have a full OpenGL binding...

And some updates on what i have been doing: I've got text working for the most part, there are just character scaling and some simple performance issues to sort out.


Thanks for the great time, we hope to do better next time!