Hi!
I am on a Radeon RX 560 2GB; using mesa git-57c8ead0cd (So... not too new not
too old), Kernel 4.12.10
I've been having complaints about our WIP branch of Ogre 2.2 about out of
memory crashes, and I fixed them.
I made a stress test where 495 textures with very different resolutions (most
uestions, that this behavior I saw isn't exactly
"normal" or "expected" and I should dedicate some time to see if I can repro in
newer versions, and if possible create a small repro.
Thanks,
Cheers
Matias
____
De: Michel Dänzer
Para: Matias N.
bug may not
only affect Mesa.
I am asking for this patch to be reviewed for inclusion in Mesa.
Thanks
Matias
>From 3db888f8645acd5d41b689ee6522d465bcf71044 Mon Sep 17 00:00:00 2001
Message-Id:
<3db888f8645acd5d41b689ee6522d465bcf71044.1499274200.git.dark_syl...@yahoo.com.ar>
From: "
bug may not
only affect Mesa.
I am asking for this patch to be reviewed for inclusion in Mesa.
Thanks
Matias
>From 3db888f8645acd5d41b689ee6522d465bcf71044 Mon Sep 17 00:00:00 2001
Message-Id:
<3db888f8645acd5d41b689ee6522d465bcf71044.1499274200.git.dark_syl...@yahoo.com.ar>
From: "
I'm reviewing the patch and there's something that confuses me about
radeonsi_assume_no_z_fights (which got implemented in a later patch). It
appears to be that part of the logic is flawed.
Please correct me whenever you feel I misunderstood what is going on.
Assuming colour writes are enabled,
Hi!
I read your article.
What I feel are missing are just minor pesky details:
1. Written as is, the frame being submitted is rounded up to display timing,
delaying *future* frames.But there is no way to delay the *currently displaying
frame* (i.e. the 'previous' frame).
Right now if frame N wa
