On Wed, 23 Jul 2008, Erik Hofman wrote: >> Ordering transparencies is handled automatically, which can lead to >> unexpected problems - I had to break the Seahawk canopy into many separate >> objects to ensure that objects inside were visible, but otherwise it usually >> works well. > > Odd, I keep getting that the non-transparent sections of the texture get > transparent within FlightGear (creating a hole in the fuselage).
Hi, If I have understood the transparency issues correctly, semi-transparent objects are one source of ordering problems. You could consider/try separating the transparent and the opaque parts into separate objects. The work on FG/OSG has lead to major architectural improvements behind the scenes, e.g. having all model loading moved off the main thread. The use of the OSG data base pager has also considerably reduced the memory footprint of FlightGear on my box. Cheers, Anders -- --------------------------------------------------------------------------- Anders Gidenstam WWW: http://www.gidenstam.org/FlightGear/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
