3D Game in 96 KB

Originally Posted by Xterria

i don't understand...

Instead of a modular setup where there's a game engine, maps, monsters, sounds, etc. that have been precreated manually, all of which you can edit/create&replace/input new, this game is fixed where all of the needed code was set in place to generate what you see.

in case you don't read readme files::

-from the readme

- We do .not. have some kind of magical data compression machine that is able to squeeze
hundreds of megabytes of mesh/texture and sound data into 96k. We merely store the
individual steps employed by the artists to produce their textures and meshes, in a very
compact way. This allows us to get .much. higher data density than is achievable with
normal data compression techniques, at some expense in artistic freedom and loading times.
- .kkrieger is not written in 100% assembler/machine language. Not even nearly. Like the
vast majority of game projects being developed today, .kkrieger was mostly written in
C++, with some tiny bits of assembler where it is actually advantageous (notably, there
are a lot of MMX optimisations in the texture generator).
- A kilobyte is, historically, defined to be 1024 (2^10) bytes, not 1000. Thus .kkrieger is
a game in 96k even though it's actually 98304 bytes.
- The concept of the texture/mesh generators was developed by fiver2. We do .not. want to
claim that the techniques we used to develop .kkrieger are new inventions. It´s rather a
selection of useful operations and their parameters to optimise the results.

isn't there a program that, when you give it a 3ds model or somthing, gives you opengl code that you can copy and paste into the program to create a polygon identical to the 3ds model? so you don't have to do all the importing?

i believe that there is, and actually anyone who understands the fileformat of models could write a program to do that

...or anyone who can visit http://www.wotsit.org/

that too

actually, come to think of it, they way they say that they did the texture thing sounds like it would limit their quality of textures quite a bit, but from the screenshots they're incredibly good looking. I don't see how they could do that same thing with the textures as it would most likely be the same size or not much smaller to make a difference. However, I can't play the game for some reason, so I don't even really know what it's like real-time...

The game plays slow on my p4 2.8 Ghz 512 MB ram Gforce FX 5650 64MB vram system... It is truly power hungryy

Its fine on my AMD 2500+ 512 MB Ram Radeon 9700

The loading time was godly long tho

anyhow the game was VERY VERY VERY nice for 96kb, in fact, above many of a several mb games that i play. anyhow, the only bad part was the physics of the guns were mesed up and no crosshair

I gun physics were great. They had gravity affect the particles. However, not having a crosshair is my only complaint from this game. It ran fine on my computer.

It'd be nice to see the source for this...

I saw this earlier on a different forum, today, actually.
96 KB... Geez...

Edit:

And the reason it takes so much memory is because that's how they get the game so small. It loads everything into the memory rather than onto the hard drive...