[pkg-fgfs-crew] Bug#611685: Bug#611685: Bug#611685: flightgear: ..will not --enable-fullscreen, main thread eats a full cpu core, childs are politely waiting, FG whines about bad drawables.

[Ove Kaaven]

Den 02. feb. 2011 14:09, skrev Arnt Karlsen:
> On Tue, 01 Feb 2011 23:11:15 +0100, Ove wrote in message 
> <4D488503.8000901 at arcticnet.no>:
> 
>> Do you have any kind of evidence that any of this is actually
>> FlightGear's fault?
> 
> ..none other than seing this (appear to) appear on upgrading FG to
> 2.0.0-2 (from 1.9.1.1 which was ok on the same bleeding edge radeon
> driver,) and seeing some (accidental?) improvement in FG-git and 
> FG-2.0.0-3. 

Well, 2.0.0-3 should not be different from 2.0.0-2. It was a Debian
packaging update, with absolutely no code changes involved (other than
of course a recompile in order to build the new package). So any
differences there would be purely coincidental.

But the difference between 1.9 and 2.0 would be big, of course, with the
introduction of a new 3D visual effect system that would use GLSL
shaders much more than before. If you see strange effects in FG 2.0 that
you did not see in FG 1.9, it probably means that there are problems
with GLSL, which you don't see in FG 1.9 because FG 1.9 did not use GLSL.

The messages on your console are clearly GLSL-related (generic input
attributes are GLSL-specific, and FS would mean Fragment Shader). They
would definitely cause rendering issues.

> ..I see none of this nonsensical camouflage pattern animation
> in any other program, that lead me to believe this is a FG bug.

If the problem do not show up on other systems, with more stable
drivers, it is probably a driver bug, not a FG bug. Does it?

Also, if FG was doing something wrong and the driver was fine, the
result would probably have been a unicolor wing, not a random-pattern
one. (OpenGL specify that in the case of *any* error, the affected unit
is disabled. In other words, if the GLSL program was invalid or could
not be used, OpenGL should disable shading. That would, presumably,
result in an untextured wing.)

> ..always possible, how do I check?

I'm not sure. Try the #dri or #dri-devel channels on irc.freenode.net,
maybe.