Re: [Flightgear-devel] Slow frame rates

2012-06-20 Thread castle . 64
:18:35 PM Subject: Re: [Flightgear-devel] Slow frame rates Hi, On Sunday, June 17, 2012 13:00:15 castle...@comcast.net wrote: > This email rekindled an idea from a while back. Last year while working on > the 747 sim with multiple projectors and a quad core CPU I experimented > with

Re: [Flightgear-devel] Slow frame rates

2012-06-19 Thread Mathias Fröhlich
Hi, On Monday, June 18, 2012 13:20:17 castle...@comcast.net wrote: > The HLA/RTI architecture is far more sophisticated than what might be > needed. The idea is not to split FlightGear into a distributed, federated > application across a multi-platform machine or network although that is an > int

Re: [Flightgear-devel] Slow frame rates

2012-06-19 Thread Mathias Fröhlich
Hi, On Sunday, June 17, 2012 13:00:15 castle...@comcast.net wrote: > This email rekindled an idea from a while back. Last year while working on > the 747 sim with multiple projectors and a quad core CPU I experimented > with setting up three instances of fgfs - one for each cpu, graphics card, >

Re: [Flightgear-devel] Slow frame rates

2012-06-18 Thread castle . 64
Buchanan" To: " FlightGear developers discussions" Sent: Monday, June 18, 2012 7:46:35 AM Subject: Re: [Flightgear-devel] Slow frame rates Hi John, As the author of the 3D clouds system, and the OSG random buildings/objects re-implementation, this is obviously an area of inter

Re: [Flightgear-devel] Slow frame rates

2012-06-18 Thread Stuart Buchanan
Hi John, As the author of the 3D clouds system, and the OSG random buildings/objects re-implementation, this is obviously an area of interest to me :) Comments inline below. On Mon, Jun 18, 2012 at 2:20 PM, wrote: > By way of an example, consider the 3D cloud system. > > Given a three projector

Re: [Flightgear-devel] Slow frame rates

2012-06-18 Thread castle . 64
Sunday, June 17, 2012 7:18:47 AM Subject: Re: [Flightgear-devel] Slow frame rates castle...@comcast.net wrote: > Multi-core machines have been around for some time now. Perhaps it is > time to think beyond running Flighgear as a monolithic process in a > single CPU configuration. As a star

Re: [Flightgear-devel] Slow frame rates

2012-06-17 Thread Martin Spott
castle...@comcast.net wrote: > Multi-core machines have been around for some time now. Perhaps it is > time to think beyond running Flighgear as a monolithic process in a > single CPU configuration. As a start you may want to visit: http://www.mail-archive.com/flightgear-devel@lists.sourcefor

Re: [Flightgear-devel] Slow frame rates

2012-06-17 Thread castle . 64
e, the floor is open to anyone who would like to comment or pursue this idea on their own. Regards John W. - Original Message - From: "Catherine James" To: flightgear-devel@lists.sourceforge.net Sent: Friday, June 15, 2012 10:02:34 PM Subject: [Flightgear-devel] Slow f

Re: [Flightgear-devel] Slow frame rates, --model-hz effect

2012-06-16 Thread Arnt Karlsen
On Fri, 15 Jun 2012 20:47:02 -0700 (PDT), Catherine wrote in message <1339818422.43212.yahoomailclas...@web83907.mail.sp1.yahoo.com>: > Some years ago when I started flying FlightGear 2.0, I added > --model-hz=480 to my startup aliases for reasons I no longer > remember. ..you're running the fd

Re: [Flightgear-devel] Slow frame rates

2012-06-16 Thread Alan Teeder
:02 AM To: flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] Slow frame rates Additional finding: if you do a File --> Reset immediately after startup, the slow 1 - 2 fps problem goes away immediately and frame rates stay high thereafter. Something seems to be gett

[Flightgear-devel] Slow frame rates

2012-06-15 Thread Catherine James
Additional finding: if you do a File --> Reset immediately after startup, the slow 1 - 2 fps problem goes away immediately and frame rates stay high thereafter. Something seems to be getting initialized either when breaking ground during takeoff or in a File --> Reset that is not getting init

[Flightgear-devel] Slow frame rates, --model-hz effect

2012-06-15 Thread Catherine James
Some years ago when I started flying FlightGear 2.0, I added --model-hz=480 to my startup aliases for reasons I no longer remember. I've continued to use these aliases through 2.4 and 2.6 with no real ill effect. However, on a git build from June 13 I've noticed that using them really clobbers