Easy lookup/access to members in "an array" of different datatypes if possible
category: code [glöplog]
rudi: If you want to take that path then go ahead, but if you've made "several demoengines" (like you said) I expect at least a gazillion demos made with them. If it's not the case then there must be something wrong, demoengines are supposed to increase productivity not the other way around :)
In my case, I did a few demos before deciding to build a "nice" system. It was pretty straightforward because after those demos I knew what I needed and how I wanted it to be right from the start. It's now 10 years old and I still can make demos with it pretty easily.
If I had chosen to aim high right from the beginning I'm pretty sure it would have been a mess and would have needed to redo everything again.
In my case, I did a few demos before deciding to build a "nice" system. It was pretty straightforward because after those demos I knew what I needed and how I wanted it to be right from the start. It's now 10 years old and I still can make demos with it pretty easily.
If I had chosen to aim high right from the beginning I'm pretty sure it would have been a mess and would have needed to redo everything again.
ithaqua! :)
<3 Everybody! :)
Quote:
then there must be something wrong, demoengines are supposed to increase productivity not the other way around :)
of course. it was like too complicated approaches. my previous ones made my productivity suck for the most part. really code suck when it is like so. alot of wasteful hours. i hope for the sake of humanity that i dont have to redo anything with this latest approach. if it turns out the design is flawed, then i can say goodbye to coding once and for all. isnt that so?
Quote:
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.
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.
kb_: I fuck the GPU. yes you're exactly right. i will optimize only where it matters. firstly i need this thing done. when it is, then all the optimizing fun begins. hopefully.
what the hell is Wayne Bars anyway?
ok, fuck it. back to the issue.
Quote:
Hmm, ever thought to read the readme?? :Dwhat the hell is Wayne Bars anyway?
No, should I? ok, i will.
rudi: Fucking GPUs could be a large mistake in a few years' perspective, sir. Unless you want to stay in the oldschool realm.
kbi: GPU's change more than CPU's. if it really gets nasty, i will go back to C64-coding again, and stay there.
rudi i'm going to axe kick you in the face at revision for being such a fucking tool
ithaqua: puta for no boozing tho! :P
thanks plek. i appreciate all kind words from you!! how is that beer going? :)
well that's bullshit of course :) but seriously, why are you so keen on rubbing people the wrong way?
maali: Next time do an extra 350km to Madrid and we'll get hammered :)
itha: are you willing to get hammered if I come to Madrid this spring? please bring your brother (a.k.a Pablo Escobar) as well :)
Madridpubmeet \o/
plek: of course but, what do you want me to say? that i should axe kick you in your the face as well? :)
and in the time that rudi has spent on arguing on pouet - everyone else has made a brand new shiny bytecode interpreting vm for the demo engines. hurray!
rasmus wins. Can we all spend our time better now?
I only know "ex kick to the face"...
Quote:
a brand new shiny bytecode interpreting vm for the demo engines
@rasmus: :-) wait, better eval the syntax tree unless you want to go the whole nine yards and JIT your code
(on 68K and similar older CPUs the bytecode approach was faster, indeed. on modern X86 or ARM (Cortex) CPUs recursive evaluation seems faster in case of a reasonably complex program/script)
Quote:
rudi i'm going to axe kick you in the face at revision
haha, he said "at" and then the name of a demoparty! :-) :-) :-)
i have to wear a god damn helmet! lol