pouët.net

rudi, have you tried using ?

Oh GOD, you are over-engineering, rudi. Just stop. Forget your "neat" idea. It's not neat at all.

Maybe it's not the answer you're looking for and it may seem obvious but you don't need a demoengine to make a demo, especially not if (from what I understand) you haven't coded any yet.
Make a couple demos first, don't worry about the code being clean and elegant, and with all the knowledge and problems faced design a system that simply will make the process easier. If you do it the other way around you'll waste a lot of time on something that probably won't be of any help because you're facing problems you didn't know that existed in the first place.
The key is what plek said, code what you need, not what you think you may need.

After you've done 2 or 3 demos you'll know exactly what you need, then you can code a demoengine straight to the point and masturbate at the code all you want.

ithaqua <3

i thought std::vector was evil?

kusma: if i managed to get to solskogen we can talk this over a beer.

ithaqua: how many demos do you think ive coded in the past? forget about the crappy quality. i know what i need, i need this. you are funny man! i won't face any problems with my idea. the only problems i can think of is the compiler and syntax itself!

so now you're taking on ithaqua as well? you don't really know when to stop, do you? :)

right now, ill stop. because im hungry for pizza. cu later.

not a pro in c++. i can barely handle that dynamic cast stuff. but I'd think that construct might work if the compiler stays awake. but i think those scattered pointer arithmetics and memory accesses from the variable index to the value might kill the performance. I'd not do it like that. some good allocated structs and types that have a good size on the cache might be better. they 're controllable and easier to route. maybe I'm even just to dumb to learn extended c-slang and do it the simple way. :/

yumeji: what you're saying makes a *lot* more sense than most of what we've seen here, really.

holy shit Ithaqua is alive :D

ARISE! \o/

Yeah, then again: People, it's a demo system. Perhaps some stuff is being generated per frame and then the GPU does all the work. And most of you here are talking of vtable overhead, cache misses and branch prediction like any of today's CPUs actually gave the slightest fuck about it. Seriously. In Wz4 we have a bytecode interpreter running _per operator_ (ok, for all ones that have an animation script) every frame and it still comes up at the bottom of the profiler result.

How about optimizing only where it matters because that's also a very important part of the process of making a demo about it. Seriously, should I ever get into demo engine programming again I'd probably do it in C# and do all the demanding stuff in the GPU anyway.

(I'd still use a generic container and a base interface instead of what Jcl does tho :D)

kb: you're absolutely right. but you can't blame people for reasoning from a professional point of view where such stuff in a huge codebase actually *can* matter, when running your game or what have you on a stupid ppc cpu. especially when people make incorrect statements it's no crime to set the record straight, much like chris pontius did on the russian police.

but again, you're right. demos. i can hardly believe how crappy my early 200s solutions were but hey, it rendered polies (*). tadaa.


* - and avis.

2000s

enrique: puta puta puta! ;)

we missed our change to booze in valencia, dammit ;)

Pouetization when you need it. provided by Maali. ;)

maal is an ass

LOOK I DID IT AGAIN

Like struct :)

Yeah well, I still visit Pouet, it's just that I don't post that often :D

i'll go for bisual vasic

ithaqua! <3