On Friday 25 February 2005 06:23, Nicolai Haehnle wrote: > On Thursday 24 February 2005 23:57, Daniel Phillips wrote: > > WritePixels has to go through the pipeline in many cases anyway, so > > this isn't a problem. We only have to worry about reads and raw > > writes. The easy solution is to flush the whole pipeline, just for the > > case of a raw blit to or from the framebuffer, don't you think? > > Otherwise, we could keep track of the bounds of the current trapezoid > > and avoid flushing in most cases, but that is a lot more work. > > Flushing the whole pipeline isn't enough when there are independent read > caches involved. Consider the following scenario: > 1) We render some textured polygons. > 2) The texture is updated (using TexSubImage or something) which results > in a DMA upload. > 3) We render some more textured polygons using the same texture. > > You are likely to get artifacts (i.e. rendering using the old instead of > the new texture) if you don't invalidate the read caches.
Of course I intended "flushing the pipeline" to include clearing the texture cache, since this is only used by the pipeline. Regards, Daniel _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
