3 ms·
Right that was my point - if a 64k demo had to actually push pixels into a framebuffer or similar API (like it was 20+ years ago), how big would they have to be
by MichaelGG 12y ago
Right that was my point - if a 64k demo had to actually push pixels into a framebuffer or similar API (like it was 20+ years ago), how big would they have to be? That is, how many bytes are saved by having high level frameworks that can do T&L and more all in the stack?
- theandrewbailey 12y agoThat's probably a question that only an Nvidia or AMD engineer can answer.
- Narishma 12y agoIt hasn't been possible to do that on PC since the DOS days. You have to go through a number of abstractions (APIs, drivers) to display anything on screen, or to play anything through your sound card.
- pjc50 12y agoBytes are often added by the high level frameworks (see the megabytes of unused C library). Putting a pixel in a framebuffer requires a single instruction. You can do quite a lot of T&L in short bits of code. Have a look at the source code for Second Reality, one of the more popular demos of 20 years ago. https://github.com/mtuomi/SecondReality https://github.com/mtuomi/SecondReality particularly the draw code https://github.com/mtuomi/SecondReality/blob/master/VISU/ADRAW.ASM https://github.com/mtuomi/SecondReality/blob/master/VISU/ADR... ; admittedly it does one light and no texttures, but it does it in a few kb of assembly.