... radio telephony procedures, such as readbacks, minimises the opportunity for misinterpretation ... or non-standard phraseology in readbacks on the surface movement control ... excess or nonstandard words in readbacks and its effect on frequency...most users complied with the readback requirements stipulated in the Aeronautical...of compliance with the AIP readback requirements; however, it was noted...

...those kinds of transfers. So go ahead and use StretchRect to do a video-video scaling operation. Do all your intermediate/scaling work in video memory, but just do one final readback using GetRenderTargetData. And you're better off doing all the pieces grouped (atlased?) together on one render target, then reading them all back together in a single GetRenderTargetData call, then...

> I'm telling you that you can't do read-modify-write in a shader where the target of the write is the same surface as the source of the read. Ok. I did pose a two part question though. Thanks for the confirmation about me not being able to do readback. Always good to know that something is actually not possible. It makes a hack solution feel more reasonable.

...new color. That is simple enough to comprehend, but it requires a read of the current backbuffer. Can the same thing be done in a shader? As far as I can see, there are no way to do a readback of the current backbuffer value. One could render to texture and swap two textures for each geometry object. Render to A, set A as lookup texture, render to B, set B as lookup etc. I assume this ...

Oops, that follow-up doesn't feel right on readback! I must be pissed :-) Guilt is often unnecessary. :-/

.../File-ShareDir-0.05-JomPak/blib/lib:/usr/local/src/CPAN/build/File-Rename-0.05-g9itVr/blib/arch:/usr/local/src/CPAN/build/File-Rename-0.05-g9itVr/blib/lib:/usr/local/src/CPAN/build/File-ReadBack! wards-1. 04-fDr8Pu/blib/arch:/usr/local/src/CPAN/build/File-ReadBackwards-1.04-fDr8Pu/blib/lib:/usr/local/src/CPAN/build/Image-ExifTool-7.00-gnDiJl/blib/arch:/usr/local/src/CPAN/build/Image-ExifTool-7....

.../File-Slurp-9999.12-DT9L5H/blib/lib:/usr/local/src/CPAN/build/File-Remove-0.37-9tZm5J/blib/arch:/usr/local/src/CPAN/build/File-Remove-0.37-9tZm5J/blib/lib:/usr/local/src/CPAN/build/File-ReadBack! wards-1. 04-Es7By8/blib/arch:/usr/local/src/CPAN/build/File-ReadBackwards-1.04-Es7By8/blib/lib:/usr/local/src/CPAN/build/Image-ExifTool-6.90-kCKmiP/blib/arch:/usr/local/src/CPAN/build/Image-ExifTool-6....

.../File-Slurp-9999.12-DT9L5H/blib/lib:/usr/local/src/CPAN/build/File-Remove-0.37-9tZm5J/blib/arch:/usr/local/src/CPAN/build/File-Remove-0.37-9tZm5J/blib/lib:/usr/local/src/CPAN/build/File-ReadBack! wards-1. 04-Es7By8/blib/arch:/usr/local/src/CPAN/build/File-ReadBackwards-1.04-Es7By8/blib/lib:/usr/local/src/CPAN/build/Image-ExifTool-6.90-kCKmiP/blib/arch:/usr/local/src/CPAN/build/Image-ExifTool-6....

... that is the entire purpose of Lock, to synchronize access and guarantee data correctness. I intended to write into textures while reading the framebuffer. That should not be a problem? and in general, readback across the bus is on the order of 10x slower than write. Oh.. I thought that was not as big an issue with pci-e as with agp? It's much faster but it is ...

...writing at the same time is not a good idea. that is the entire purpose of Lock, to synchronize access and guarantee data correctness. I intended to write into textures while reading the framebuffer. That should not be a problem? and in general, readback across the bus is on the order of 10x slower than write. Oh.. I thought that was not as big an issue with pci-e as with agp?