Re: [Flightgear-devel] optimisation of FlightGear code

2005-07-05 Thread Paul Kahler
Based on several months of following this list I would guess that most of the CPU time in FGFS is spent in rendering the scenery. Just look at the recent reports of frame rate dropping with the addition of 3d clouds. Or perhaps people are limited by the graphics hardware? It sounds like the FDM

Re: [Flightgear-devel] optimisation of FlightGear code

2005-07-05 Thread Andy Ross
Jim Campbell wrote: Hopefully I would like to start a discussion of Flightgear code optimisation. OK. The most important point to remember is that FlightGear is generally not CPU bound at all. It spends the vast majority of its time sending primitives to the hardware to be rendered, and then

[Flightgear-devel] optimisation of FlightGear code

2005-07-04 Thread Jim Campbell
Hi folks, Hopefully I would like to start a discussion of Flightgear code optimisation. My first thoughts are that fgfs divides logically into a number of sub-systems: a) Flight Dynamics Modelling (FDM) b) Exterior View c) Cockpit input and output ie joystick controls,switches and displays. d)