> Please note, the check for
> features.can_disable_environment == 1 is gone now. It doesn't make any
> sense there.
In a current GIT, none of the checks make any sense, because current GIT
always has all the features. On the other hand, the purpose of the
compat_layer.nas is to provide compatibil
Ill try this & see if it works, ill get back to u guys later on this week,
away on vacation now. But thanks for responding, if anyone else know of
"sure" solution let me know though, but I will be sure to try this out. Oh
& yes the com port number is correct, not sure y its that high but it is
CO
On Thu, Aug 4, 2011 at 12:22 AM, marthter wrote:
>
>
> I also have separately installed FlightGear via the package manager, so I
> tried pointing FG_AIRCRAFT at what appears to be the Aircraft directory,
>
> Also when I guessed at what to put for the terrasync exe spot, which I found
> in ~/flight
I used the download_and_compile.sh script as described here:
http://wiki.flightgear.org/Scripted_Compilation_on_Linux_Debian/Ubuntu.
I have done this all under my home directory under a "flightsim"
directory I made, and my system is
$ cat /etc/issue
Ubuntu 11.04
$ uname -a
Linux software1
Tim Moore wrote:
> One thing (perhaps the only thing) that was nice about keeping
> aircraft in fgdata is that enforced synchronization between the
> aircraft and other common nasal and instrument files. However, if they
> are split out, maybe we will be forced to be more mature about
> backward
On Tue, Aug 2, 2011 at 11:39 AM, Francesco Angelo Brisa
wrote:
> Any news about a possible separation of aircrafts data from the fgdata
> folder ?
> I am afraid this topic is sligtly falling into the "forget about it" folder
> :-(
>
>
> Cheers
> Francesco
>
Some of the inertia -- on my part -- com
On Wed, 3 Aug 2011, Csaba Halász wrote:
On Wed, Aug 3, 2011 at 8:53 PM, Gene Buckle wrote:
COM27 is also a suspicously(sp) high port#.
That seems to be quite normal for usb adapters. However you are right
that this is the cause of the problem.
Quote from msdn:
I've NEVER seen it higher th
On Wed, Aug 3, 2011 at 8:53 PM, Gene Buckle wrote:
>>
> COM27 is also a suspicously(sp) high port#.
That seems to be quite normal for usb adapters. However you are right
that this is the cause of the problem.
Quote from msdn:
To specify a COM port number greater than 9, use the following syntax:
On Wed, 3 Aug 2011, Curtis Olson wrote:
> I personally have never tested the generic protocol over a serial port on
> windows. I'm not sure I have tested any IO over a serial port on windows
> since the very early days of the project back when we were building with
> cygwin. I do recall at the t
I personally have never tested the generic protocol over a serial port on
windows. I'm not sure I have tested any IO over a serial port on windows
since the very early days of the project back when we were building with
cygwin. I do recall at the time being (this is maybe 10 years ago at
least?)
-- Forwarded message --
From: "Derrick Washington"
Date: Aug 2, 2011 12:49 AM
Subject: Generic Protocol Error --> Error opening serial device "COM27" The
system cannot find the file specified.
To:
Hi Curt
I have been trying for a few weeks now to get FG to transmit data to
>> var setLift = func (lift) {
>> setprop("/environment/local-weather-lift",lift);
>> }
>
> Please change it on GIT and I'll change it for my next version - however
> I'd suggest to name the property
>
> /environment/local-weather-lift-fps
>
> for consistency.
Done in master and release/
> Hmmm - just notices you are setting wind-from-down-fps in your local
> weather. This is a bad idea as it is a computed value
>
> wind-from-down-fps =
>thermal-lift-fps +
>ridge-lift-fps +
>local-weather-lift
>
> That's how it was hardcoded in the "old" weather system and what I
> forg
> It's quite possible that it's broken for a while - there are not so many
> glider enthusiasts around, I usually prefer to rely on thermals when I
> have time to do some soaring, and the last time I distinctly remember
> having used ridge lift is before September 2010... Good we caught it
> before
On Wednesday 03 August 2011 11:44:23 thorsten.i.r...@jyu.fi wrote:
> It's quite possible that it's broken for a while - there are not so many
> glider enthusiasts around,
But they do exist :) But I only tried it once in FG, since performance with
the free radeon drivers is just barely usable. Bu
Thorsten wrote:
> > Meanwhile - at the cheap end of the market, Emilian and I have cleaned
> up
> > most of the textures, made some of the AC3D models single-sided,
> > reordered
> > the objects, provided unique names, and converted everything to .dds.
> >
> > This has much improved loading/unlo
> Meanwhile - at the cheap end of the market, Emilian and I have cleaned up
> most of the textures, made some of the AC3D models single-sided,
> reordered
> the objects, provided unique names, and converted everything to .dds.
>
> This has much improved loading/unloading, and given a much better
>
> Fixed in master and release/2.4.0. For some reason that code did got get
> upstream when I opened up the system for local weather. Must have been
> broken since September 2010!?
Thanks for the quick attention!
It's quite possible that it's broken for a while - there are not so many
glider enthu
18 matches
Mail list logo
