[Flightgear-devel] Accepted flightgear 0.9.9-1 (source i386) (fwd)

2006-01-03 Thread Vassilii Khachaturov
Ho ho ho! Debian package for 0.9.9 is out! (Thanks go to Ove Kaaven). Happy New Year everyone! Vassilii -- Forwarded message -- Date: Tue, 03 Jan 2006 14:32:53 -0800 From: Ove Kaaven <[EMAIL PROTECTED]> To: debian-devel-changes@lists.debian.org Subject: Accepted flightgear 0.9.9-1

Re: [Flightgear-devel] FGv099 won't start under win98me

2006-01-03 Thread dene maxwell
Hi Fred, I think I mentioned that this "prefs" relates to the last time a ran FG this happened to be fgv098a (successfully) NOT fgv099 (crashes) I will run FG099 when I get a chance and send you the FR099 "prefs" file. This does raise the issue though of both versions using the same "prefs" f

Re: [Flightgear-devel] Code/Model Optimization

2006-01-03 Thread Ampere K. Hardraade
On January 3, 2006 04:13 pm, Paul Surgeon wrote: > With regards to MP aircraft : > We need the default aircraft to have a decent pyramid of LOD models as well > texture pyramids. There's no point in loading high resolution textures for > MP aircraft that are barely within visual range. This is a go

Re: [Flightgear-devel] Patch for Nasal flaps, gear, Vne, airframe stress warnings

2006-01-03 Thread Karsten Krispin
Am Mittwoch, 4. Januar 2006 01:12 schrieb Ampere K. Hardraade: > That can be shortened to displayMsg(). > > How about screenPrint() ? > Sound even better... that also exactly what I would expect from this function. print as C or Perls Print some text, but do that into the FG-Screen/Window.. :)

Re: [Flightgear-devel] Patch for Nasal flaps, gear, Vne, airframe stress warnings

2006-01-03 Thread Ampere K. Hardraade
On January 3, 2006 06:38 pm, Karsten Krispin wrote: > Am Mittwoch, 4. Januar 2006 00:05 schrieb Curtis L. Olson: > > popup() > > dialog() > > Both do not express the propery function they have. From a dialog-function > I expect to get a dialog and from a popup-function something that pop ups. > ;)

Re: [Flightgear-devel] Patch for Nasal flaps, gear, Vne, airframe stress warnings

2006-01-03 Thread Karsten Krispin
Am Mittwoch, 4. Januar 2006 00:05 schrieb Curtis L. Olson: > popup() > dialog() Both do not express the propery function they have. From a dialog-function I expect to get a dialog and from a popup-function something that pop ups. ;) - silly.. but true. :) displayMessage() would be rather ok. K

Re: [Flightgear-devel] Patch for Nasal flaps, gear, Vne, airframe stress warnings

2006-01-03 Thread Curtis L. Olson
Buchanan, Stuart wrote: I was originally going to replicate all the ATCDisplay functions within Nasal, hence the long name. However, in the end I only created a single interface. As Curt say, people expect print() to print to the console. What about displayMessage() ? popup() dialog() ?

Re: [Flightgear-devel] Patch for Nasal flaps, gear, Vne, airframe stress warnings

2006-01-03 Thread Buchanan, Stuart
--- Andy Ross <> wrote: > Stuart Buchanan wrote: > > - Provide a Nasal interface to display simple text messages on the > > screen like the ATC display. In fact, I copied the code from the > > ATCDisplay.cxx and simply shifted it further down the screen. > > > > The Nasal interface to display mess

Re: [Flightgear-devel] FGv099 won't start under win98me

2006-01-03 Thread Frederic Bouvier
Dene, See my recommendations below : dene maxwell wrote : ; FLTK preferences file format 1.0 ; vendor: flightgear.org ; application: fgrun [.] fg_exe:C:/Program Files/FlightGear098/bin/Win32/fgfs.exe fg_root:C:/Program Files/FlightGear098/data fg_scenery:C:/Program Files/FlightGear098/data/S

Re: [Flightgear-devel] Code/Model Optimization

2006-01-03 Thread Dave Culp
On Tuesday 03 January 2006 03:13 pm, Paul Surgeon wrote: > With regards to MP aircraft : > ... > We can either make all the FG aircraft comply or we need to make some sort > of separate MP aircraft package like MSFS guys do (example Project AI). I like that idea, but would it be easier if modelers

Re: [Flightgear-devel] Patch for Nasal flaps, gear, Vne, airframe stress warnings

2006-01-03 Thread Curtis L. Olson
Andy Ross wrote: This is really cool, but I'm not a big fan of long function names for simple, global actions. How about we call this thing "print()" and rename the existing print() function (which dumps to the console) log() instead? Almost everyone would prefer this to be the default text ou

Re: [Flightgear-devel] Code/Model Optimization

2006-01-03 Thread Paul Surgeon
On Tuesday 03 January 2006 22:04, Ben Clark wrote: > Hey There > > Although i have a fairly moderate spec machine i've noticed that FG frame > rate can be extremely low, particually when near the carrier, or when > playing multiplayer. Many people have told me this is due to the sever > complexity

Re: [Flightgear-devel] Patch for Nasal flaps, gear, Vne, airframe stress warnings

2006-01-03 Thread Andy Ross
Stuart Buchanan wrote: > - Provide a Nasal interface to display simple text messages on the > screen like the ATC display. In fact, I copied the code from the > ATCDisplay.cxx and simply shifted it further down the screen. > > The Nasal interface to display messages can be called simply as follows:

Re: [Flightgear-devel] Re: New FlightGear mousepad

2006-01-03 Thread Arnt Karlsen
On Tue, 3 Jan 2006 15:37:40 +1100, Pigeon wrote in message <[EMAIL PROTECTED]>: > > and created a design that shows what FlightGear is capable of today: > > http://www.a1.nl/~ehofman/fgfs/gallery/fgfs-mousepad2006.jpg > > Nice! > > Just a personal thing, i always prefer with a trailing

[Flightgear-devel] Code/Model Optimization

2006-01-03 Thread Ben Clark
Hey ThereAlthough i have a fairly moderate spec machine i've noticed that FG frame rate can be extremely low, particually when near the carrier, or when playing multiplayer. Many people have told me this is due to the sever complexity of the models. My question is, does anyone know the most severe

Re: [Flightgear-devel] Nasal/IRIX bug, fixed.

2006-01-03 Thread Mathias Fröhlich
Hi, On Tuesday 03 January 2006 18:17, Erik Hofman wrote: > Aha, that might well be the problem then. > It would be a good idea to solve this for all platforms (even untested > ones) then. Your proposed fix to use a function instead of a macro seems to fix that. The evaluation order is forced to o

Re: [Flightgear-devel] Nasal/IRIX bug, fixed.

2006-01-03 Thread Erik Hofman
Mathias Fröhlich wrote: I am not sure, but for the first thing, the lines around 427 look suspicious to me. They also reference opTop from the ctx variable which is modified by the macro. I believe that the order of the increment and the assignent of the array is undefined in this macro expansi

Re: [Flightgear-devel] Patch for Nasal flaps, gear, Vne, airframe stress warnings

2006-01-03 Thread Buchanan, Stuart
--- Martin Spott <> wrote: > "Buchanan, Stuart" wrote: > > > - Provide generic Nasal code to check if a pilot is abusing their > aircraft > > by extending their gear/flaps above the maximum allowed speed, > exceeding > > Vne, or pulling excessive G-forces. > > - Implement limits within the C182.

Re: [Flightgear-devel] Nasal/IRIX bug, fixed.

2006-01-03 Thread Mathias Fröhlich
Hi Erik, On Monday 02 January 2006 14:53, Erik Hofman wrote: > # define PUSH(r) do { \ > if(ctx->opTop >= MAX_STACK_DEPTH) ERR(ctx, "stack overflow"); \ > ctx->opStack[ctx->opTop++] = r; \ > } while(0) [...] > The only thing I can think of right now is that inside the function the

Re: [Flightgear-devel] pa24-25 (Piper Comanche) 3d model ready to apply textures-help

2006-01-03 Thread Christian Mayer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Erik Hofman schrieb: > Dave Perry wrote: > >> What tool do I use to associate the .jpg with the 3d object? >> Thanks in advance for the help. > > > Steve Baker (the chief development of plib) refuses to add support for > JPEg textures (and probably

Re: [Flightgear-devel] Calling FG functions via network interface

2006-01-03 Thread Martin Spott
Paul Surgeon wrote: > Python rocks (most of the time). :) > > However you'll need to add GUI library on top of Python since as far as I > know > it doesn't have a "built in one" like VB, Visual C++, Delphi, etc. > Maybe Qt with the Python Qt bindings or something along those lines. There is P

Re: [Flightgear-devel] Patch for Nasal flaps, gear, Vne, airframe stress warnings

2006-01-03 Thread Martin Spott
"Buchanan, Stuart" wrote: > - Provide generic Nasal code to check if a pilot is abusing their aircraft > by extending their gear/flaps above the maximum allowed speed, exceeding > Vne, or pulling excessive G-forces. > - Implement limits within the C182. Does anyone have the necessary experience w

Re: [Flightgear-devel] Patch for Nasal flaps, gear, Vne, airframe stress warnings

2006-01-03 Thread Buchanan, Stuart
--- "Ampere K. Hardraade" <> wrote: > On January 2, 2006 06:21 pm, Buchanan, Stuart wrote: > > - Provide a Nasal interface to display simple text messages on the > screen > > like the ATC display. In fact, I copied the code from the > ATCDisplay.cxx > > and simply shifted it further down the scree

Re: [Flightgear-devel] Calling FG functions via network interface

2006-01-03 Thread Thomas Förster
Am Dienstag 03 Januar 2006 00:22 schrieb Paul Surgeon: > On Tuesday 03 January 2006 00:38, [EMAIL PROTECTED] wrote: > > I'd just follow this up by putting in a plug for Python. An advantage > > of Perl/Python/Java/etc. is that they're cross-platform, as Martin > > said. Another is that unless you