I managed to get the vtxfmt path enabled and fixed a small problem that
didn't show up when vtxfmt wasn't enabled. Flightgear performance
increased only marginally since it draws most of its geometry using
vertex arrays which is a vtxfmt fallback. I was able improve the
situation by not installing
On Wed, 31 Dec 2003 00:00:17 +0100
Jacek Pop <[EMAIL PROTECTED]> wrote:
> On Tue, Dec 30, 2003 at 09:38:21PM +0100, Felix Kühling wrote:
> > And I found out that apperently the entire vtxfmt code path is not working.
>
> Was it working before "newmesa"?
I'm not sure. Looking at an old config-0-
On Tue, Dec 30, 2003 at 09:38:21PM +0100, Felix Kühling wrote:
> And I found out that apperently the entire vtxfmt code path is not working.
Was it working before "newmesa"?
--
Free Software - find interesting programs and change them
NetHack - meet interesting creatures, kill them and eat thei
Hi,
I was wondering why flightgear was so slow so I did some profiling and
debugging. And I found out that apperently the entire vtxfmt code path
is not working. I believe the root cause is that radeonNotifyBegin is
never called with current Mesa. So the driver's own vtxfmt functions are
never ins
