It really depends on the method you are using for the grayscale, as well as the interrupt frequency (ie. desolate).  The more often interrupts are triggering, the more often the screen is being blinked, so it will be less flickery, but that also means the game will be slower, because more of the processor's power is being devoted to the grayscale

I just learned interrupts yesterday, and can't wait to teach them ^_^

I'm not sure I would rebel, children can piss me off a ton sometimes.




j/k j/k  

Each basic command is interpreted into assembly, and almost all of them include the command 'Halt', which stops all cpu operation until an interrupt occurs, so the higher the interrupt frequency, the more often interrupts will trigger, and the less time you waste stuck on a halt command.  

Anyway, to get back on topic, what else ought to make it into the tutorials?  I need to learn about interrupts/grayscale, then I will try to make a very in-depth explanation of how to create grayscale.  Interrupts are a toughy (tuffy?) to learn, and I'm pretty sure teaching them won't be any easier, but I will do my best.  

If this is in ASM, it won't be a problem.  The main reason for the 83+'s lack of speed is interrupts.  In basic, interrupts must be running, and so these interrupts can slow down your game significantly.  However, there is a way to change the interrupt speed to a much faster pace, without any hardware modifications such as overclocking.  This is called interrupt speed, and is very similar to interrupt frequency (for those of you who have ever played desolate).  But now I'm just rambling.  The point of what I am saying, is that you could alter interrupt speed to allow you to run much faster, and possibly stream from USB at an acceptable rate.

PixelPainter is really good, it gives you a ton of options, such as whether you want to export the sprite in bin or hex, and whether you want a .z80 or a .inc file extension.


http://www.ticalc.org/archives/files/fileinfo/386/38615.html