[Flightgear-devel] Changelog for Release 2.8.0

2012-08-13 Thread Torsten Dreyer
Hi everybody, we are very close to our release date, just a few days left until we hopefully ship our latest-and-greates-ever FlightGear version. Please check the changelog at http://wiki.flightgear.org/Changelog_2.8.0 and make sure every new feature is noted at a prominent place there. These

Re: [Flightgear-devel] Memory issues

2012-08-13 Thread James Turner
On 11 Aug 2012, at 18:21, Tim Moore wrote: > This is what osg::PagedLOD does, though we often forget that the > paging of the higher LODs is triggered in the cull phase. >> I can't recall what scene modifications are / are not permitted inside a >> cull-callbacl, however. > You would want to let

[Flightgear-devel] MSVC build slave..

2012-08-13 Thread geneb
...is back online! Many thanks to Curt for donating a replacment drive! g. -- Proud owner of F-15C 80-0007 http://www.f15sim.com - The only one of its kind. http://www.diy-cockpits.org/coll - Go Collimated or Go Home. Some people collect things for a hobby. Geeks collect hobbies. ScarletDME

Re: [Flightgear-devel] FlightGear Usability

2012-08-13 Thread Martin Spott
James Turner wrote: > On 12 Aug 2012, at 20:44, Martin Spott wrote: > >>> But it's not an either/or. There could be an FGCom binary that uses the >>> same >>> code as the built-in FGCom. >> >> Which environment would be set up to build this separate binary ? > > The fgfs one, but I don't think

Re: [Flightgear-devel] FlightGear Usability

2012-08-13 Thread Stuart Buchanan
On Sun, Aug 12, 2012 at 4:48 PM, James Turner wrote: > On 11 Aug 2012, at 22:52, Martin Spott wrote: >>> 3) Scenery. Terrasync is now built into FG, and we have nice UI to >>> configure it in-sim. However, it still requires users to set up a >>> separate directory and configure FG_SCENERY before

Re: [Flightgear-devel] FlightGear Usability

2012-08-13 Thread James Turner
On 12 Aug 2012, at 20:44, Martin Spott wrote: >> But it's not an either/or. There could be an FGCom binary that uses the same >> code as the built-in FGCom. > > Which environment would be set up to build this separate binary ? The fgfs one, but I don't think that's a particularly onerous requi