As a spin-off from the RISC OS Pyromaniac work, I've been creating a build environment for RISC OS 64 binaries. This is still a work in progress, but building and running 64bit binaries is relatively painless. https://t.co/4747dot66i shows a short video of the compilation.
@robwordsYT check out this quite old video from Dave Gorman about how people have been misusing (or making better) common phrases! https://t.co/FxrkJjJkTL
RISC OS 64 bit presentation to ROUGOL finished ! Went really well with lots of good feedback from people. Thanks for the very friendly reception. Wheeeee!
Whilst debugging some code with Pyromaniac, I know it's doing a large memory initialisation but the trace file of instructions is small; I'm trying to see what's gone wrong. Then I notice a line in the trace: `REPEAT &813c - &8164 1427 times` - a nice feature I'd forgotten!
Recently I had a play with making ChuckieEgg work on RISC OS Pyromaniac. As we don't have a frame buffer, that means that we have to use sprite plotting, but I could pinch that code from Heretic. The result is pretty neat. A BBC game being played on a modern version of RISC OS.
I did a live stream of some coding yesterday afternoon. It turned out rather well - a few small hiccups, but enjoyable, and people in the chat seemed interested. I ported an ARM disassembler to RISC OS and then made a rudimentary Debugger module. https://t.co/CzIcmiINdc
Last year, I showed how the RISC OS Pyromaniac command server can run RISC OS commands within a host shell. Pyromaniac now supports the reverse - running host commands from within RISC OS. Here's a demo of running host commands from RISC OS - running simple tools and an editor.
Last night’a presentation to WROCC about Doom, Heretic and Hexen went really well. Thanks to all and to the group for inviting me. Slides and resources can be found on my presentation site https://t.co/OLlcoSmpzM.
Testing games like Hexen is a rather manual process, but it's still possible to have automated tests. Having accidentally released betas that contained rogue debug code, the CI now runs the release version to check that there is no output. All done through the RO build service.