On Tue, 19 Apr 2011 04:13:45 +0200, Robert wrote in message
banlktim5dkxvgxyh5owvjwrcv23odt6...@mail.gmail.com:
I also have the flickering issue with shaders on.
..white flickering?
(ATI/AMD,
..which ATI/AMD?
Debian,
..which Debian, Squeeze?
fglrx)
..url to screenshots?
..try the
On Mon, 2011-04-18 at 16:14 +0200, Csaba Halász wrote:
On Mon, Apr 18, 2011 at 1:38 PM, Christian Schmitt ch...@ilovelinux.de
wrote:
Csaba Halász wrote:
Info registers, and something like x/10i $eip (or $rip on 64 bit)
Here you go (still on Atom), Phenom this evening.
(gdb) info
On Tue, Apr 19, 2011 at 9:13 AM, Geoff McLane ubu...@geoffair.info wrote:
Quite some time ago now ran into this NULL ptr
passed to the merge_left() (internal) gpc library
function, when trying to process dense (very detailed)
data, but even after adding code 'protecting' against
such a
On Tue, 2011-04-19 at 09:29 -0500, Curtis Olson wrote:
[]
Yup, this is definitely a problem. In order to keep file sizes down,
the index into the vertex, normal, and texture coordinate lists is a
short ... it might even be a signed short.
[]
Tradeoffs ... if we switch from short to int, we
here is a screenshot:
http://img251.imageshack.us/i/fgfsscreen077.png/
If you ask me it looks pretty much like z-fighting artefacts.
Maybe a shader that doesnt account for near and far frustum?
--
Benefiting from Server
I had to fly pretty low to cause this flickering.
Also there is a flickering problem with panel instruments and cockpit
itself, But in about 300 screenshots I couldn't catch this issue because it
lasts only a few frames and I don't have the reaction time of a machine :)
I think a video would be
6 matches
Mail list logo
