Martin Spott writes: > I'm running FlightGear on an SGI Octane MXI (supplied with the recommended > texture cache RAM, so called TRAM). Besides, this machine employs a cross > bar switch to connect CPU, RAM and display (which provides a theoretical > bandwidth of 1.6 GByte/sec) and has two parallel rendering pipelines/engines > so I expect this machine to be 'pretty fast' (TM) at rendering a whole > scene. This can be demonstrated with several demos (SGI and 3rd party). > > Unfortunately this machine is still quite slow at FlightGear (even without > using textures) - I believe this is caused by the slow CPU (195 MHz only). > So if you say that the FDM only takes a few cycles the conclusion would be, > that processing the scene graph takes most of the time,
If you do a profiling run of FlightGear, you will see that ssgCullAndDraw() takes a big chunk of the CPU as well as the terrain intersection. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
