[A83] Re: statvars...??? [Ti83+]
[Prev][Next][Index][Thread]
[A83] Re: statvars...??? [Ti83+]
> Van: Kirk Meyer <kirk.meyer@colorado.edu>
>
> For a tilemaped game, for example, grayscale is better accomplished by
> drawing the tilemap for the next frame while you're waiting for the
current
> frame to finish drawing. Consult Hideaki's routine. To this end, a much
> better way of doing grayscale in this case would be to call the
tilemaping
> routine twice, once for each plane. Doing grayscale in the interrupt can
> slow it down quite a bit -- for some programs such as puzzle games, this
> doesn't matter quite so much, but for action games, this can be a major
> drawback. It was more of a comment than something you can fix in a C
> compiler, since having efficient grayscale would require different asm
for
> different things.
(I couldn't find the routine on my PC, and hadn't time to go into the
internet...)
So this tilemaproutine, copies the previously generated screen to the LCD
while making a new one? Must have been some trouble to make...
You also needed to make use of a tilemaped game/program to make this work
off course...
Okay we do have spriteroutines, but they are variable width/height
spriteroutines (tilemaps need fixed sized sprites). And the other graphics
routines are ones to draw circles, fill parts of the screen, etc. Not
really things where a tilemap-routine would be handy...
It can be something to think off for putting into the compilers-library
(but not for greyscale I'm afraid).
Henk Poley
Follow-Ups: