3 ms·
First of all, there is. There's people making Linux demos. There's plenty cross-platform demos, too. Search http://www.pouet.net http://www.pouet.net for Linux
by skrebbel 14y ago
First of all, there is. There's people making Linux demos. There's plenty cross-platform demos, too. Search http://www.pouet.net http://www.pouet.net for Linux demos.
However, indeed it's pretty thin compared to Windows demos. There's a bunch of reasons, but I believe that there are three big ones:
1. Linux, until fairly recently, required a significant amount of tinkering and tweaking config files before you could even use it decently, let alone code graphics on it. This does not match the average demoscener's mindset; most demosceners want to get stuff on the screen, now. A side-effect of this attitude, by the way, is really shitty code, which in turn has contributed to the small amount of open source demos out there (people are ashamed of the pile of dirt that's under the hood).
2. For most of the nineties and early zeroes, Windows was obviously the strongest platform for 3D graphics. All the graphics hardware just worked, you could choose between OpenGL and DirectX and typically both had decent drivers. You could say that that's unfair because the hardware vendors supported Windows, and Linux drivers were often homecooked by the community, but that's beside the point: Stuff. On the screen. Now.
3. Audience. You could give a Windows demo to your gamer friend and he could see it. Of course, you couldn't give the Windows demo to that classmate who only ran Linux, but you'd prefer not to get into a discussion with him anyway because It'd always turn into a rant about licenses and freedom. Or, well, that's how the common perception of "the average Linux user" was among much of the demoscene.
Nowadays, many active demosceners are game programmers by day, and Windows still is the strongest game dev platform. These people are used to Windows gamedev tools and switching for the evening hobby just sounds too much of a hassle.
- anonymous 14y agoI was actually hoping that, with the release of documentation on AMD's graphics cards, we'd see demos coded "on the metal", without passing through the standard graphics stack. That won't be possible on windows, since you can't just boot to console and then bang the pci bus yourself, but would be possible on linux. It could even be written as a kernel module for maximum effect.
- seanmcdirmid 14y agoDirectX is pretty efficient already. I don't think you would be able to push many more polygons going to the metal.
- bni 14y agoThe impressive graphics (for the hardware) on current gen consoles showns what is possible when going to the metal, bypassing several layers of WDM, scheduler, drivers and DirectX.
- CJefferson 14y agoI believe, on the Xbox 360 at least, you have to go through the scheduler, drivers and DirectX. There is no direct hardware access.
- Narishma 14y agoDirectX on the Xbox 360 is very lightweight and exposes a lot more of the hardware than what you get on Windows.
- seanmcdirmid 14y agoNo it doesn't. It takes a lot of effort with Cell just to reach parity, Xbox is basically DX9. You program the GPU by writing shaders that run right on the GPU, the only perf increases to be had involve how fast you can move data on and off the GPU. Eliminating all abstraction might give you a few percentage points, not enough to do anything that we would consider amazing under current circumstances.
- wladimir 14y agoThat would be nice, but I think the issue is less one of documentation (lots of demosceners into reverse engineering) but that there are (a) just too many different graphics cards out there (b) the platform lifetime is very short (c) less motivation for hw specific tricks as "everything is already possible"; GPUs these days are parallel general purpose computing hardware, at most you'll speed up something a bit. If you make your demo to work on one ATI card you will have a small audience at most, and the card will be out of the market in a year and all the tricks you learnt were for nothing. And if you want it to work on more hardware you get into the device driver business, and that rules out special tricks for specific hardware to do non-standard rendering anyway... Back in the days of home computers there was one longer-lived hardware platform that many people were using. There is a faint hope that initiatives such as the Raspberry Pi may bring people to "standardize" on one more or less ubiquitous platform for longer time, but I'm afraid this ship has sailed. So it makes sense for demosceners to focus on what is possible on the higher, portable API level.