<div dir="ltr"><div>I've managed to capture a trace that loads TF2 to the menu and reproduces some of the flickering. I haven't managed to capture any gameplay yet due to an error in CD Key authentication due to how I'm launching the game. URL: <a href="http://www.watrys.net/tf2_menu.trace.xz">http://www.watrys.net/tf2_menu.trace.xz</a> </div>--Aaron <div><div class="gmail_extra"> <div class="gmail_quote">On Wed, Feb 20, 2013 at 1:33 PM, Marek Olšák <<a href="mailto:maraeo@gmail.com" target="_blank">maraeo@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Well, I really wonder why it doesn't work with TF2. We have a lot of piglit tests for DISCARD_RANGE (AKA INVALIDATE_RANGE in GL) and the copy-buffer functionality and they all pass. There are actually 3 different implementations of copy-buffer: streamout, CP DMA, and async DMA. It's highly unlikely that all 3 would be broken in the same way. Other apps like openra also draw their GUI while using DISCARD_RANGE to discard old data and there is no issue. I need an apitrace to debug this. I wouldn't like to disable DISCARD_RANGE just because of TF2, because everything else seems to be working without any issues and because the performance regression can turn out to be a show-stopper for some other apps. Marek <div class=""><div class="h5"> On Sun, Feb 17, 2013 at 6:25 PM, Andreas Boll <<a href="mailto:andreas.boll.dev@gmail.com">andreas.boll.dev@gmail.com</a>> wrote: > This reverts commit 1eedebc65b02130ef7a27062a1ed67972a317a08. > > Until we have a proper fix disable DISCARD_RANGE for now. > It fixes the garbled ui in TF2. > > Bugzilla: <a href="https://bugs.freedesktop.org/show_bug.cgi?id=58042" target="_blank">https://bugs.freedesktop.org/show_bug.cgi?id=58042</a> > > Cc: Marek Olšák <<a href="mailto:maraeo@gmail.com">maraeo@gmail.com</a>> > --- > src/gallium/drivers/r600/r600_buffer.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/src/gallium/drivers/r600/r600_buffer.c b/src/gallium/drivers/r600/r600_buffer.c > index 6df0d91..82630af 100644 > --- a/src/gallium/drivers/r600/r600_buffer.c > +++ b/src/gallium/drivers/r600/r600_buffer.c > @@ -137,6 +137,7 @@ static void *r600_buffer_transfer_map(struct pipe_context *ctx, > r600_set_constants_dirty_if_bound(rctx, rbuffer); > } > } > +#if 0 /* this is broken (see Bug 53130) */ > else if ((usage & PIPE_TRANSFER_DISCARD_RANGE) && > !(usage & PIPE_TRANSFER_UNSYNCHRONIZED) && > rctx->screen->has_streamout && > @@ -161,6 +162,7 @@ static void *r600_buffer_transfer_map(struct pipe_context *ctx, > } > } > } > +#endif > > /* mmap and synchronize with rings */ > data = r600_buffer_mmap_sync_with_rings(rctx, rbuffer, usage); > -- > 1.7.10.4 > _______________________________________________ mesa-dev mailing list <a href="mailto:mesa-dev@lists.freedesktop.org">mesa-dev@lists.freedesktop.org</a> <a href="http://lists.freedesktop.org/mailman/listinfo/mesa-dev" target="_blank">http://lists.freedesktop.org/mailman/listinfo/mesa-dev</a> </div></div></blockquote></div> </div></div></div>