From: Juergen Gotschlich (juergen.gotschlich++at++dlr.de)
Date: 11/03/2003 04:32:20
Hi Paolo,
I am one step further in isolating my pfconv problem. It makes
definitely a difference, if I run pfconv on my development system
(Indigo) or or on our Onyx. The same command running on the Onyx works
fine. Running on the Indigo gives exactly the same messages. No warnings
about unavailable filters, etc... But the resulting pfb file is
different, when I test it with perfly. My command is
pfconv -M pfb,2,1, infile outfile
So, the DWB-loader seems to be dependent of the graphic-hardware. But
that is nonsense for a development system.
regards, Jürgen
-----------------------------------------------
Hi Jürgen,
I cannot think of why pfconv would change your texture filter..
You could quickly try to convert your models to .pfa to see if
that makes any difference.
If you can send us a small terrain file in .dwb format, I will be
happy to take a closer look.
Thanks,
Regards,
Paolo
Juergen Gotschlich wrote:
> Hi performers,
>
> I ported all my terrain files from .dwb-format to .pfb with the pfconv
> utility. But now my .pfb-files don't use any mipmapping filter, as
> my .dwb-files do.
> So, I see a lot of flickering pixels in the far distance.
>
> Any idea why and how to solve ?
>
> thanks, Jürgen
-- ________________________________________________________________________Jürgen Gotschlich email: juergen.gotschlich++at++dlr.de __/|_ Phone: +49(531)295-3248/2778 /_/_/_/ Fax : +49(531)295-2640 |/ DLR
Deutsches Zentrum für Luft-und Raumfahrt | German Aerospace Center in der Helmholtz-Gemeinschaft | Institut für Flugsystemtechnik | Inst. of Flight Research Abt. Flugsimulation | Flight Simulation Dep. Lilienthalplatz 7 | Lilienthalplatz 7 D-38108 Braunschweig | D-38108 Braunschweig, Germany ________________________________________________________________________
This archive was generated by hypermail 2b29 : Mon Nov 03 2003 - 03:38:32 PST