I've noticed a bug in the cloud rendering at night which appears to occur when
climbing / descending through layers. (Current CVS)
A cloud layer above or below suddenly appears bright-white which can be rather
disconcerting; I've only managed to get one screenshot of it and repeating
the bug
Curtis L. Olson wrote:
Are there any major outstanding bugs or issues we need to resolve before
the next release?
I don't think so, no major issues. Although I'd like to mention two
things:
1.) Do you have any plans if/when to deal with Michael's already
well-known ;-) 'crease' stuff -
On Wed, 15 Dec 2004 10:18:04 -0600
Curtis L. Olson [EMAIL PROTECTED] wrote:
Are there any major outstanding bugs or issues we need to resolve before
the next release? I realize there are perpetual things (such as our gui
interface is crude) that we won't be able to address immediately,
Chris Metzler wrote:
Flying a 737, saving the state, quitting, restarting, and loading
the saved state crashes fgfs.
C172 and C310 typically are JSBSim-based, you could try the YASim-C172
for a cross-check,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
Curtis L. Olson wrote :
... but right now I would tentatively be targeting somewhere between
Christmas and New Years.
I will not be able to make win32 binaries until 2005.
-Fred
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
On Wednesday, 15 December 2004 18:18, Curtis L. Olson wrote:
Are there any major outstanding bugs or issues we need to resolve before
the next release?
The select airport option in FG does not work in my CVS build on Saturday.
In fact I've never seen it work.
I'm not sure how hard it would be
On Wed, 15 Dec 2004 13:15:34 -0500
Chris Metzler [EMAIL PROTECTED] wrote:
- the inner marker sound immediately upon startup, while sitting on
the runway, that can only be stopped by starting your takeoff roll and
getting far enough along into it.
AMENDMENT: as noted when this got brought up
On Wed, 15 Dec 2004 13:15:34 -0500
Chris Metzler [EMAIL PROTECTED] wrote:
- attempting to load a saved state from the menu crashes the program.
ADDENDUM: This appears to be a/c dependent.
Flying a c172, saving the state, quitting, restarting, and loading
the saved state works.
Flying a c310,
On Tue, Sep 14, 2004 at 04:52:01PM +0200, Georg Vollnhals wrote:
due to my bad english knowledge I will repeat some technical expressions in
German, Melchior Franz will understand it:
I'm Austrian! Well, I do of course understand some German words ...
And by the way, your English seems fine for
Melchior FRANZ wrote:
On Tue, Sep 14, 2004 at 04:52:01PM +0200, Georg Vollnhals wrote:
If you lock your rotor brake when starting a turbine you will burn the
blades of the working turbine part - good luck!
Once I implement the rotor brake, I'll need to know what I had
to expect model in
On Wed, Sep 15, 2004 at 02:52:30PM +, Martin Spott wrote:
Melchior FRANZ wrote:
I'm in exile and handling email via
telnet/mutt on a Win95/100MHz/8MB machine; very painful! :-/ )
Try 'PuTTY' - presumably the best you can get on Windows:
I meant 'telnet' -- the protocol, not Micros~1's
On Wed, 15 Sep 2004 18:58:00 +0200, Melchior wrote in message
[EMAIL PROTECTED]:
On Wed, Sep 15, 2004 at 02:52:30PM +, Martin Spott wrote:
Melchior FRANZ wrote:
I'm in exile and handling email via
telnet/mutt on a Win95/100MHz/8MB machine; very painful! :-/ )
Try 'PuTTY' -
How about smelly exhaust? =P
Ampere
On September 15, 2004 10:17 am, Melchior FRANZ wrote:
If you lock your rotor brake when starting a turbine you will burn the
blades of the working turbine part - good luck!
Once I implement the rotor brake, I'll need to know what I had
to expect model
On Sun, Sep 12, 2004 at 08:21:47PM +, Martin Spott wrote:
According to what I've seen (partly from very nearby) helicopter pilots
use to start their turbines with the transmission already clutched to
the engine.
I fly regularly with helicopters (just 4 days ago with an AB212), but
Melchior FRANZ wrote:
I fly regularly with helicopters (just 4 days ago with an AB212), but
unfortunately I don't usually pay much attention to this. Mostly
they do pick me up with running engines and rotors. I remember,
though, that an AB204 pilot started the engine first, and *then*
On Mon, Sep 13, 2004 at 09:50:50AM +, Martin Spott wrote:
I hope you didn't misunderstand me. It was _not_ my intention to drag
your startup procedure in the mud.
No problem. Despite the unfinished state of the FDM the Nasal
parts could perhaps be more realistic at least. As I said, I'll
On Sat, Sep 11, 2004 at 08:28:13PM -0600, Dave Perry wrote:
1. bo105 - no power. I did not look for the reason.
Shift-]- start turbines
wait 30 seconds
Shift-] again - clutch rotor
m.
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Melchior FRANZ wrote:
On Sat, Sep 11, 2004 at 08:28:13PM -0600, Dave Perry wrote:
1. bo105 - no power. I did not look for the reason.
Shift-]- start turbines
wait 30 seconds
Shift-] again - clutch rotor
m.
Does fgfs use direct key addressing or is it important which keymap do
Dave Perry wrote:
3. f104 - no power. This used to work.
I'm baffled about this one. It's not clear to me what is causing this.
4. j3cub - Aborted. This used to work.
This dos work for me. If it's an assertion problem then it is caused
by OpenAL. Just try to start FlightGear again and things
Matevz Jekovec wrote:
Melchior FRANZ wrote:
On Sat, Sep 11, 2004 at 08:28:13PM -0600, Dave Perry wrote:
1. bo105 - no power. I did not look for the reason.
Shift-]- start turbines
wait 30 seconds
Shift-] again - clutch rotor
m.
Does fgfs use direct key
On Sun, Sep 12, 2004 at 10:17:12AM +0200, Melchior FRANZ wrote:
Shift-]- start turbines
wait 30 seconds
Shift-] again - clutch rotor
err ... it's less than 30 seconds, actually. Just wait for
100% engine power. Then you'll have to wait around 30 seconds
for the rotor to spin up to
Melchior FRANZ wrote:
On Sat, Sep 11, 2004 at 08:28:13PM -0600, Dave Perry wrote:
1. bo105 - no power. I did not look for the reason.
Shift-]- start turbines
wait 30 seconds
Shift-] again - clutch rotor
BTW, isn't this totally irrealistic ? I've never seen a helicopter
clutching
On Sun, Sep 12, 2004 at 04:35:15PM +, Martin Spott wrote:
Melchior FRANZ wrote:
On Sat, Sep 11, 2004 at 08:28:13PM -0600, Dave Perry wrote:
1. bo105 - no power. [...]
Shift-]- start turbines
wait 30 seconds
Shift-] again - clutch rotor
BTW, isn't this totally
Melchior FRANZ wrote:
On Sun, Sep 12, 2004 at 04:35:15PM +, Martin Spott wrote:
BTW, isn't this totally irrealistic ? I've never seen a helicopter
clutching the rotor with engines at full speed - I assume this would
break the whole transmission at once !
No, it isn't totally
Martin Spott wrote:
The 'faked' engine startup process doesn't look that bad. I simply
wonder why you didn't sync rotor acceleration to it. To be honest: I
don't understand how you managed to separate the two
Sorry, I forgot tthe smilie - here you are: :-)
Martin.
--
Unix _IS_ user
Not if the helicopter uses an automatic transmission. =P
Ampere
On September 12, 2004 12:35 pm, Martin Spott wrote:
BTW, isn't this totally irrealistic ? I've never seen a helicopter
clutching the rotor with engines at full speed - I assume this would
break the whole transmission at once !
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] next release - ac that don't work
Not if the helicopter uses an automatic transmission. =P
Ampere
On September 12, 2004 12:35 pm, Martin Spott wrote:
BTW, isn't this totally irrealistic ? I've never seen a helicopter
clutching
Giles Robertson wrote:
Automatic gearboxes fail too often on the road, without much warning,
for me to want one in a chopper. At least if a fixed wing engine fails
you can attempt to glide.
I've talked about that to a real helicopter pilot at our local club:
Most real rotary pilots would tell you
6. shuttle - broken (maybe I don't know what it is supposed to do)
I would suggest that the shuttle should not be released at the moment.
Jon
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Curt wrote
Sent: 16 July 2004 16:34
To: FlightGear developers discussions
Subject: [Flightgear-devel] Next release of FlightGear
I've started doing some of the pre-release work for FlightGear-0.9.5
(which is the next release.) That means I'd like to do our official
next release in the
Vivian Meazza wrote:
The Cygwin build of FGFS-cvs appears still to have a problem with the
scenery path.
I've downloaded 0.9.5 scenery via Terrasync into /FlightGear/scenery
This works:
--fg-scenery=/FlightGear/scenery
as does this:
--fg-scenery=/FlightGear/data/scenery
this
Fred wrote
Sent: 19 July 2004 10:20
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Next release of FlightGear
Vivian Meazza wrote:
The Cygwin build of FGFS-cvs appears still to have a problem with the
scenery path.
I've downloaded 0.9.5 scenery via
Frederic Bouvier writes
Norman Vine wrote:
Frederic Bouvier writes:
FG is not using the latest features new cards are offering and the
'old'
features are pretty maxed out now. This is not an explanation for
worst performance but just for lack of improvement. In the meantime,
you
Ampere K. Hardraade wrote:
Please tell me that you don't play FlightGear in wireframe mode. =P
Neh, my O2 does support filled triangles.
Just kidding.
Oh. ;-)
Erik
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Innis Cunningham wrote:
It is quite possible that the new graphics card/system is not set up for
FG.I will have a play with it and see if I can improve the situation.I
think
anisotropic filtering is on.
The point I was trying to make is people trying FG for the first time will
be dissuaded from
Erik Hofman wrote:
Innis Cunningham wrote:
It is quite possible that the new graphics card/system is not set up for
FG.I will have a play with it and see if I can improve the situation.I
think
anisotropic filtering is on.
The point I was trying to make is people trying FG for the first time
will
Richard Harke wrote:
On Saturday 17 July 2004 07:08 am, Innis Cunningham wrote:
I had a GeForce 2 Titanium with a PIII Xeon at 550MHz getting about 15 fps
over SF Video card crapped out (even has a red LED come on to tell you
it has crapped out) so I bought a Geforce FX 5200 Frame rate dropped to
Erik Hofman wrote:
This is the penalty for those who want eye-candy. If specular
highlighting is supported it will be enabled an make FlightGear slower.
I noticed some enhancements in the new rendering dialog, and would like
to ask how feasible it would be to integrate even more
Boris Koenig wrote:
Erik Hofman wrote:
Well, if we turn all that off, people start to complain that
FlightGear looks like crap and will search for something else. At
least now they start asking questions ...
Then how about optionally offering to disable such things in the
(advanced) rendering
Jonathan Polley wrote:
Fred,
It turns out that the problem should exist on every FlightGear
system, not just the Mac. On exit(), fgExitCleanup() is called which
deletes the globals class and then calls fgOSExit(). The only thing
that fgOSExit() does is turn around and call
Frederic Bouvier wrote:
What about calling SDL_Quit in a function installed by 'atexit', remove
fgOSExit and only rely on exit in all the program ?
The problem is that plib has taken the liberty to call exit() whenever
they feel like it
Erik
___
I wrote
Sent: 17 July 2004 15:22
To: 'FlightGear developers discussions'
Subject: RE: [Flightgear-devel] Next release of FlightGear
Erik Hofman wrote
Sent: 17 July 2004 14:51
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Next release of FlightGear
Vivian
[EMAIL PROTECTED] wrote:
Erik Hofman wrote:
IRIX and Solaris binaries also include it by default.
I'm not sure about other distributions, but I would
encourage them to include it with the distribution.
I include it with the slackware package too.
Is there likely to be a new release of fgrun
On Friday 16 July 2004 17:34, Curtis L. Olson wrote:
I've started doing some of the pre-release work for FlightGear-0.9.5
(which is the next release.) That means I'd like to do our official
next release in the next week or two. Please take a few minutes to
download the tar balls and test
Yep, I just got the same error. I had hoped that rerunning ./autgen.sh would
fix the problem but it appears not to.
Cheers,
Durk
On Saturday 17 July 2004 06:32, Ampere K. Hardraade wrote:
I've got an error during compiliation:
-DPKGLIBDIR=\/usr/share/FlightGear/share/FlightGear\ -g -O2
Indeed, the package only contains fg_os_sdl.cxx. I think it reflects
the packager's ( Curt ) own build option. And the package doesn't include
Network/jpg-httpd.* .
May I suggest to include all the files that are in conditional statement in
Makefile.am to be include inconditionally in an
Curtis L. Olson wrote:
I've started doing some of the pre-release work for FlightGear-0.9.5
(which is the next release.) That means I'd like to do our official
next release in the next week or two. Please take a few minutes to
download the tar balls and test this pre1 release. Please!
I wrote:
Curtis L. Olson wrote:
I've started doing some of the pre-release work for FlightGear-0.9.5
(which is the next release.) That means I'd like to do our official
next release in the next week or two. Please take a few minutes to
download the tar balls and test this pre1
Ampere K. Hardraade wrote:
make[2]: *** No rule to make target `fg_os.cxx', needed by `fg_os.o'.
Good catch. There was a mistake in the build system. This should be
solved in the FlightGear-0.9.5-pre2. (In the mean time you could just
copy the fg_os* files from CVS)
Erik
Frederic Bouvier wrote:
Indeed, the package only contains fg_os_sdl.cxx. I think it reflects
the packager's ( Curt ) own build option. And the package doesn't include
Network/jpg-httpd.* .
May I suggest to include all the files that are in conditional statement in
Makefile.am to be include
Curt wrote
Sent: 16 July 2004 16:34
To: FlightGear developers discussions
Subject: [Flightgear-devel] Next release of FlightGear
I've started doing some of the pre-release work for FlightGear-0.9.5
(which is the next release.) That means I'd like to do our official
next release in the
Vivian Meazza wrote:
SimGear-0.3.6-pre1 will not compile under Cygwin. It fails in
[openal-test1.exe]: cannot find -lalut.
This is using Norman's prebuild libraries, isn't it?
Norman has integrated the alut library and the openal library so the
reference should then be removed in the
Erik Hofman wrote:
Vivian Meazza wrote:
SimGear-0.3.6-pre1 will not compile under Cygwin. It fails in
[openal-test1.exe]: cannot find -lalut.
This is using Norman's prebuild libraries, isn't it?
Norman has integrated the alut library and the openal library so the
reference should then
Frederic Bouvier wrote:
Erik Hofman wrote:
Vivian Meazza wrote:
SimGear-0.3.6-pre1 will not compile under Cygwin. It fails in
[openal-test1.exe]: cannot find -lalut.
This is using Norman's prebuild libraries, isn't it?
Norman has integrated the alut library and the openal library so the
Ampere K. Hardraade wrote:
I've got an error during compiliation:
-DPKGLIBDIR=\/usr/share/FlightGear/share/FlightGear\ -g -O2 -D_REENTRANT -c
-o viewer.o `test -f viewer.cxx || echo './'`viewer.cxx
source='viewmgr.cxx' object='viewmgr.o' libtool=no \
depfile='.deps/viewmgr.Po'
Since there is a new release coming, I decided to bring the Mac version
back up to date (I've been busy otherwise). When I exit FlightGear, I
get the following errors (and crash).
*** malloc[8626]: Deallocation of a pointer not malloced: 0x18bef000;
This could be a double free(), or free()
Erik Hofman wrote
Sent: 17 July 2004 10:27
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Next release of FlightGear
Vivian Meazza wrote:
SimGear-0.3.6-pre1 will not compile under Cygwin. It fails in
[openal-test1.exe]: cannot find -lalut.
This is using
Line 92 of globals.cxx seems ok. subsystem_mgr was allocated with a
new operator in line 45. Could you put a breakpoint at line 92 to see
if on your system, the destructor is not called twice ?
-Fred
Jonathan Polley wrote:
Since there is a new release coming, I decided to bring the Mac
Vivian Meazza wrote:
Once the offending entries are removed from simgear/sound, simgear compiles
correctly, but Norman's pre-built libraries were still present. I'll remove
those and try again.
Nono, that's not what I meant.
Norman once build a separate library for alut and openal, but in the end
Hi Curt
I downloaded the windows binaries last night for
9.4 and the problem of the drop down menu's
locking the sim up still seem to exist.Even if you
go to exit FG and then select cancel the sim locks up.
The reason that I downloaded the binaries was that I
have just built a new box,that I am
Erik Hofman wrote
Sent: 17 July 2004 14:51
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Next release of FlightGear
Vivian Meazza wrote:
Once the offending entries are removed from simgear/sound, simgear
compiles
correctly, but Norman's pre-built libraries
Vivian Meazza wrote:
I'm a bit confused now!
There is really no need to be confused.
Norman's last version put all the stuff into openal
Good. That part is fixed in CVS no.w
Unless test1 and test2 do something useful they can be easily removed from
simgear/sound/makefile.am
We sometimes include
On Sat, 17 Jul 2004 09:34:24 +0200, Frederic wrote in message
[EMAIL PROTECTED]:
I wrote:
Curtis L. Olson wrote:
I've started doing some of the pre-release work for
FlightGear-0.9.5(which is the next release.) That means I'd like
to do our official next release in the next week
Innis Cunningham wrote:
Hi Curt
I downloaded the windows binaries last night for
9.4 and the problem of the drop down menu's
locking the sim up still seem to exist.Even if you
go to exit FG and then select cancel the sim locks up.
Hey Innis,
you just downloaded the release that is 3
I was too quick to press the reply button. I now see your
motivations, so receive all my apologies.
Frederic Bouvier wrote:
Innis Cunningham wrote:
Hi Curt
I downloaded the windows binaries last night for
9.4 and the problem of the drop down menu's
locking the sim up still seem to
Frederic Bouvier writes:
Also I noticed that in the 9.4 base the runfgfs bat file has been
removed.
Was there a reason for this.
It has been supercede by fgrun that is much user frendly.
Until fgrun is distributed with FGFS I 'vote' for the batch file being
reinstalled in the
Norman Vine wrote:
Frederic Bouvier writes:
Also I noticed that in the 9.4 base the runfgfs bat file has been
removed.
Was there a reason for this.
It has been supercede by fgrun that is much user frendly.
Until fgrun is distributed with FGFS I 'vote' for the batch file
Scrubbing FlightGear because of framerates was excatly what a friend of mine
did. I agree with Innis that someone should fix this problem.
Regards,
Ampere
On July 17, 2004 10:08 am, Innis Cunningham wrote:
The following tests were done using windows 98SE
The old box was a 850meg duron with
Frederic Bouvier writes:
Norman Vine wrote:
Frederic Bouvier writes:
Also I noticed that in the 9.4 base the runfgfs bat file has been
removed.
Was there a reason for this.
It has been supercede by fgrun that is much user frendly.
Until fgrun is distributed with
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Frederic
Bouvier
Sent: Saturday, July 17, 2004 12:20 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Next release of FlightGear
I was too quick to press the reply button. I
Frederic Bouvier writes:
FG is not using the latest features new cards are offering and the 'old'
features are pretty maxed out now. This is not an explanation for
worst performance but just for lack of improvement. In the meantime,
you probably switched to another setup/resolution that can
Norman Vine wrote:
Frederic Bouvier writes:
Norman Vine wrote:
Frederic Bouvier writes:
Also I noticed that in the 9.4 base the runfgfs bat file has
been
removed.
Was there a reason for this.
It has been supercede by fgrun that is much user frendly.
Frederic Bouvier wrote:
Norman Vine wrote:
Perhaps merntion of this should be made as a 'dependenciy'
then on http://www.flightgear.org/Downloads/source.html
Sorry Norman, but I don't understand. FlightGear does not depend on fgrun.
It is just in the Win32 binary package since 0.9.3 and probably
Norman Vine wrote:
Frederic Bouvier writes:
FG is not using the latest features new cards are offering and the 'old'
features are pretty maxed out now. This is not an explanation for
worst performance but just for lack of improvement. In the meantime,
you probably switched to another
Fred,
It turns out that the problem should exist on every FlightGear
system, not just the Mac. On exit(), fgExitCleanup() is called which
deletes the globals class and then calls fgOSExit(). The only thing
that fgOSExit() does is turn around and call exit(), which repeats the
process.
Norman Vine wrote:
Frederic Bouvier writes:
fgrun is installed by fgsetup. It is launched when you double-click on
the FG icon.
Cool,
Perhaps merntion of this should be made as a 'dependenciy'
then on http://www.flightgear.org/Downloads/source.html
IRIX and Solaris binaries also include it
Ampere K. Hardraade wrote:
Scrubbing FlightGear because of framerates was excatly what a friend of mine
did. I agree with Innis that someone should fix this problem.
The following tests were done using windows 98SE
The old box was a 850meg duron with 256 meg ram and
a GF4-MX-440 64meg graphics
Please tell me that you don't play FlightGear in wireframe mode. =P
Just kidding.
Regards,
Ampere
On July 17, 2004 04:54 pm, Erik Hofman wrote:
This is the penalty for those who want eye-candy. If specular
highlighting is supported it will be enabled an make FlightGear slower.
Erik
Frederic Bouvier wrote:
Just a thought :
Maybe it would be wise to have a TerraGear release that match released
SimGear as well ? That would avoid question about compatibility issues
that are only resolved in CVS.
Yes, I'm planning to do that soon, time permitting ...
Curt.
--
Curtis Olson
Erik Hofman wrote:
IRIX and Solaris binaries also include it by default. I'm not sure about
other distributions, but I would encourage them to include it with the
distribution.
I include it with the slackware package too.
Is there likely to be a new release of fgrun before the release of 0.9.5
Erik Hofman wrote:
IRIX and Solaris binaries also include it by default.
I'm not sure about other distributions, but I would
encourage them to include it with the distribution.
I include it with the slackware package too.
Is there likely to be a new release of fgrun before the
The file or
folder /site/ftp.flightgear.org/flightgear-ftp/Source/FlightGear-0.9.5-pre1.tar.gz
does not exist.
Did anyone encounter this problem?
Regards,
Ampere
On July 16, 2004 11:34 am, Curtis L. Olson wrote:
I've started doing some of the pre-release work for FlightGear-0.9.5
(which is
Ampere K. Hardraade wrote:
The file or
folder /site/ftp.flightgear.org/flightgear-ftp/Source/FlightGear-0.9.5-pre1.tar.gz
does not exist.
Did anyone encounter this problem?
Most likely sunsite hasn't sync'd it's mirror yet. You can always go
direct to ftp://ftp.flightgear.org
Regards,
Curt and others,
Just a quick question: Does this mean, we're entering a feature-freeze period
now? The reason I'm asking is that I have some upates for the traffic manager
that I was planning to clean-up a bit and submit by the end of the weekend.
This new code, while humble in size, is going
Ampere K. Hardraade wrote:
The file or
folder /site/ftp.flightgear.org/flightgear-ftp/Source/FlightGear-0.9.5-pre1.tar.gz
^^
does not exist.
Simply put a de. in there,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
Durk Talsma wrote:
Curt and others,
Just a quick question: Does this mean, we're entering a feature-freeze period
now?
Yes, I apologize for not being 100% clear ... I'm juggling way too many
things this summer, but I'm still trying to get a release out.
The reason I'm asking is that I have
I've got an error during compiliation:
-DPKGLIBDIR=\/usr/share/FlightGear/share/FlightGear\ -g -O2 -D_REENTRANT -c
-o viewer.o `test -f viewer.cxx || echo './'`viewer.cxx
source='viewmgr.cxx' object='viewmgr.o' libtool=no \
depfile='.deps/viewmgr.Po' tmpdepfile='.deps/viewmgr.TPo' \
depmode=gcc3
Oh, I forgot to mention, I installed simgear in /usr/share/simgear and tried
to do the same with FlightGear in /usr/share/FlightGear.
I used the following commands when I was compiling FlightGear:
./configure --prefix=/usr/share/FlightGear --with-simgear=/usr/share/simgear
make (with the error
Correction:
Not only is fgfs missing, but so are metar, terrasync, and (est-epsilon?).
Regards,
Ampere
On July 17, 2004 12:42 am, Ampere K. Hardraade wrote:
Oh, I forgot to mention, I installed simgear in /usr/share/simgear and
tried to do the same with FlightGear in /usr/share/FlightGear.
I
Oliver C. wrote:
I also found out that we have in many menus an ok button and an apply
button, for example like in the Weather conditions menu, but when i change
something in the Weather condition menu, then i can press ok and then the
change gets applied.
But when pressing ok is enough to
On Friday 26 March 2004 22:05, Curtis L. Olson wrote:
I have a bit of time this afternoon so I'm going to try to get the
official SimGear-0.3.5 and FlightGear-0.9.4 rolled out. I plan to
give the mirrors a day or two to catch up and maybe hope for a windows
build before make an official
Oliver C. wrote:
In my opinion Flightgear is not ready for the 0.9.4 release,
there are still some small bugs in the latest cvs version that should be fixed
before the release.
For example in the File menu the High-Res Snapshot option is not working, it
does nothing, a snapshot is not
On Fri, 26 Mar 2004 23:13:59 +0100
Oliver C. [EMAIL PROTECTED] wrote:
On Friday 26 March 2004 22:05, Curtis L. Olson wrote:
I have a bit of time this afternoon so I'm going to try to get the
official SimGear-0.3.5 and FlightGear-0.9.4 rolled out. I plan to
give the mirrors a day or two to catch
Erik Hofman [EMAIL PROTECTED] wrote:
Martin Spott wrote:
Shift-b _schould_ toggle the parking brake and it does so on _most_
aircrafts - some by LeeE have additional very nice gimmicks. Someone
posted Ctrl-b for the speed brake but none of the aircraft that I tried
has a working one.
The
Curtis L. Olson wrote:
I think I would like to start prepairing for the 0.9.3 release of
FlightGear. Lot's of stuff has changed, and the latest scenery works
slightly better with the current cvs code.
What is the timeline you have in mind?
I am working on a reorganization of the subsystem-, and
I think I would like to start prepairing for the 0.9.3 release of
FlightGear.
Two new key bindings are needed for the JSBSim turbine engine, and since key
bindings can be a bit contentious I thought I'd open it up for debate. I
personally don't care what keys are used. Both bindings will
David Culp wrote:
I think I would like to start prepairing for the 0.9.3 release of
FlightGear.
Two new key bindings are needed for the JSBSim turbine engine, and since key
bindings can be a bit contentious I thought I'd open it up for debate. I
personally don't care what keys are used.
Curtis L. Olson [EMAIL PROTECTED] wrote:
I think I would like to start prepairing for the 0.9.3 release of
FlightGear. Lot's of stuff has changed, and the latest scenery works
slightly better with the current cvs code.
Nice to hear - I hope I'll get the manual up to date in time. There are
a
3.) fix several aircrafts: For example thos who are supposed to have a
speed brake should really have a working one.
Yeah, my J-22 has speed brakes (modeled and animated correctly), but
shift+b doesn't do anything? This should really be fixed...
- Matevz
Yeah, my J-22 has speed brakes (modeled and animated correctly), but
shift+b doesn't do anything? This should really be fixed...
Try Ctrl-B. Does your keyboard have that?
Dave
--
David Culp
[EMAIL PROTECTED]
1 - 100 of 129 matches
Mail list logo
