Arnt Karlsen wrote:
..be adviced the guys here torched me for suggesting redoing FG in C,
so I guess you by C really meant C++, no? ;-)
No I really did mean C :-) I'm not suggesting redoing anything, just
writing an app which may be useful to real pilots and FG pilots too.
AFAIK (and I
On Thursday 29 Apr 2004 6:40 am, Martin Spott wrote:
I _strongly_ support Arnt's idea of 3D coordinates for the sound/noise
sources. To complete the picture I'd suggest binding the listener's ear
positions to the view direction (implemented somewhere in the viewer
mechanics in order to make it
Jonathan Richards wrote:
Seconded - this is very important for first-person games [0], but it would be
good to have, for instance surround wind noise, engine noise from the engine
directions and ATIS speaking from the speakers. Oh, hold on. In a real
plane, I've got headphones, haven't
Does anyone know why this might be happening:
$ ls -al *.exe
ls: invalid option --
Try `ls --help' for more information.
I've already checked alias - I don't have anything for ls.
ls --version gives:
$ ls --version
ls (fileutils) 4.1
Written by Richard Stallman and David MacKenzie.
Copyright
Matthew Law wrote:
Arnt Karlsen wrote:
..be adviced the guys here torched me for suggesting redoing FG in C,
so I guess you by C really meant C++, no? ;-)
No I really did mean C :-) I'm not suggesting redoing anything, just
writing an app which may be useful to real pilots and FG pilots
Jon Berndt wrote:
Does anyone know why this might be happening:
$ ls -al *.exe
ls: invalid option --
Try `ls --help' for more information.
I've already checked alias - I don't have anything for ls.
ls --version gives:
$ ls --version
ls (fileutils) 4.1
Jon,
The only thing that comes to mind
Jon Berndt wrote:
Does anyone know why this might be happening:
$ ls -al *.exe
ls: invalid option --
Try `ls --help' for more information.
I've already checked alias - I don't have anything for ls.
ls --version gives:
$ ls --version
ls (fileutils) 4.1
Written by Richard Stallman and David
Martin Spott wrote:
Yep, but when you're sitting in your favourite light single and you
turn your head over to your co (or passengers) you'll still hear most
of the engine noise on your left ear - even with headset applied. If
something hits the aircraft during flight I assume you'll still notice
Curt wrote:
The only thing that comes to mind is to check if you have a .exe
filename that starts with a -. This will confuse ls's command line
parser. There are a few ways around that, such as ls -al ./*.exe
Heh. You're good. I had a file named -o parseDatcom.exe. Removing that
fixed it.
joke
AFAIK that isn't possible because the earpoint would change whether
you were looking at the ground in front or the air 10 miles away. What
shouldn't be hard is to take an audio feed from a different location
from the viewpoint, but not much might happen if the audio hasn't been
initialised
David Megginson said:
Martin Spott wrote:
Yep, but when you're sitting in your favourite light single and you
turn your head over to your co (or passengers) you'll still hear most
of the engine noise on your left ear - even with headset applied. If
something hits the aircraft during
I actually got interested in all this windows stuff yesterday (no, I
can't explain why), and played around with getting it built. Here's
the proof:
http://plausible.org/andy/fgfs-mingw.zip [2.3 MB]
It's a MinGW* build, using SDL and OpenAL. It works, with sound and
video mode switching.
Andy Ross writes:
I actually got interested in all this windows stuff yesterday (no, I
can't explain why), and played around with getting it built. Here's
the proof:
http://plausible.org/andy/fgfs-mingw.zip [2.3 MB]
Cool
+ There is no Win32 implementation of the simgear/threads
Jim Wilson wrote:
Lower frequencies especially would be hard to detect direction anyway even
without the hard surfaces. This reminds me of the engine out protocol on
light twins, which seems to assume that you won't hear which engine is silent.
That's an excellent point -- there are several
Hi Andy,
First of all, thanks for your help with the config file.
Now I have another question: I would like to ask you if it is possible to
start from Yasim in order to obtain a ground vehicle dynamic model. My idea
is to develop a truck simulation inside FlightGear and I have thought to
start
Hi Andy,
First of all, thanks for your help with the config file.
Now I have another question: I would like to ask you if it is possible to
start from Yasim in order to obtain a ground vehicle dynamic model. My idea
is to develop a truck simulation inside FlightGear and I have thought to
start
Marco Gugel wrote:
My idea is to develop a truck simulation inside FlightGear and I
have thought to start from Yasim because it uses the rigidbody
dynamics;
Right. That's the RigidBody/Integrator/BodyEnvironment
implementation. You set masses on the body, calculate forces inside
the
Iain Dawson has sent me a very nice 2D instrument panel for the Beech 99
which I have committed to CVS. Now that the panel is so nice, it's a
shame that the 3d model is so simplistic and unanimated. Anyone want to
take a crack at this? Also, the FDM is UIUC based which means the
gear/engine
Curtis L. Olson wrote:
Anyone want to take a crack at a new FDM model for the Beech 99
as well? You could probably start with the data for the UIUC
model and go from there.
The Beech 99 is a turboprop, which means that YASim is going to
need new code to support it. I'd be happy to write it
Andy Ross wrote:
The Beech 99 is a turboprop, which means that YASim is going to
need new code to support it. I'd be happy to write it if someone
decides they want to go that way.
Doing so would open the way to a whole bunch of other interesting
turboprops, including the Beech KingAir (from
That would argue for a variable for each viewpoint changing the
directionality of the sound (i.e the size of the magnitude of difference
between the speakers). Howe easy would this be to implement?
Giles
-Original Message-
From: David Megginson [mailto:[EMAIL PROTECTED]
Sent: 29 April
I just tried an endurance flight in the B-52F, after having tweaked the fdm a
bit, but the engines shut down while I still had 64% fuel remaining.
The B-52F currently has five fuel tanks: 2 x internal wing tanks - 7lbs, 1
x internal fuselage tank - 73318 lbs 2 x external wing tanks -
Giles Robertson wrote:
That would argue for a variable for each viewpoint changing the
directionality of the sound (i.e the size of the magnitude of difference
between the speakers).
No - at least not as long as I don't misunderstand your point ;-)
From an engineers point of view (I _am_ an
Lee Elliott wrote:
It looks like the fuel was being taken from each tank at the same rate
instead of proportionally, depending upon their capacity, with the
result that the external wing tanks were emptied while the other tanks
still held plenty of fuel, and this caused the engine shutdown.
It's even better. You can hook up your 5.1 amplifier and speaker set
using ALSA:
http://floam.ascorbic.com/how-to/alsa5.1
Finally a fitting moment has come to test my 5.1 digital set up...
unfortunately I won't get time until the weekend...
___
On Thursday 29 April 2004 19:59, Andy Ross wrote:
Lee Elliott wrote:
It looks like the fuel was being taken from each tank at the same rate
instead of proportionally, depending upon their capacity, with the
result that the external wing tanks were emptied while the other tanks
still held
Norman Vine wrote:
Andy Ross writes:
+ There is no Win32 implementation of the simgear/threads stuff, so
MinGW (and MSVC) builds cannot use threads.
see
Open Source POSIX Threads for Win32
http://sources.redhat.com/pthreads-win32/
This works fine with MingW or MSVC and
On Thursday 29 April 2004 20:50, Andy Ross wrote:
Lee Elliott wrote:
Is there a way of starting a Nasal script automatically at start-up?
(this would help with zeroing the A-10 external tanks for the clean
configuration)
Sure, you can put a nasal block at the top of a -set.xml file (next
David Luff helped some more
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
David Luff
Sent: 28 April 2004 21:18
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] OpenAL
Vivian Meazza writes:
Result - failure,
Lee Elliott wrote:
and the scripts then need to be explicitly invoked.
Presumably, omitting the '![CDATA[' and ']]' bits will then result in the
scripts being executed at start-up.
No, the CDATA stuff is just escaping to prevent the XML parser from
being confused by literal , or characters
Vivian Meazza writes:
I downloaded the most recent CVS version, with the modifications already
made, and I still get
Config.status: creating \
.infig.status: error:cannot find input file.
Hi Vivian,
Was this a fresh CVS checkout or did you just refresh
your existing files ?
If the
Giles Robertson wrote:
That would argue for a variable for each viewpoint changing the
directionality of the sound (i.e the size of the magnitude of difference
between the speakers).
No - at least not as long as I don't misunderstand your point ;-)
I'll give an example. In a fictional
OK, I think I've got the kinks worked out of the MinGW work, and
have written up a little README (attached) describing how the
process works. Thanks to Norman and Frederic for the pointer to
the pthread library.
The required changes are in CVS now, and the process has been
tested at least on my
33 matches
Mail list logo
