I vote in favor of enabling threads. I've ran FlightGear for ten hours, with
threads enabled, without any problems.
In addition, it's probably a good time to do this now, just after a release.
Because enabling threading now in cvs will give the developers ample time to
iron out any bugs well
Durk Talsma wrote:
I vote in favor of enabling threads. I've ran FlightGear for ten hours, with
threads enabled, without any problems.
In addition, it's probably a good time to do this now, just after a release.
Because enabling threading now in cvs will give the developers ample time to
On Friday 16 April 2004 19:52, Curtis L. Olson wrote:
Are there any platforms which use the configure system which have
trouble with threads? What's the situation with cygwin and mingwin?
Cygwin supports threads just fine. I don't know about mingwin though...
HTH,
Durk
Curtis L. Olson writes:
Durk Talsma wrote:
I vote in favor of enabling threads. I've ran FlightGear for ten hours, with
threads enabled, without any problems.
In addition, it's probably a good time to do this now, just after a release.
Because enabling threading now in cvs will give
I have modified the configure script to default to enabling [p]threads.
On systems with buggy or no pthread support, you can easily disable
threads by passing --with-threads=no to the configure script.
Regards,
Curt.
--
Curtis Olsonhttp://www.flightgear.org/~curt
HumanFIRST Program
Durk Talsma wrote:
I experienced (some of) these pauses as well when I built FlightGear
without threading support (See my bug reports on fgfs-devel last week,
the smoother performance refers to the absence of the pauses
:-)). After enabling threading again, the pauses went away. So my
guess
Is there any way to play sounds from a Nasal script?
--
Roy Vegard Ovesen
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Roy Vegard Ovesen wrote:
Is there any way to play sounds from a Nasal script?
Sort of. The current sound model is property-driven. You can create
a new sound event (see the *-sound.xml files under Aircraft for
examples) and drive it from a given set of properties. You can then
set those
Andy Ross wrote:
Roy Vegard Ovesen wrote:
Is there any way to play sounds from a Nasal script?
Sort of. The current sound model is property-driven. You can create
a new sound event (see the *-sound.xml files under Aircraft for
examples) and drive it from a given set of properties. You
Curtis L. Olson wrote:
Andy, one thing that would be useful would be a
globals-get_commands()-addCommand() type function that would load
and play an arbitrary sound file. I don't know if there is a nasal
interface to these commands but if not, that would be a useful thing.
These commands can
On Friday 16 April 2004 23:38, Andy Ross wrote:
Roy Vegard Ovesen wrote:
Is there any way to play sounds from a Nasal script?
Sort of. The current sound model is property-driven. You can create
a new sound event (see the *-sound.xml files under Aircraft for
examples) and drive it from a
Roy Vegard Ovesen wrote:
Very simple. I just want to make a beeping sound or a number of
beeps to use when the autopilot is disengaged (or any other audible
annunciators).
If it is aircraft-specific, then the mechanism of putting it into the
-sound.xml file is probably exactly what you want.
Thanks for the tips.
On Friday 16 April 2004 23:58, Andy Ross wrote:
If it is aircraft-specific, then the mechanism of putting it into the
-sound.xml file is probably exactly what you want.
I would say that it's more instrument-specific than aircraft-specific.
Things like
playing sounds
Hi,
Curt has just committed my Bendix/King KAP140 Two axis autopilot. It is
available in the default C172 3d cockpit and 2d panel. Please try it out. I
have no hands-on experience with the KAP140, so there might (rather _will_)
be some things that I haven't got right. Please let me know!
The
Roy Vegard Ovesen wrote:
I don't think it's possible to put sound configurations into the
instrument configuration XML files, or is it?
No, it has to live under /sim/sound/fx in the global property tree.
We can make a set of global sounds in preferences.xml (or something
included from there)
Curtis L. Olson writes:
Durk Talsma wrote:
I vote in favor of enabling threads. I've ran FlightGear for ten hours, with
threads enabled, without any problems.
In addition, it's probably a good time to do this now, just after a release.
Because enabling threading now in cvs will give
16 matches
Mail list logo
