pouët.net

and we should cater to his demands of video so he can peruse at his leisure.

Obviously it's a fucking ridiculous idea.

So are there many people who think that defining compo rules only in terms of size limit and platform is somehow unfair?

The way I see it, the development of computing power and facilities provided by the GPU, drivers and libraries bundled with operating systems is essentially providing an "engine" i.e. a higher-level language to work with. You can say much more with much less bytes. So, why the heck has the demo size limit gone UP at the same time. As if the platform improvements weren't enough.

Mesh size? Texture size? Materials use more textures and maps? Shit gets big yo.

yep ^^ textures take lots of space. for a classic shader i use albedo,normal,gloss, metal a in 1024 or 2048 res :)

yzi: that's not code, but data related. e.g. a 5k polys 3DS with a 256x256 JPEG envmap from 2001 is a lot smaller than a 500k polys FBX with 4x 2048x2048 PNG color, spec, gloss, normal/height-maps last time i looked!

But can't we just go back to 5k poly 3Ds with 256x256 JPEG envmaps and make them look super modern?

and that gets even worse when you bake your 3D-voronoi-explosions of a mid-poly skull in PLA data :P

Because if you're writing at the 'cutting edge' (which is what PC demos usually aspire to) your assets, libraries, and general data increase in size exponentially with each big hardware iteration. If you want "2016-grade" demos you can't keep using the same workflow to get there. (in some cases literally can't use the same workflow anymore) PC demo is the only category where pre-calcing assets isn't the norm and it should stay that way.

britelite: i got it for free!!!! :)

How much are you paying? Hey, my demos might be worth something after all!