John Denker wrote:
> The simplest approach might be:
> 0) For naive users, and even experienced VFR users,
> they don't know and don't care about this issue,
> and everybody would like to keep it that way.
> 1) At startup, we shall set every reversible ILS to
> the higher-numbered end (1
> I agree, we are due for an aggressive -Wall clean up and I'd like to remind
> our active developers that they should consider always compiling with
> warning flags activated. The following is pretty standard for me ...
>
> CFLAGS="-Wall -O2" CXXFLAGS="-Wall -O2" ./configure
>
> There is a
leee wrote:
> On Friday 07 Aug 2009, Anders Gidenstam wrote:
>> On Fri, 7 Aug 2009, leee wrote:
>>> I'm just wondering how much hardwood there is in Sweden.
>>> Sweden's Firs might have been ok for the masts and spars but
>>> hardwood was needed for the hull and superstructure, typically
>>> Oak
Tatsuhiro Nishioka wrote:
> By the way, I agree with Jari's opinion.
> I guess I need to add some script or document for building a local fgfs.
>
> I use mac specific repository since I need to make Universal binary
> with GUI launcher for both Tiger and Leopard. Thus the manual building
> in
Tatsuhiro Nishioka wrote:
> Jari,
>
> On Jun 16, 2009, at 8:47 AM, Jari Häkkinen wrote:
>> Last week I realized that I miss the OSX lancher. I checked out the OSX
>> launcher from the repository (trunk branch ... I don't get latest fixes
>> to the launcher :-0),
James Turner wrote:
> I'm always curious to know how other Mac users build FlightGear - does
> your build setup produce an fgfs binary (or application bundle) you
> could make available somewhere? It would provide another case I could
> test locally.
Since recently I actually do both (sort o
I am running fg on an MacBook Pro (10.5.7) equipped with an GeForce
8600M GT graphics card. I have not experienced any problems with
macflightgears 1.9.1 nor with the May 19 CVS package (my 1 hour flight
ended just a few minutes ago). I usually run a non-macflighgear based fg
that I build frequ
I too think that flightgear.org needs to be revamped.
As a returning user to fg I'd say that the presentation of the project
is poor but the software is great. However, it takes some time to
realize the fact that fg actually is usable ... it may be due to the
fact that I use a mac and other OSe
Have you tried
--metar=" 012345Z 15003KT 12SM SCT041 FEW200 20/08 Q1015 NOSIG"
Jari
Torsten Dreyer wrote:
> Hi,
>
> anybody an idea, how to make this work?
> --metar= 012345Z 15003KT 12SM SCT041 FEW200 20/08 Q1015 NOSIG
> I can't convice the cmdarg-parser to accept what comes behind t
Hi all,
I am a programmer and I also have a hard time to understand the impact
of the suggested changes. What I understand though is that strong egos
are battling it out on this mailing list.
There is a source code repository that supports branches. Use that! I am
sure git supports simple mer
Jon S. Berndt wrote:
> This question comes up sometimes, and then a fix is made. There may be a
> misinterpretation in the interface between FlightGear and JSBSim about
> winds. For instance, when a wind is specified is that a from direction or a
> "to" direction? JSBSim interprets wind specificati
Hi all,
I have Saitek Cyborg Evo Force joystick that does not work with the
released MacFG (1.9.1) nor latest CVS flightgear on my Mac (OSX 10.5.6).
There are several issues to resolve. I list the issues below and also
suggest how to fix them.
1) The latest release of PLIB does not recogniz
Hi,
There is an configuration error in file
flightgear/data/Input/Joysticks/Saitek/Cyborg-Gold-3d-USB.xml
affecting Mac users. The axis assignement for both throttle and rudder
is axis 2, i.e. the same axis. Changing the configuration file to assign
axis 3 to the throttle makes my joystick alm
101 - 113 of 113 matches
Mail list logo