Thomas Hellstrom writes:
> The reason it was CC'd stable was that it appeared to fix a rendering
> problem that we were seeing, but I should definitely have tested this
> more thoroughly. :(
No worries. It happens to all of us at times.
> An unfortunate situation but the sooner we could cut a 10
Carl,
Unfortunately a pretty bad problem made it into the XA state tracker in
10.1.2 with commit "Cache render target surface" and it was
just fixed in master with commit
9306b7c171b29ac99f837e9efcd0281caf1d332e. It makes vmware swapbuffers
fall back to software.
The reason it was CC'd stable was
