https://bugs.freedesktop.org/show_bug.cgi?id=72895
Priority: medium Bug ID: 72895 Assignee: dri-devel@lists.freedesktop.org Summary: Missing trees in flightgear 2.12.1 with r600 driver and mesa 10.0.1 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: mister.freeman@laposte.net Hardware: All Status: NEW Version: unspecified Component: Drivers/Gallium/r600 Product: Mesa
Created attachment 91014 --> https://bugs.freedesktop.org/attachment.cgi?id=91014&action=edit glxinfo output
I have a radeon HD4650 PCIe running in archlinux 64 bits OS,
I use the r600 driver,
OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD RV730 OpenGL core profile version string: 3.1 (Core Profile) Mesa 10.0.1 ( you can fin full gxinfo output in the attachement with this message )
Since I upgrade to Mesa 10.0.1 I notice missing trees in flightgear 2.12.1,
on startup I can see trees, vegetations, but if I maximize the windows or if I start the engine or move the plane the trees disappear,
it's a weird bug because sometimes the trees appear again when moving the plane or using a different point of view ( tower, outside the plane ), but instantly these trees disappear again when I return in the cockpit of the plane,
see the attachements with this mail ( 2 screenshots, one with the trees displayed, and one when the bug occurs, no trees ),
I think it's a bug from mesa 10.0.1 because with mesa 9.2.5 I don't have this bug
https://bugs.freedesktop.org/show_bug.cgi?id=72895
--- Comment #1 from Barto mister.freeman@laposte.net --- Created attachment 91015 --> https://bugs.freedesktop.org/attachment.cgi?id=91015&action=edit trees are displayed normally in flightgear 2.12.1
trees are displayed normally in flightgear 2.12.1 at startup
https://bugs.freedesktop.org/show_bug.cgi?id=72895
--- Comment #2 from Barto mister.freeman@laposte.net --- Created attachment 91016 --> https://bugs.freedesktop.org/attachment.cgi?id=91016&action=edit trees disappear in flightgear 2.12.1 after starting the engine
trees disappear in flightgear 2.12.1 after starting the engine or moving the plane or changing the point of view
https://bugs.freedesktop.org/show_bug.cgi?id=72895
--- Comment #3 from Michel Dänzer michel@daenzer.net --- Can you bisect?
https://bugs.freedesktop.org/show_bug.cgi?id=72895
--- Comment #4 from Barto mister.freeman@laposte.net --- I don't know how to do a bissect, but I will try
https://bugs.freedesktop.org/show_bug.cgi?id=72895
--- Comment #5 from Barto mister.freeman@laposte.net --- I did a bisect with git,
and the culprit seems to be :
59b01ca252bd6706f08cd80a864819d71dfe741c is the first bad commit commit 59b01ca252bd6706f08cd80a864819d71dfe741c Author: Fredrik Höglund fredrik@kde.org Date: Tue Apr 9 20:54:25 2013 +0200
mesa: Add ARB_vertex_attrib_binding
update_array() and update_array_format() are changed to update the new attrib and binding states, and the client arrays become derived state.
Reviewed-by: Eric Anholt eric@anholt.net
:040000 040000 e1270491ec1e0f8a98f930a0cf959038a56c4449 d2f6ee337ecbf36f764921474f2c69a67308eafa M src
you can fin the git log for the bisect in attachment with this message,
the bisect wad doing by setting the first good bissect with the revision 9.2.5 of mesa and the bad bissect with the HEAD revision of mesa mastering ( last revision on git ),
I hope we have enough clues to fix this bug
https://bugs.freedesktop.org/show_bug.cgi?id=72895
--- Comment #6 from Barto mister.freeman@laposte.net --- Created attachment 91114 --> https://bugs.freedesktop.org/attachment.cgi?id=91114&action=edit git bisect log
the git bisect log,
# first bad commit: [59b01ca252bd6706f08cd80a864819d71dfe741c] mesa: Add ARB_vertex_attrib_binding
https://bugs.freedesktop.org/show_bug.cgi?id=72895
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Assignee|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop. |.org |org CC| |fredrik@kde.org Component|Drivers/Gallium/r600 |Mesa core
dri-devel@lists.freedesktop.org