[Flightgear-devel] Problems with fgjs on windows xp...

2008-01-04 Thread Cainan Whelchel
Has anyone had a problem with a missing file when trying to run the joystick config in windows? (I'm running FlightGear 1.0) It got a failed to open the template.xml file. While it is there in C:\Program Files\FlightGear\data\Input\Joysticks\ fgjs fails to find it. I got around this by

[Flightgear-devel] fg (plib branch) crashes, probably in groundnetwork.cxx

2008-01-04 Thread Maik Justus
Hi, with the plib branch (actual cvs, source and data) fg crashed here from time to time. Now I have a new (faster) PC and fg crashes much more often. It seems, that the frame rate has influence on the crash rate. Compiled with debugging information and running in the debugger I got no crash,

Re: [Flightgear-devel] [OT] Asterisk-1.4 Debian packages? Where to find?

2008-01-04 Thread Csaba Halász
On Jan 2, 2008 3:01 PM, Holger Wirtz [EMAIL PROTECTED] wrote: I have upgraded Asterisk to version 1.4. The conferences should now have an auto-mute feature: onlay one (the first) person can speak. Looks like something is broken, we get call rejected for some frequencies, such as KOAK or KNID

Re: [Flightgear-devel] view options

2008-01-04 Thread Maik Justus
Hi, Maik Justus schrieb am 26.12.2007 20:38: Hi Syd, what's about an algorithm, which checks the ratio of the screen and sets fow to 55 for 4:3 screens and 70 for 16:9 screens? (55 / 70 = (4/3) / (16/9) ) Maik P.S.: for non-physicists: (55 / 73,333 = (4/3)

Re: [Flightgear-devel] view options

2008-01-04 Thread SydSandy
On Fri, 04 Jan 2008 21:01:15 +0100 Maik Justus [EMAIL PROTECTED] wrote: Hi, Maik Justus schrieb am 26.12.2007 20:38: Hi Syd, what's about an algorithm, which checks the ratio of the screen and sets fow to 55 for 4:3 screens and 70 for 16:9 screens? (55 / 70 = (4/3) / (16/9) )

Re: [Flightgear-devel] view options

2008-01-04 Thread AnMaster
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 How does this work with windowed mode (that I always use, as maximized window, still showing the 64 pixels high KDE taskbar at the bottom, and window edges). My monitor is 4:3, but the window isn't. Regards, Arvid Norlander Maik Justus wrote:

Re: [Flightgear-devel] view options

2008-01-04 Thread alexis bory
AnMaster wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 How does this work with windowed mode (that I always use, as maximized window, still showing the 64 pixels high KDE taskbar at the bottom, and window edges). My monitor is 4:3, but the window isn't. AnMaster, same problem

Re: [Flightgear-devel] view options

2008-01-04 Thread AnMaster
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 My resoltion is 1400x1280, but you also have to consider window borders. Not sure how large they are, however the screenshots I took at www.flightgear.org (A10-KNID-01 for example), were in maximized window. Should be possible to calculate from

Re: [Flightgear-devel] view options

2008-01-04 Thread Maik Justus
Hi Arvid, AnMaster schrieb am 04.01.2008 23:13: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 My resoltion is 1400x1280, not 4:3 nor 16:9 ? but you also have to consider window borders. Not sure how large they are, however the screenshots I took at www.flightgear.org (A10-KNID-01 for

[Flightgear-devel] all flight trims initialize to 0.0?

2008-01-04 Thread dave perry
Hi all, I searched this list for a change to trim initialization but did not find any. This is from the plib branch, essentially V1.0. I have initial values specified in the -set.xml file for /controls/flight/elevator-trim /controls/flight/aileron-trim /controls/flight/rudder-trim which are

Re: [Flightgear-devel] all flight trims initialize to 0.0?

2008-01-04 Thread dave perry
dave perry wrote: Hi all, I searched this list for a change to trim initialization but did not find any. This is from the plib branch, essentially V1.0. I have initial values specified in the -set.xml file for /controls/flight/elevator-trim /controls/flight/aileron-trim