Amiga38 demo compos
category: general [glöplog]
Amiga38 news
It's nice to see the makers of the Vampire platform to hold compos for the Vampire V4 standalone platform, OCS/1MB and stock A1200!
FPGA, PiStorm etc seem difficult - even for more open demoparties like Revision and Assembly, they go in Wild compo. Why should they, when those parties allow PC, and other platforms like Javascript that also change?
At least to me there's 3 major categories, 8, 16, and 32-bit+ with RTG/GPU with regards to what you see and hear. Then for performance there's fixed platform or not. There's a theoretical here - could all demoparties have these 6 democompo categories and nothing else, and the platform you contribute is exactly the one you're coding and having fun on now?
~
This post is some mix of news post and reflection beyond my own preference, which is fiercely Amiga OCS and more a tendency to more limited platforms rather than less. As I think you know ;) And a perfectly defined compo despite platform is the best compo an orga can create.
But I took these news openly, and saw a chance to promote less platform subdivisions, instead of outcries against modern (including early 2000s) accelerators for our beloved fixed platforms. <3
Bottom line: why should the Vampire, RPi etc not find a democompo at demoparties? Demos for them are not 'wilder' than PC demos.
It's nice to see the makers of the Vampire platform to hold compos for the Vampire V4 standalone platform, OCS/1MB and stock A1200!
FPGA, PiStorm etc seem difficult - even for more open demoparties like Revision and Assembly, they go in Wild compo. Why should they, when those parties allow PC, and other platforms like Javascript that also change?
At least to me there's 3 major categories, 8, 16, and 32-bit+ with RTG/GPU with regards to what you see and hear. Then for performance there's fixed platform or not. There's a theoretical here - could all demoparties have these 6 democompo categories and nothing else, and the platform you contribute is exactly the one you're coding and having fun on now?
~
This post is some mix of news post and reflection beyond my own preference, which is fiercely Amiga OCS and more a tendency to more limited platforms rather than less. As I think you know ;) And a perfectly defined compo despite platform is the best compo an orga can create.
But I took these news openly, and saw a chance to promote less platform subdivisions, instead of outcries against modern (including early 2000s) accelerators for our beloved fixed platforms. <3
Bottom line: why should the Vampire, RPi etc not find a democompo at demoparties? Demos for them are not 'wilder' than PC demos.
A software emulator that overrides the CPU and adds virtual peripherals is wilder than a regular PC.
i approve of this use of neuropol!
Nice...Thanks for sharing
@absence
The Vampire is not a software emulator, it is a hardware FPGA implementation.
@Thread
This "why no Vampire on demoscene/compos" discussion keeps popping up for the last 5 years, and I can only repeating myself - if people start making Vampire demos, we will find a compo for them. But lets see those demos first. There are plenty of compos where they're allowed already. Additionally - as I also wrote before - there's absolutely nothing that stops anyone from making a demo that has Vampire specific optimizations - can run in higher resolution on a Vampire, supports its RTG, etc - but still runs on a '060 as well, that is allowed in the compo. But we don't even see that. So all this is theoretical, IMO. Maybe this "Vampire compo" will change this, but ... I have serious doubts. Prove me wrong.
On a personal note: I guess the push from the Vampire team for Vampire-only demos, or anything Vampire is because the PiStorm, especially the PiStorm32 is an "existential threat" to the Vampire. It's much faster, and much cheaper, and provides basically anything the Vampire could to someone who is craving a faster classic Amiga but still want to use some sort of real hardware. The Vampire really opened up RTG for the A500 and A1200 masses, something that was previously mostly available but that is no longer exclusive to it.
For a coder, in practice, the Vampire doesn't really provide anything performance or features wise that hasn't been available on the Amiga for decades in some shape or form. So from this point on, it's just a matter of personal preference.
And in the end, the demoscene is going exactly the other direction currently, more and more people start A500/OCS projects, and even '060/AGA demos start to be a minority in compos. So I doubt there is serious interest for more and faster expansions right now. But as I said, prove me wrong.
(And while we're at it - I'm still in favor of doing OCS/060 stuff, just to piss off OCS purists... :P)
The Vampire is not a software emulator, it is a hardware FPGA implementation.
@Thread
This "why no Vampire on demoscene/compos" discussion keeps popping up for the last 5 years, and I can only repeating myself - if people start making Vampire demos, we will find a compo for them. But lets see those demos first. There are plenty of compos where they're allowed already. Additionally - as I also wrote before - there's absolutely nothing that stops anyone from making a demo that has Vampire specific optimizations - can run in higher resolution on a Vampire, supports its RTG, etc - but still runs on a '060 as well, that is allowed in the compo. But we don't even see that. So all this is theoretical, IMO. Maybe this "Vampire compo" will change this, but ... I have serious doubts. Prove me wrong.
On a personal note: I guess the push from the Vampire team for Vampire-only demos, or anything Vampire is because the PiStorm, especially the PiStorm32 is an "existential threat" to the Vampire. It's much faster, and much cheaper, and provides basically anything the Vampire could to someone who is craving a faster classic Amiga but still want to use some sort of real hardware. The Vampire really opened up RTG for the A500 and A1200 masses, something that was previously mostly available but that is no longer exclusive to it.
For a coder, in practice, the Vampire doesn't really provide anything performance or features wise that hasn't been available on the Amiga for decades in some shape or form. So from this point on, it's just a matter of personal preference.
And in the end, the demoscene is going exactly the other direction currently, more and more people start A500/OCS projects, and even '060/AGA demos start to be a minority in compos. So I doubt there is serious interest for more and faster expansions right now. But as I said, prove me wrong.
(And while we're at it - I'm still in favor of doing OCS/060 stuff, just to piss off OCS purists... :P)
*"something that was previously mostly available but"
Should read: "something that was previously mostly available for big box systems only, but"
Should read: "something that was previously mostly available for big box systems only, but"
Quote:
The Vampire is not a software emulator, it is a hardware FPGA implementation.
Not only that, but it's standalone as well, so based on all that information you can probably guess that I was talking about Pi Storm, and not Vampire. :)
so has there been any release in any category or has it basically been canceled?
thre ewas some routine-snippets all made by the vampireteam what I could understand.
so nah. nothing to see here..
so nah. nothing to see here..
(on Amiga 38 that is)
also this FPGA is an Implementation.. I would say: It depends.
a FPGA CAN be just as the ASIC yes. but I wuold say it is an implementation IF it is done from the original data. but as it is now it is done from the reverse engineered documentation..
so it is Hardware Emulation. NOT implementation.. When someone find the original schematics of the chips and do the fpga code from that. THEN it is implementation!
a FPGA CAN be just as the ASIC yes. but I wuold say it is an implementation IF it is done from the original data. but as it is now it is done from the reverse engineered documentation..
so it is Hardware Emulation. NOT implementation.. When someone find the original schematics of the chips and do the fpga code from that. THEN it is implementation!
4. Bud Linux, maybe oneday?
