pouët.net

Go to bottom

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.
added on the 2012-02-14 19:58:02 by ithaqua ithaqua
ithaqua! :)
added on the 2012-02-14 20:01:13 by gloom gloom
<3 Everybody! :)
added on the 2012-02-14 20:01:23 by ithaqua ithaqua
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?
added on the 2012-02-14 20:09:33 by rudi rudi
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.
added on the 2012-02-14 20:21:27 by rudi rudi
what the hell is Wayne Bars anyway?
added on the 2012-02-14 20:24:30 by rudi rudi
ok, fuck it. back to the issue.
added on the 2012-02-14 20:26:27 by rudi rudi
Quote:
what the hell is Wayne Bars anyway?
Hmm, ever thought to read the readme?? :D
added on the 2012-02-14 20:29:06 by ferris ferris
No, should I? ok, i will.
added on the 2012-02-14 20:30:20 by rudi rudi
rudi: Fucking GPUs could be a large mistake in a few years' perspective, sir. Unless you want to stay in the oldschool realm.
added on the 2012-02-14 20:33:33 by kbi kbi
kbi: GPU's change more than CPU's. if it really gets nasty, i will go back to C64-coding again, and stay there.
added on the 2012-02-14 20:39:21 by rudi rudi
rudi i'm going to axe kick you in the face at revision for being such a fucking tool
added on the 2012-02-14 20:50:37 by superplek superplek
ithaqua: puta for no boozing tho! :P
thanks plek. i appreciate all kind words from you!! how is that beer going? :)
added on the 2012-02-14 20:56:04 by rudi rudi
well that's bullshit of course :) but seriously, why are you so keen on rubbing people the wrong way?
added on the 2012-02-14 21:01:12 by superplek superplek
maali: Next time do an extra 350km to Madrid and we'll get hammered :)
added on the 2012-02-14 21:41:59 by ithaqua ithaqua
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 :)
added on the 2012-02-14 22:08:08 by superplek superplek
Madridpubmeet \o/
added on the 2012-02-14 23:05:30 by ithaqua ithaqua
plek: of course but, what do you want me to say? that i should axe kick you in your the face as well? :)
added on the 2012-02-15 07:01:34 by rudi rudi
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?
added on the 2012-02-15 09:17:31 by gloom gloom
I only know "ex kick to the face"...
added on the 2012-02-15 10:36:05 by raer raer
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)
added on the 2012-02-15 12:25:34 by xyz xyz
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! :-) :-) :-)
added on the 2012-02-15 12:41:57 by skrebbel skrebbel
i have to wear a god damn helmet! lol
added on the 2012-02-15 15:09:00 by rudi rudi

login

Go to top