[Flightgear-devel] FOV broken?

2006-01-28 Thread Josh Babcock
Just compiled the latest greatest, and FOV does not seem to change. x and X pop up the FOV dialog, but the view does not change ... Josh --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop!

[Flightgear-devel] Autopilot on default Cessna

2006-01-28 Thread Martin Spott
Hello, I just took the latest CVS for a ride, starting at EDWJ and heading to EDDW. To ease the job I tried to engage the autopilot via the menu - but the autopilot pull-down menue is inactive, the word Autopilot in the headline is greyed-out. Is this intentionally ? Cheers, Martin. --

Re: [Flightgear-devel] Autopilot on default Cessna

2006-01-28 Thread Martin Spott
Martin Spott wrote: I just took the latest CVS for a ride, using the default aircraft, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! --

[Flightgear-devel] Re: Autopilot on default Cessna

2006-01-28 Thread Melchior FRANZ
* Martin Spott -- Saturday 28 January 2006 16:35: but the autopilot pull-down menue is inactive, the word Autopilot in the headline is greyed-out. Is this intentionally ? Yes, it's intentional. The KAP140 is AFAIK only operatable via 3D cockpit. The dialogs don't work for it, so the entry is

Re: [Flightgear-devel] Autopilot on default Cessna

2006-01-28 Thread Curtis L. Olson
Martin Spott wrote: Hello, I just took the latest CVS for a ride, starting at EDWJ and heading to EDDW. To ease the job I tried to engage the autopilot via the menu - but the autopilot pull-down menue is inactive, the word Autopilot in the headline is greyed-out. Is this intentionally ?

Re: [Flightgear-devel] Re: night slowdown with nvidia GeForce 6200 on linux

2006-01-28 Thread Diogo Kastrup
Alex Romosan wrote: still trying to figure out the real reason why the nvidia driver is slow when we enable GL_POINT_SMOOTH in fgfs (and learning a lot more about openGL then i ever wanted to know). I've modified your test program to follow what is done in flightgear, and looks like the

[Flightgear-devel] Re: night slowdown with nvidia GeForce 6200 on linux

2006-01-28 Thread Alex Romosan
Diogo Kastrup writes: I've modified your test program to follow what is done in flightgear, and looks like the problem is the lack of acceleration when drawing triangles in point mode. So, if this is right, we can't get the acceleration again without changing the way lights are drawn.

[Flightgear-devel] Re: Autopilot on default Cessna

2006-01-28 Thread Melchior FRANZ
[autopilot menu entry disabled for the default aircraft] * Martin Spott -- Saturday 28 January 2006 19:45: Melchior FRANZ wrote: Yes, it's intentional. The KAP140 is AFAIK only operatable via 3D cockpit. Ah, that's ok. This doesn't make it easier to realise my plan but I will accept the

Re: [Flightgear-devel] Request for comment: runtime validation of input files

2006-01-28 Thread AJ MacLeod
On Wednesday 25 January 2006 19:13, Berndt, Jon S wrote: Yes. If you look at the top of some of the JSBSim aircraft models (the ones that were gotten from the JSBSim web site, were created with a current version of Aeromatic, or have been translated using the latest translation utility) you

Re: [Flightgear-devel] Re: Autopilot on default Cessna

2006-01-28 Thread Martin Spott
Melchior FRANZ wrote: [autopilot menu entry disabled for the default aircraft] * Martin Spott -- Saturday 28 January 2006 19:45: Ah, that's ok. This doesn't make it easier to realise my plan but I will accept the facts :-) $FG_ROOT/Nasal/gui.nas, line 71 ... it's all yours! :-) Many

RE: [Flightgear-devel] Discussion: next FlightGear release.

2006-01-28 Thread Innis Cunningham
Hi Curt Curtis L. Olson writes Now that the v0.9.10 scenery is done. I would like to start thinking about the next FlightGear release which will be called v0.9.10 to match the scenery. The biggest thing that comes to mind for the next release is that we need to fix up all the JSBsim

Re: [Flightgear-devel] Discussion: next FlightGear release.

2006-01-28 Thread Curtis L. Olson
Innis Cunningham wrote: Animations ??.I am aware that there has been changes to the FDM and the engine files but was not aware of any changes to the control surface animations.If this is so could someone point me to the relevant information. As I am in the middle of updating the 737 model and

Re: [Flightgear-devel] Discussion: next FlightGear release.

2006-01-28 Thread Innis Cunningham
Curtis L. Olson writes Innis Cunningham wrote: The issue is that JSBsim doesn't output the normalized control surface positions like it used to. Instead you have to add a section for each surface in the JSBsim config file to set the normalized surface values that FlightGear expects to

0.9.10 Scenery Quirks (was Re: [Flightgear-devel] Discussion: next FlightGear release.)

2006-01-28 Thread David Megginson
On 28/01/06, Curtis L. Olson [EMAIL PROTECTED] wrote: Now that the v0.9.10 scenery is done. I would like to start thinking about the next FlightGear release which will be called v0.9.10 to match the scenery. I've been using the new scenery, and have noticed some quirks -- for example, the

[Flightgear-devel] OT: Saturday night movie review

2006-01-28 Thread Curtis L. Olson
I suspect that most of you probably don't care too much about my life story, but it's Saturday night, things are slow, I just got back from seeing End of the Spear, so it's movie review and story time. If anyone wants to know where my love of aviation comes from go see this movie. I've never

RE: [Flightgear-devel] OT: Saturday night movie review

2006-01-28 Thread dene maxwell
Hi Curt, Thanks for the review and the pics. Isn't sharing those sorts of experiences what the flying (sim or reality) is about? It's great hearing about others experiences and even better with pics Cheers Dene From: Curtis L. Olson [EMAIL PROTECTED] Reply-To:

Re: [Flightgear-devel] Discussion: next FlightGear release.

2006-01-28 Thread Martin Spott
Curtis L. Olson wrote: I'm going to be out of town Feb 7-14 for Scale 4x in Los Angeles so the release won't happen until sometime after that. After the v0.9.10 release, I would really like to make our final push toward v1.0. This timeframe sounds like a good start - I think it's the