Re: [Flightgear-devel] Replacement fpr mpserver01.flightgear.org

2010-04-08 Thread Oliver Schroeder
Hi Matt, According to pigeon mpserver02 uses about 10-15 GByte per day. Regards, Oliver On Wednesday 07 April 2010 12:52:16 Mattt wrote: Oliver, To assist with my ambition for laziness, can you give me a round figure for monthly bandwidth? I may be able to assist - note, however,

Re: [Flightgear-devel] Normal map shader example - c172p

2010-04-08 Thread Frederic Bouvier
Hi Stuart, - Stuart Buchanan a écrit : Hi All, I've just updated the c172p to make use of the bumpspec Effect for a bump-map. I've still to get the rivet separation right, but the effect so far is rather pleasing: http://www.nanjika.co.uk/flightgear/fgfs-screen-004.png Glad to see

Re: [Flightgear-devel] Replacement fpr mpserver01.flightgear.org

2010-04-08 Thread Mattt
Oliver, Ouch... But I thought so... The requisite bandwidth would cost a substantial amount for me :-( Oliver Schroeder wrote: Hi Matt, According to pigeon mpserver02 uses about 10-15 GByte per day. Regards, Oliver On Wednesday 07 April 2010 12:52:16 Mattt wrote: Oliver, To

Re: [Flightgear-devel] Normal map shader example - c172p

2010-04-08 Thread Torsten Dreyer
Hi All, I've just updated the c172p to make use of the bumpspec Effect for a bump-map. I've still to get the rivet separation right, but the effect so far is rather pleasing: http://www.nanjika.co.uk/flightgear/fgfs-screen-004.png Like most of the other shader effects, this looks

Re: [Flightgear-devel] Replacement fpr mpserver01.flightgear.org

2010-04-08 Thread George Patterson
Hi Oliver, If mpserver02 is using 10-15 Gigabytes a day, do we know what data the other servers are using? I'm just wondering what percentage of the 10-15 gig is due to people being too lazy to connect to the most appropriate mpserver. If the above theory is correct, it would be a good reason

Re: [Flightgear-devel] Normal map shader example - c172p

2010-04-08 Thread Detlef Faber
Am Donnerstag, den 08.04.2010, 00:13 +0100 schrieb Stuart Buchanan: Hi All, I've just updated the c172p to make use of the bumpspec Effect for a bump-map. I've still to get the rivet separation right, but the effect so far is rather pleasing:

Re: [Flightgear-devel] mpmap ILS data

2010-04-08 Thread James Turner
On 8 Apr 2010, at 03:06, Peter Brown wrote: Perhaps this has been brought up before, but I see that the ILS beam data for each airport on the mpmap is derived from the runway alignment (as verified in taxidraw). This doesn't allow for magnetic deviation, and therefore all the course

Re: [Flightgear-devel] Normal map shader example - c172p

2010-04-08 Thread Erik Hofman
Detlef Faber wrote: The striking thing with using the shader is that it is now possible to have smaller image files for liveries as now only the colour is needed. Details can now be done in the shader. This reduces the lag while selecting different liveries. Good to know, I might want to

Re: [Flightgear-devel] Replacement fpr mpserver01.flightgear.org

2010-04-08 Thread Oliver Schröder
On Wednesday 07 April 2010 12:52:16 Mattt wrote: Oliver, To assist with my ambition for laziness, can you give me a round figure for monthly bandwidth? According to pigeon mpserver02 uses about 10-15 GByte per day. Regards, Oliver I may be able to assist - note, however, that my

Re: [Flightgear-devel] mpmap ILS data

2010-04-08 Thread David Megginson
On Wed, Apr 7, 2010 at 10:06 PM, Peter Brown smoothwater...@adelphia.net wrote: Perhaps this has been brought up before, but I see that the ILS beam data for each airport on the mpmap is derived from the runway alignment (as verified in taxidraw).  This doesn't allow for magnetic deviation,

Re: [Flightgear-devel] New Reflection Shader- Very Nice but....

2010-04-08 Thread Heiko Schulz
Hi Vivian, -objects with this shader are emissive when ambient- correction set higher than zero. That is indeed a bug. I have a fix, but I'm having difficulty in balancing out the blue in the ambient light. Hopefully I can upload it soon. Bugfix in cvs. The colour and light

Re: [Flightgear-devel] mpmap ILS data

2010-04-08 Thread Peter Brown
On Apr 8, 2010, at 8:08 AM, David Megginson wrote: On Wed, Apr 7, 2010 at 10:06 PM, Peter Brown smoothwater...@adelphia.net wrote: Perhaps this has been brought up before, but I see that the ILS beam data for each airport on the mpmap is derived from the runway alignment (as verified in

Re: [Flightgear-devel] mpmap ILS data

2010-04-08 Thread David Megginson
On Thu, Apr 8, 2010 at 11:32 AM, Peter Brown smoothwater...@adelphia.net wrote: David, yes, as I have as well.  The localizer for 33 as you listed above is on a 326 heading per the approach plate, but the mpmap shows ILS data as the runway heading in degrees - as if for users to use as the

Re: [Flightgear-devel] mpmap ILS data

2010-04-08 Thread Peter Brown
On Apr 8, 2010, at 1:29 PM, David Megginson wrote: On Thu, Apr 8, 2010 at 11:32 AM, Peter Brown smoothwater...@adelphia.net wrote: David, yes, as I have as well. The localizer for 33 as you listed above is on a 326 heading per the approach plate, but the mpmap shows ILS data as the

Re: [Flightgear-devel] mpmap ILS data

2010-04-08 Thread Martin Spott
Peter Brown wrote: I see. So that brings us back to magnetic vs true, as I was originally referring to. But, that's somewhat irrevelant as it _appears_ the mpmap is sourcing the data from the actual runway placement. or from the navaids. My opinion is there should be an data file

Re: [Flightgear-devel] mpmap ILS data

2010-04-08 Thread Martin Spott
Martin Spott wrote: BTW, feel free to use this service if your're looking for slightly more complete airfield data:

Re: [Flightgear-devel] mpmap ILS data

2010-04-08 Thread Peter Brown
On Apr 8, 2010, at 4:09 PM, Martin Spott wrote: Peter Brown wrote: I see. So that brings us back to magnetic vs true, as I was originally referring to. But, that's somewhat irrevelant as it _appears_ the mpmap is sourcing the data from the actual runway placement. or from the

Re: [Flightgear-devel] mpmap ILS data

2010-04-08 Thread David Megginson
On Thu, Apr 8, 2010 at 2:00 PM, Peter Brown smoothwater...@adelphia.net wrote: I see.  So that brings us back to magnetic vs true, as I was originally referring to.  But, that's somewhat irrevelant as it _appears_ the mpmap is sourcing the data from the actual runway placement.  My opinion

Re: [Flightgear-devel] mpmap ILS data

2010-04-08 Thread Peter Brown
On Apr 8, 2010, at 4:58 PM, David Megginson wrote: On Thu, Apr 8, 2010 at 2:00 PM, Peter Brown smoothwater...@adelphia.net wrote: I see. So that brings us back to magnetic vs true, as I was originally referring to. But, that's somewhat irrevelant as it _appears_ the mpmap is sourcing

Re: [Flightgear-devel] mpmap ILS data

2010-04-08 Thread Martin Spott
Peter Brown wrote: On Apr 8, 2010, at 4:09 PM, Martin Spott wrote: BTW, feel free to use this service if your're looking for slightly more complete airfield data:

Re: [Flightgear-devel] mpmap ILS data

2010-04-08 Thread Peter Brown
On Apr 8, 2010, at 5:23 PM, Martin Spott wrote: If you're in need of a human-readable one-shot database table dump, please let me know. Cheers, Martin. -- That'd be great, send it my way. Peter --

Re: [Flightgear-devel] Normal map shader example - c172p

2010-04-08 Thread Stuart Buchanan
Frederic Bouvier wrote: Glad to see the effect is used. I noticed the bump is reverted on one axis. In a previous thread, I wrote : I use the GIMP normal map plug-in to create my normal maps. Here are two example. A bump : http://frbouvi.free.fr/flightsim/gimp-normalmap-bump.png A hole :

[Flightgear-devel] Fwd: mpmap ILS approach data

2010-04-08 Thread Peter Brown
First email never arrived to the list Might be a question for Pigeon, rather than apt.dat or nav.dat Begin forwarded message: From: Peter Brown pe...@smoothwatersports.com Date: April 4, 2010 10:36:05 AM EDT To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net

Re: [Flightgear-devel] mpmap ILS data

2010-04-08 Thread John Denker
On 04/07/2010 07:06 PM, Peter Brown wrote: Perhaps this has been brought up before, but I see that the ILS beam data for each airport on the mpmap is derived from the runway alignment (as verified in taxidraw). That sounds like a problem. This doesn't allow for magnetic deviation, and