5 ms·
That's unreal. On what kind of graphics hardware, though? Seems like it probably offloads most of the work on GPU whereas we'd have had to do most of it in soft
by nickpsecurity 10y ago
That's unreal. On what kind of graphics hardware, though? Seems like it probably offloads most of the work on GPU whereas we'd have had to do most of it in software on HW weak enough that 4KB size actually mattered. And probably not achieve this demo.
- adamnemecek 10y agoThe 4kb restriction isn't there to make it run on weak hw, it's there to push people.
- nickpsecurity 10y agoI figured that. It's just that almost everythings done on the GPU for a rendering demo. That's really pushing people. ;)
- arcticfox 10y agoThe wink face makes it seem like you think this is easy because using a GPU to execute the program is allowed. No? Edit: just read your other comment about real challenges in the C64 subset of the demoscene. That's like "You set a record in a 1600m race? For a real challenge, set a record in a marathon." It's just arbitrarily moving the totally legitimate goalposts to a different challenge because you prefer it.
- nickpsecurity 10y agoHow much harder would it be if software rendered or on a simple GPU from the late 90's? Their executable still 4KB? No?
- Kristine1975 10y ago>How much harder would it be if on a simple GPU from the late 90's It would be impossible since pixel shaders didn't exist until the 2000's ;-) As for software rendering: Since a pixel shader is essentially a program executed for every pixel, it's trivially portable to the CPU: Just turn it into a function and call it for every pixel on the screen. Making it fast is another matter altogether though.
- nickpsecurity 10y ago"It would be impossible since pixel shaders didn't exist until the 2000's ;-)" Lmao. You got me there. "Just turn it into a function and call it for every pixel on the screen. Making it fast is another matter altogether though." I was imagining it took up many MB of memory and massive cycles even on a multicore CPU. Suddenly, one faces tough decisions about organization, resolution, primitives, techniques used, algorithms, and so on. Gets really, really hard to make tiny and fast stuff without that GPU doing heavy lifting. :)
- chipsy 10y agoA soft renderer wouldn't fit in 4096 bytes, too. The overwhelming preference of the demoscene when doing PC filesize compos is to lean on OS provisions in order to free up space for more algorithms. Hence you have demos that use files in C:\Windows as source data. Likewise, you have demos for older computers that require aftermarket RAM upgrades and employ preprocessing techniques that require modern computing resources. In unrestricted compos modern game engines get employed these days, too, and while many of those entries suffer the downside of having a low entry bar, good work has been made too. Pointing at the GPU as a particular cheat or a make-easy button is not relevant to the conversation, in this light. Having a Gravis Ultrasound was also a cheat back in the day ;) It's all fairly arbitrary stuff, and in the end, the point is to present something cool running on the hardware and within the nominal restrictions, even if you get tricky to do so.
- nickpsecurity 10y ago"It's all fairly arbitrary stuff, and in the end, the point is to present something cool running on the hardware and within the nominal restrictions, even if you get tricky to do so." Another good, detailed perspective on it. Appreciate it. I'll especially agree with the part I quoted. :)
- zurn 10y agoNitpicking: in the offline rendering world RenderMan had shaders ca. 1990[1], and graphics hackers got around to compiling those for research GPUs in the 90s too[2]. (Hardware had programmability equivalent to current shaders early as well [3], but no compilers for fancy shading languages) [1] https://people.csail.mit.edu/ericchan/bib/pdf/p289-hanrahan.pdf https://people.csail.mit.edu/ericchan/bib/pdf/p289-hanrahan.... [2] http://www.cs.unc.edu/~olano/papers/pxflshading.pdf http://www.cs.unc.edu/~olano/papers/pxflshading.pdf [3] http://www.cs.unc.edu/~pxfl/papers/high-speed_rendering.pdf http://www.cs.unc.edu/~pxfl/papers/high-speed_rendering.pdf
- nickpsecurity 10y agoResponse to edit: more like they couldn't pull it off so they asked people to buy a better graphics card. That's in their own race. Then I pointed out doing graphics operations, mostly rendering, almost entirely on a graphics card designed for that was barely an accomplishment vs stuff like in C64 demoscene. .kkrieger had me way more impressed due to all the elements involved vs size. So, I suggested subsetting or constraining the graphics card so its hundreds of millions of transistors don't just hand people their victories. Plus allow more creativity.
- imtringued 10y agoHowever it does irritate me that it's pregenerating the entire scene in memory. Being allowed to use 300MB of RAM doesn't strike me as very limiting.
- nickpsecurity 10y ago"Being allowed to use 300MB of RAM doesn't strike me as very limiting." BOOM! I knew it was going to be huge. That's a beefy GPU + 300MB in RAM + pregenerating. I'd have... made sacrifices to have that even in the Half-Life 1 days. :)
- wolfd 10y agoYou wanted optimized code size and optimized performance? I mean, sure, but think about how big 4KB is, the tricks that are being used to create the scenes are crazy hacks using default Windows sound files and literally anything the executable can reference on the cheap. Procedural content generation is really expensive (in general), but that's the beauty of it. You find a way to abstract the content into an algorithm, and then you can reduce the size of the assets, but you pretty much always need to pay the price somewhere. But hey, I understand the sentiment, I wish Slack didn't consume 2 GB of RAM on my machine.
- Kristine1975 10y ago>Seems like it probably offloads most of the work on GPU It does just about everything on the GPU. All the CPU does is repeatedly render two triangles and play music: https://news.ycombinator.com/item?id=8070879 https://news.ycombinator.com/item?id=8070879 Here it has been adapted to WebGL: https://www.shadertoy.com/view/MdX3Rr https://www.shadertoy.com/view/MdX3Rr Edit: I'm wrong about the two triangles. From the .nfo-file: for those wondering, this a (too) low density flat mesh displaced with a procedural vertex shader. there arent any texturemaps for texturing, instead texturing (and shading) is defferred and computed procedurally in a full screen quad. this means there is zero overdraw for the quite expensive material at the cost of a single geometry pass. then another second full screen quad computes the motion blur. camera movements are computed by a shader too and not in the cpu, as only the gpu knows the procedural definition of the landscape.
- nickpsecurity 10y agoThanks for detailed response. I figured it mostly did GPU stuff. So, real computing necessary here is a massively-parallel chip with generic and custom hardware with a bunch of memory plus a regular core using 4KB on other end. I think a more interesting challenge would be to force use of a subset of GPU functions or memory plus tiny memory on CPU side. I don't follow demoscene close enough to know if they subset GPU's like that. Idea being making them run closer to the old Voodoo or pre-GeForce GPU's to see just how much 2D or 3D performance once could squeeze out of it. Tricks could have long-term benefit given any emerging FOSS GPU is more likely to be like one of the older ones given complexity of new ones. I'd clone one like SGI's Octane ones they used to do movies on with mere 200MHz processors. Meanwhile, similar tricks might let one squeeze more out of the existing, embedded GPU's in use. Maybe subset a PC GPU in demoscenes like one of the smartphone GPU's. Yeah, that's got some interesting potential.
- Kristine1975 10y ago>plus a regular core using 4KB on other end. The .exe is 4K (it has been compressed using Crinkler), not the application's RAM requirements. The game .kkrieger for example is a 96K .exe, but uses several hundred MB of RAM when run. Also, the strict size requirements can interfere with execution speed. From the .nfo again: believe it or not, this was running at 30 fps in a gefoce 7900 at some point, but size optimizations forced us to ask you for a pretty decent graphics card, like a geforce 8800gtx or hd4850. please, make sure you have d3d9_33.dll somewhere there. also, you only need windows xp.
- pjc50 10y agoThe C64 subset of the demoscene is still going if you want it.
- nickpsecurity 10y agoThat's a real challenge. :) My comment to Kristine has some other details on how we might do something between that and a full GPU.
- Frenchgeek 10y agoIf we go that way, a real challenge would be designing your own computer then making a demo to run on it. Just because the tools are more capable doesn't mean the challenge is any less real or the result less impressive.
- nickpsecurity 10y agoI'm actually working toward that challenge. Well, that plus synthesis, verification, and analog tech to create it. Glad we agree on high end for a demo challenge. :P
- FreeFull 10y agohttp://www.linusakesson.net/scene/parallelogram/index.php http://www.linusakesson.net/scene/parallelogram/index.php Here is a demo from someone who has actually done just that. He's done a lot of other cool stuff too.
- nickpsecurity 10y agoI have nothing but props for that one. A true, full-stack or whole-system coder in the way the term should be used. He's also about halfway to Frenchgeek's grand challenge. Maybe we need to take up funding for him to put it all on an ASIC at 0.35 micron.