BAH. Crashes on launch in my lappy... Though it doesn't meet the requirements. (P3 700 ATI Rage Mobility).
This requires 512MB of ram to work properly. All game code is rendered and stored in RAM for fast access. Runs fine on our systems here. Another fine work by Chaos and RYB.
Cheers!
didn't work here; disappears after 20 seconds or so.
740 MB ram with a 64MB DDR graphics card, radeon mobility. more than enough HD space (64 kb? )...
no clue why doesnt' work
740 MB ram with a 64MB DDR graphics card, radeon mobility. more than enough HD space (64 kb?
)...no clue why doesnt' work
the graphics, more importantly the textures, are rendered on the fly when you start the game. The engine is impressive for 96kb.
Originally posted by: paruhd0x
Someone link a site with more of these.... I tried google and failed
I don't believe this is an official intro from Farbrausch, but if you're interested in more stuff like this, its known as "The scene". Try
www.scene.org - click on 'viewing tips' on the top.
Also, www.pouet.net is probably one of the best resources for your demo/intro appetites.
EDIT: Apparantly, this isn't made by Farbbrausch at all. Not sure why its named "the produkkt", since its not made by the same people as the original product.
Rendering the textures after you start the game doesn't mean the game has to be slow. It's not rendering as you play.
SunnyD
Belgian Waffler
These are so tiny because they generate the texture data mathematically (procedural textures), as well as do some amazing compression on the code and data. I remember reading about the demo scene once especially with .produkt - they were given approximately 72 hours to compete a demo, competely with 3d graphics and sound, using no external 3D API's, with code and data all together under 100K. They barely made it, and they were doing some amazing things like writing their own audio trackers and such using assembler in 100 bytes or so.
The procedural textures are huge when generated, 512x512 and more. Like I said, they're all mathematically generated, which is how they make the final product so small. Goes to show you that a lot can be done using math. However, not everything always looks good.
The procedural textures are huge when generated, 512x512 and more. Like I said, they're all mathematically generated, which is how they make the final product so small. Goes to show you that a lot can be done using math. However, not everything always looks good.
2ghz Athlon (2400+) with 512mb ram (well, with lots running in the bg), as well as a 9800Pro.
Load time is worse than BF1942, the graphics look a few notches above Quake (smoother and not as pixellated, but still...), and my FPS is horrible. Plus, this thing NEEDS a crosshair. In addition, in the loading movie especially, the colors look washed out. Int he actual game (I only went in a little bit), the color is fine.
Load time is worse than BF1942, the graphics look a few notches above Quake (smoother and not as pixellated, but still...), and my FPS is horrible. Plus, this thing NEEDS a crosshair. In addition, in the loading movie especially, the colors look washed out. Int he actual game (I only went in a little bit), the color is fine.
pretty interesting.. low frames but i'm running a bunch of stuff in the background... on a ti4600. But it didn't look right, washed out.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 23K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter