* Sigh * - You don't understand what circumstances I was in when I was writing that post. I was in a hurry and had to go to school while I was writing that post. I go to school very early in the morning.
Then why didn't you simply write "Sorry I don't have time to explain it right now, I'm gonna add a more complete post later"? Your posts above show that you simply didn't plan to give the details, and you weren't expecting that someone could ask you about it.
It's like how you were to busy to talk to me on MSN when I offered to tell you these kind of things.
School and education comes first before grayscales.
No problem with that. Btw when you called me on MSN it was 2:00 AM here, and I had an exam at 8:00 AM. So indeed I was too busy at that time
![;)](/dot/public/style_emoticons/default/wink2.gif)
I guess you killed my topic. Look at the direction where this topic is heading towards now...
Oh, sorry. I guess you were just expecting more posts saying "Yeah kucalc you are the best!".
I was just looking for comments about grayscales on the fx-9860 since people want it really badly and we have been trying for about a year (and maybe even a pat on the back), not attacks!
"attacks"?
So for you, asking for details or explanations about your work is an attack huh
![:huh:](/dot/public/style_emoticons/default/huh.png)
Did I say any bad comment on your work?
But as I thought, you were just expecting for people to acclaim your work. This is just too childish.
Sorry guy, but things don't work that way. Don't think that when you succeed in doing something, people never ask you about the whereabouts of your work. The only people who just say "yeah! wonderful!" are the ones who have no idea about how it could be done. People with experience will allways start by saying "yes that's nice, but what about ...?". You better should get used to that
![;)](/dot/public/style_emoticons/default/wink2.gif)
(OK this one is an "attack". But it does not concern your program, only the way you act.)
Here's your "Devo EZ Muzak"
explanation of how the grayscale engine works:
1. Determine the two buffers
2. Initialize the engine by setting up the SH3 timer interrupts
3. Run through some program code (Timer is counting down in the background)
3a. If the SH3 timer has underflowed draw the buffer on deck directly to the screen. Place the next buffer on deck and set the timer again.
4. Go back to 3
OK this is a begin of explanations. But unfortunately there is absolutely nothing new here, because most grayscale systems that are based on timers work that way. I'd like you to give more precision... For example, you have 4 colors but only 2 buffers. So that mean that one of the two buffers appears more often than the other one. But in which proportion? 60%/40%? 66%/33% ?
Well, I tried using three buffers, look at the picture of my calculator above. But using three buffers would complicate programming for people who want to make some games. Having to keep track and drawing three separate buffers...
It would complicate programming for people who will write the graphic library using the 3 buffers, that's for sure. But making games with it is another thing
![;)](/dot/public/style_emoticons/default/wink2.gif)
Another problem is that it takes too much CPU resources as the CPU would be devoted to just drawing the buffers to the screen, unless maybe we use CPUSPEED... This kind of thing may be only good for displaying a bitmap.
This is a common problem with grayscales... That's why we should try to find some efficient way to reduce flickering without having to use some low values for the timer cycles.
We also have already eliminated flickering, it's already been done for a while now... The problem is a white line that pops up and fades. I've heard that the same problem occurs on the ClassPad. Do you want me to show you another picture?
I'm well aware of that fact. And the reason is that the update rate of the buffers isn't perfectly synchronized with the refresh rate of the screen... I guess it is the best that could be obtained with this method
Again I'm not trying to destroy your work (which is great, that's a fact). I'd like you to describe your work in a more professional way, that's all
![:)](/dot/public/style_emoticons/default/smile.png)
Remember, there aren't only gamers here, sometines there are some other programmers too
![;)](/dot/public/style_emoticons/default/wink2.gif)
Or maybe you are just anxious that someone else could "steal" your work for himself?
I'm available on MSN if you want to talk a little