Revision Demo Party 2019

…must be the first demoish code for quite a while on Risc OS. I rememeber that one from pouet. Though I can’t get it to run on my RPI3. I set the Filetype to ‘Absolute’, correct or ? May be it’s my ancient Risc OS 5.23 ?

5.23 should be fine, I think.

It should be an untyped file with load+exec of &8A80

Yeah, hard choice what one can do on Risc OS as a demo that would be impressive. But sometimes the idea is more important than any kind of coderporn ;-)

You don’t even need coding skills to do a demo these days. There are some very clever people out there who create a demo out of music!!!!

https://www.youtube.com/watch?v=r8Lm9CoxEHg&list=LLD2DwfUj4FwX777RmSC0Vjg&index=222&t=0s
check this video from Revision 2018. – ABSOLUTELY AWESOME – make sure you watch right to the end cause it keeps getting more impressive as it progresses.

@Jeffrey: Works flawless, it was just that I unpacked on PC to USB-Stick and then it didn’t like it to run. Any chance for the source code/assembler code on this ? I’d just like to know if you find short ways for the OS-specific stuff (double buffering, getting screen address, exit etc.)

@Alan: Is saw that one live last year, that was pretty cool, it must have been a hell of work to put all that kind of ASCII-Art into the track.

Source now uploaded:

http://www.phlamethrower.co.uk/riscos/creation.php

This is after I’ve tidied up the code a bit (mainly the math code), so it’s not exactly the same as was used with the original. There’s also source to a (rather slow) conversion of http://glslsandbox.com/e#53899

I’d just like to know if you find short ways for the OS-specific stuff (double buffering, getting screen address, exit etc.)

There isn’t much magic there. There’s no double buffering, and getting the screen address is just done using OS_ReadVduVariables. Exit handling is criminally minimal (it doesn’t install exit/error handlers, so the VFP context – which is located in app space – isn’t cleaned up if the demo exits abnormally, which can cause problems. I did intend to change it to use the RMA, which would allow it to leak harmlessly (and shrink the code a bit), but forgot!)