Your web-browser is very outdated, and as such, this website may not display properly. Please consider upgrading to a modern, faster and more secure browser. Click here to do so.
So one of the reasons I started working on MDE2 was that I enjoyed the process of designing custom processors, but I hated the process of debugging them. You could only see values that you specifically designated for debug viewing, and then only in a visually unintuitive way, as parallel lines on a very long graph, rather than any sort of graphical display. Trying to figure out where things had gone wrong was a nightmare!
Well, here I am, working on the late-game levels of MDE2… and debugging them is a nightmare!
It’s not quite as bad as that makes it sounds. The earlier levels are reasonably easy to debug, and the later ones are still better (simpler) than their ‘real life’ equivalents. But the later levels are long enough & complex enough that it can be tricky to sort the signal (fuck-ups) from the noise!
My current plan is to add a ‘warnings’ system. It’ll watch for things which might be an error (unexpected values written to memory, or to a module which you designate as a regfile), and tell you when & what the problems are if it notices any.
If you have any ideas for useful warnings the game can give, please let me know?
I think I’m going to try to start wrapping things up on MDE2.
Weekend was spent waiting for the java download site to come back up. (Compiling Flash/Flex requires Java, at least the way FlashDevelop does it.) It’s finally back up now, so I’ll hopefully be able to make some progress this week.
e: it builds!
Page 1 of 97