This is the rather appallingly named RoXXoRoIDz, my Asteroids derivative for the GBA (with a quick and dirty DS port also up and running). If anyone's got a better naming suggestion for a Spheres of Chaos/Geometry Wars inspired Minteresque shooter, please let me know
It's not finished or available yet, but once I get my arse in gear and pull it all together I'll shout.
nyarla wrote:I like the name RoXXoRoIDz, but r0xx0roids would be even better.
looks nice!
Lower-case in the font I'm using looks a bit crap, hence the inversion. I'll probably be changing or at least tweaking the font before I finish so the latter may make a return (assuming a better name doesn't turn up).
thalamus wrote:Currently slaving away on FishEd, my 2D Map Editor:
Heh. I see you've met the RAGE of the Blitz programming forums.
I'm saying nothing.
"We don't have a great war in our generation, or a great depression, but we do, we have a great war of the spirit. We have a great revolution against the culture. The great depression is ourlives. We have a spiritual depression." - Tyler Durden
Scribbling on notes for a 4/8K MiniGame thing that is a bit like Sokoban (viewpoint and movement at least) but is more centered on item combination puzzles.
I'll probably find that it is nearly exactly like something else if I ever finish it and get it released...
Istar wrote:Step four, commenced last week, is to write a VB6 app that lets me 'debug' and tweak the microcode, and make sure every instruction is described, has the right addressing modes, sets the right flags, etc. This is a 'not for public release' housekeeping app to get the instruction database clean and working.
Istar wrote:Step four, commenced last week, is to write a VB6 app that lets me 'debug' and tweak the microcode, and make sure every instruction is described, has the right addressing modes, sets the right flags, etc. This is a 'not for public release' housekeeping app to get the instruction database clean and working.
Yawn... I'm writing a device driver which allows me to allocate kernel memory, extract the physical address and then all the user mode application to map this address into their virtual memory. I've got the allocation and free working, just got to do the phys -> virt mapping this afternoon.
Device drivers are buggers to write, the development environment is crap, command line compilers etc. I've managed to scrape together an MFC application to communicate with the driver, but even this is a hack because the DDK header files aren't compatible with the Visual Studio compiler.
Oh, by the way I've never written device drivers before so if anyone has any useful information please feel free to butt in!
Glyndwr wrote:Yawn... I'm writing a device driver which allows me to allocate kernel memory, extract the physical address and then all the user mode application to map this address into their virtual memory. I've got the allocation and free working, just got to do the phys -> virt mapping this afternoon.
Device drivers are buggers to write, the development environment is crap, command line compilers etc. I've managed to scrape together an MFC application to communicate with the driver, but even this is a hack because the DDK header files aren't compatible with the Visual Studio compiler.
Oh, by the way I've never written device drivers before so if anyone has any useful information please feel free to butt in!
Curiousity piqued, why do you need to so this?
P.S. Just seen your location, if live/work anywhere near the Greene King brewer then I'm just a touch jealous.