#173756 - Thajocoth - Thu Apr 29, 2010 12:18 am
I've been coding fairly blind for a while now... I can't really find any way to get any sort of variable information or even debug output. I'm able to slowly work around this... But I'd be able to go a lot faster if I didn't have to do as much guesswork. Especially now that I'm working on some of the AI parts, like D* pathing...
Of the emulators I've been using, Ensata seems to be the only one that supports debug output. I've also been using DeSmuME for the graphics viewing and have tried to see what information I could get out of iDeaS & No$, which has been none.
In libnds, the link to "Console and Debug Printing" loads up a blank page, as do both of the links in the "Debugging" section. The Nitro command for debug output does not work (though, that's expected). So, how to I output to Ensata's debug window with devkitPro? Is there something I'm overlooking as far as variable tracking and the like go?
Last edited by Thajocoth on Thu Apr 29, 2010 9:13 pm; edited 1 time in total
Of the emulators I've been using, Ensata seems to be the only one that supports debug output. I've also been using DeSmuME for the graphics viewing and have tried to see what information I could get out of iDeaS & No$, which has been none.
In libnds, the link to "Console and Debug Printing" loads up a blank page, as do both of the links in the "Debugging" section. The Nitro command for debug output does not work (though, that's expected). So, how to I output to Ensata's debug window with devkitPro? Is there something I'm overlooking as far as variable tracking and the like go?
Last edited by Thajocoth on Thu Apr 29, 2010 9:13 pm; edited 1 time in total