Anmelden
?

96 Kbyte(!!) 3d-Shooter

system requirements
----------------------

.kkrieger requires a relatively high-end machine to run properly. To be
precise:

- A 1.5GHz Pentium3/Athlon or faster.
- 512MB of RAM (or more)
- A Geforce4Ti (or higher) or ATI Radeon8500 (or higher) graphics card
supporting pixel shaders 1.3, preferably with 128MB or more of VRAM.
- Some kind of sound hardware
- DirectX 9.0b

We've done some testing to ensure it runs on all hardware meeting those
requirements we could get, and we checked it runs on all major supported
configurations with current drivers, but with some graphics card/driver
combinations it might screw up. In case you have problems, please try
getting the most recent driver release from your vendor, and only if the
problem persists contact us (refer to the contact section).
Klicken, um alles anzuzeigen...

technical FAQ
----------------

In general, if you have any technical questions concerning .kkrieger, either refer to our
web site or contact us via email. However past experience shows that there are some rumours
and misunderstandings about our work that are very hard to correct, so we'll state the truth
here, in written form, for all the world to see :)

- 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.
Klicken, um alles anzuzeigen...



contact
----------

web site: http://www.theprodukkt.com
contact: fanmail@theprodukkt.com (fanmail, flames and cooking recipes)
Klicken, um alles anzuzeigen...


Und noch ein paar screens:

pretty.jpg


kk2.jpg
 
also ist schon erstaunlich was man mit so wenig speicher alles machen kann!
aber es lädt aber verdammt lange! (1024MB ram) man merkt förmlich wie das game gerade erstellt wird.. ;)

und wirklich flüssig läuft es auch nicht...
 
habs auch gerade ausprobiert.

nach der ca. 30sekündigen ladezeit startet das game und ist absolut flüssig.
sehr weit hab ich zwar nicht gespielt... da ich gleich weg muss, aber meine 1,5 Gb RAM scheinen zu reichen ;)
 
Bei mir ruckelte das Spiel ebenfalls nicht - bei 2 GHz Ram ist das allerdings auch nicht verwunderlich. :)
 
Flüssig ist relativ ..... die FPS waren nicht ultra hoch .. aber es ruckelte nicht störend.

Aber schon ziemlich HighTech das Teil ...
Stencil Shadows und BumpMapping sticht ins Auge ...
 
Wahrscheinlich werden mein AthlonXP 2700+ und mein 1 Gig Ram dem Spiel nicht im Wege stehen, aber meine ÜbergangsgraKa schon ( GeForce 4 MX 440 :( verdammtes Scheissteil!!! ).
Nächsten Monat beobachte ich erstma die Fights zwischen dem nv40 und dem R420 und kaufe mir dann eine neue...
 
Du musst dich anmelden oder registrieren, um zu antworten.
Zurück
Top Bottom