[A83] Re: statvars...??? [Ti83+]
[Prev][Next][Index][Thread]
[A83] Re: statvars...??? [Ti83+]
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.
-----Original Message-----
From: assembly-83-bounce@lists.ticalc.org
[mailto:assembly-83-bounce@lists.ticalc.org]On Behalf Of Henk Poley
Sent: Friday, July 06, 2001 12:48 PM
To: assembly-83@lists.ticalc.org
Subject: [A83] Re: statvars...??? [Ti83+]
> Van: Kirk Meyer <kirk.meyer@colorado.edu>
>
> I think that perhaps he has problems with both but hasn't quite noticed
it
> yet.
Please, whats wrong? Couldn't you wait till I answered you?
> I have to wonder if an interrupt is the best way do grayscale on an 83.
But
> I'll leave that up to you. Obviously it would have to be that way in a C
> program where the grayscale couldn't be tailored to the specific
situation.
How on earth would you then like it to do? Write a program that outputs so
much data to the LCD-driver that it looks like greyscale? Has been done on
the GameBoy color to boost up the colours to be able to display around
65000 colours when displaying short movies/intros. That option is quite...
ehm.. BIG.. (talking about big C compiled programs...)
Henk Poley
References: