futz
Active Member
Quoting myself:
But why?
I finally gave up and took a look at your code and saw that you were reading twice to get proper result. Why is that dummy read necessary? I put the 2nd read in my code and it fixed the bogus reads I was getting.I'm just debugging my rasterizer for the display. I'm getting unexpected and just plain wrong results from my display data reads, which of course scrambles what I write to the screen, as I read first and then OR my new pixel into that byte and write it back out. Much confusion and debugger time ensues.
But why?