mjh_PROJECT NOTES / 03 All projects

03 / CASE STUDY Singularity-Wars

Singularity-
Wars

A little physics. A lot of space. A Python and OpenGL space-combat project that connects movement, hazards, enemies, and rendering in one game loop.

CONTEXT

CSE423 coursework · Collaborative project

MY ROLE

Concept & game enhancements

BUILT WITH
PythonPyOpenGLGLUTGame physics
Singularity-WarsPROJECT VIEW
Singularity-Wars 3D space combat gameplay
The game combines spaceship flight, combat, and environmental hazards.
Movement through space
6-DOF
Difficulty settings
3
Camera perspectives
2

01 / THE PROBLEM

Make interacting systems feel like a game.

Movement, collisions, enemies, and gravity must respond together. A small change in one system can change the whole flight and combat experience.

02 / THE APPROACH

A loop that keeps the world moving.

GLUT callbacks handle input, updates, and drawing. Python updates the simulation; OpenGL renders it. Player actions and environmental forces feed the next update.

A simplified view of the game loop
  1. 01Read inputFlight and weapons
  2. 02Update worldPhysics, enemies, collisions
  3. 03Render sceneOpenGL drawing
  4. 04RepeatDisplay the next frame

A conceptual view of the implemented callbacks. Simulation and rendering live in the main Python game file.

03 / KEY DECISIONS

The details that shape the build.

01

Connect hazards to movement

Black holes attract, white holes repel, and wormholes relocate the player. Environmental objects affect navigation as well as the scene.

02

Offer two perspectives

First-person and third-person views give players different ways to judge position and threats.

03

Let challenge grow with play

Difficulty settings and progression affect combat. Upgrades and enemy scaling give continued play a changing rhythm.

04 / THE RESULT

An explorable combat sandbox.

The build includes flight, enemies, weapon upgrades, gravitational hazards, and score tracking.

A constraint worth understanding

Parts of the physics use an assumed frame rate. Measured elapsed time would be a useful next step toward more consistent simulation across machines.

05 / EXPLORE THE CODE

Go one level deeper.

Follow the implementation behind the decisions.

NEXT CASE STUDY / 01F1 Pitwall Analytics