On 5 May 2010, at 12:33, Jon S. Berndt wrote:
I'd have to agree with all this. I stopped trying to build FlightGear years
ago because it is highly non-trivial. Having been involved in several large
engineering and training simulations over the years, I can say that in my
experience it's
On 5 May 2010, at 13:36, HB-GRAL wrote:
James Turner schrieb:
- grab ALUT.framework from here:
http://files.goneabitbursar.com/fg/alut-osx-universal.zip
(temporary location)
I have a own freealut 1.1.0 compiled/installed for i386. Do I have to
replace this one with your
On 17 Apr 2010, at 04:20, Tom P wrote:
That's an awesome setup, very interesting.
Would you have a tarball of this configuration and some details of how you
set up the system?
Quick answer is no, not yet, but I will. The configuration is exportable as XML
files, and I'm using the
http://zakalawe.ath.cx:8080/
is a *prototype* build server for FG (including OSG and SimGear), running on my
home box - it will need a proper home if it moves beyond the prototype stage.
For people who don't know, a build server talks to some slaves, and
grabs/builds/tests/packages code. The
On 12 Apr 2010, at 13:07, Erik Hofman wrote:
Log Message:
Replace Devid Megginsons version of the j3cub with the excellent work of
karla from the forum. Signed off by David.
Woo-hoo!
This is an awesome model, about to fire it up and take it for a spin.
Thanks to all involved for their
On 8 Apr 2010, at 03:06, Peter Brown wrote:
Perhaps this has been brought up before, but I see that the ILS beam data
for each airport on the mpmap is derived from the runway alignment (as
verified in taxidraw). This doesn't allow for magnetic deviation, and
therefore all the course
On 7 Apr 2010, at 03:36, Ron Jensen wrote:
I like the idea of using some standardized properties
under /sim/realism/ and retrofitting all aircraft to respect start-dark
or something similar.
I am also firmly against turning on aircraft to aircraft collisions.
Aircraft-aircraft collisions
On 6 Apr 2010, at 20:35, Martin Spott wrote:
Except in the case of an accident or mechanical failure, you would
*never* be sitting on the threshold with your engine off, especially
at a big airport like KSFO (unless you wanted to give your plane and
yourself a 747-sized colon exam). I think
On 7 Apr 2010, at 00:27, David Megginson wrote:
OK, here's my suggestion: *all* aircraft start with the runway
threshold with the engine idling, unless the user has overridden that.
Engine on/off is a decision that it doesn't make sense leaving to
individual aircraft designers, since it's a
On 2 Apr 2010, at 09:25, James Sleeman wrote:
I can see there is a huge performance penalty on 2-years old GPUs, so we
also need performance vs eye candy user setting to choose which technique
could be applied besides simple advertised extension support
Turning on Landmass effects cuts my
On 2 Apr 2010, at 15:28, Peter Brown wrote:
Quick question for James I think - when the route manager passes the last
listed nav point, the AP doesn't disengage, it turns west (from the east
coast). This is a default heading to KSFO or some other pre-determined
home ?
The intended
On 1 Apr 2010, at 11:46, Anders Gidenstam wrote:
Good, chase view seems to be back in shape after this bug fix.
Unfortunately, some other views seems to have broken: views that
are neither from-model or at-model views have stopped to obey the
eye-heading-deg-path, eye-pitch-deg-path and
On 30 Mar 2010, at 16:46, Frederic Bouvier wrote:
What about putting subset of the current materials.xml inside the
scenery tree ? The material library could search either, in that order :
1- ./tile.mat.xml ( along with tile.stg and tile.btg.gz )
2- ./materials.xml (shared for the 1x1 area
http://code.google.com/p/flightgear-bugs/issues/detail?id=99
describes (rather briefly, but the linked forum posts give more flavour) some
broken behaviour caused by refactoring in FGViewer during the 2.0 development
timeframe. The viewer damping code (which is a horrible piece of logic) was
On 24 Mar 2010, at 08:52, Martin Spott wrote:
Ooh good. Fred is that only in the CVS or also in 2.0. All working?
You did also the 3D relief? Cool I'm looking forward to try this.
So far it's just a parser. As far as I can tell there's no plan how the
Scenery is supposed to be set up,
On 24 Mar 2010, at 14:31, Torsten Dreyer wrote:
I just fixed a bug that probably revealed itself when the atmosphere model
was
changed. I noticed, that flying with real weather fetch enabled was very
unpleasant when METAR changed.
Now the sea-level temperature and dewpoint changes are
On 24 Mar 2010, at 22:09, Vivian Meazza wrote:
Bad news - works perfectly here on XP with cvs as of a few minutes ago!
Checking to see if I can break it still though.
I was using the Lightning to test my mach-calculations code earlier today (Mac,
latest CVS code) and it seemed fine.
James
On 20 Mar 2010, at 23:36, Curtis Olson wrote:
The nav radio does not work in magnetic headings. It works in which ever
alignment the station was setup in. In the 60's when GEP was installed, it
was aligned with magnetic north at that time. In the subsequent years, the
actual magnetic
On 20 Mar 2010, at 21:05, David Megginson wrote:
I understand that these properties are convenient for other systems,
but they should go somewhere they would be in real life, like a DME,
GPS database or FMS, not in the (relatively dumb) nav radio itself
under /instrumentation/nav/.
Yep,
On 20 Mar 2010, at 22:24, David Megginson wrote:
It would take hours to sort out the code to see what's actually
happening. The new init functions make things even more confusing, by
including strange side effects (for example, setting the heading now
sets the azimuth to a VOR or airport,
Replying to some specifics, I'll let Syd comment in general since he's the
Primus author, and has seem more documentation than me by far.
On 18 Mar 2010, at 03:49, Max Hertling wrote:
3) I think it would be nice, if the CDI would show the course-deflection
in FMS-Mode the same way it does
On 18 Mar 2010, at 13:01, Robin van Steenbergen wrote:
You
can find it under http://openrj.stoneynet.nl/ , it's BSD licensed, so
feel free to have a poke around in the source code ;)
I might have a chat with you about efficient anti-aliased rendering of digital
displays via OpenGL in a
I've cooked up a (crude!) moving navigational map as a custom PUI widget - it's
*not* an Atlas-replacement, or an MPMap replacement, more a 'close in' thing
for situational awareness, and a way to prototype and experiment with
techniques I'll use in real cockpit displays in the future. (it's
On 15 Mar 2010, at 23:49, Michael A. K. Gross wrote:
I haven't seen this happen elsewhere, so I suspect it may not have been
noticed, hence the bug report.
This is a bleeding edge CVS, with bleeding edge OSG and SimGear as
well. Debian linux with the latest graphics driver from Nvidia,
On 16 Mar 2010, at 08:14, Erik Hofman wrote:
When I try a reset from the menu , I get this error :
passed invalid index (0) to FGRouteMgr::jumpToIndex
Fatal error: name may contain only ._- and alphanumeric characters
This looks like a comment from the xml parser.
Ouch - the first
On 16 Mar 2010, at 08:43, Frederic Bouvier wrote:
Durk use exceptions to return errors. FP means Flight Plan, not Floating
Point. That's normal program execution, but it's really annoying when you
want to debug because all these exceptions are a performance killer for the
debugger, and it
On 16 Mar 2010, at 11:12, Frederic Bouvier wrote:
I've changed this code to stop using exceptions-as-return values - I
believe the fix should be in 2.0.0, but I'm not 100% positive about
that.
I am pretty sure it is not
I committed the fix on 19th February, it seems - evidently that
On 16 Mar 2010, at 15:01, Curtis Olson wrote:
There are a lot of different angles here, but I think whatever we do, we
can't take out our frustrations on the end users that flightsimpro manages to
sucker into buying a copy of FlightGear without telling them what it actually
is.
The guy
On 13 Mar 2010, at 02:55, syd adams wrote:
Could someone apply please ?
Done.
James
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and
On 10 Mar 2010, at 07:27, adams@gmail.com wrote:
Ive had a better look at the changes you made to my patch ... could you
please change them back ?
I'd prefer the option of setting these in the instrumentation.xml file , and
for safety sake , add the default settings back.
I appreciate
On 10 Mar 2010, at 15:44, syd adams wrote:
It is a bit of a turn off though, when I try to fix some minor issues and get
back into the coding side of things. and its immediately rewritten without
notice.
I apologise for committing the modified changes without asking - I felt my
On 9 Mar 2010, at 07:04, syd adams wrote:
The patch also includes the dme nav2 fix that I posted previously.
Could someone take a look and commit please ?
I'm testing these now, and will commit in a couple of moments.
James
On 9 Mar 2010, at 09:18, James Turner wrote:
Could someone take a look and commit please ?
I'm testing these now, and will commit in a couple of moments.
Committed now, with some changes:
- I've switched the pressure-alt source to be configurable, instead of
hard-coded; it defaults
I just updated data to try the A380, and I'm not seeing any model (interior or
exterior) - the FDM and other pieces seem to be loading fine. My tree contains
assorted minor changes, but nothing that should affect this.
Relevant errors, I suspect:
Failed to load submodel: Failed to load 3D
On 26 Feb 2010, at 15:40, Curtis Olson wrote:
Are you talking about forwarding your bug tracker emails to the
flightgear-devel list? I would be against that. This is effectively signing
up a bunch of people to a new mailing list they didn't ask for and is
typically considered to be
On 24 Feb 2010, at 22:15, Torsten Dreyer wrote:
logic filters use well known conditions to drive output properties. Example
for bax = baz (foo | bar).
Nice!
Regards,
James
--
Download Intel#174; Parallel Studio
On 22 Feb 2010, at 17:37, Frederic Bouvier wrote:
This should be :
int len = strlen(s);
char *buf = new char[len];
...
delete buf;
Urk I'm confused - I thought this was a C99 feature, is it a GNU extension?
Regards,
James
On 22 Feb 2010, at 18:29, Frederic Bouvier wrote:
Yes, I am afraid. This code construction show up in the code from time to
time and we have to provide a replacement.
I think the best approach is to use an auto_ptr.
std::auto_ptrchar buf( new char[len] );
in order to be exception safe.
On 22 Feb 2010, at 20:13, Brant Gipson wrote:
This file fails to compile even on Linux with g++. I just commented
out the problematic line as a quick fix so FG will compile.
That is *very* odd : I build (when I remember) with Ubuntu 9.10 here and
everything works - can you be more specific
On 16 Feb 2010, at 15:26, Jari Häkkinen wrote:
EDDB is one of the reported airports. In apt.dat.gz you'll find this row
10 52.372560 013.505561 07R 68.77 9807 . 0984.0984 148
351351 1 0 3 0.25 1 0300.0300
and in nav.dat.gz you'll find rows like
4 52.37906900
On 15 Feb 2010, at 09:12, James Turner wrote:
Start at EDDB and tune nav radio to ils frequency 110.70
fgfs: ../../../src/Instrumentation/navradio.cxx:920: double
FGNavRadio::localizerWidth(FGNavRecord*): Assertion `rwy' failed.
Ack, my fault, I'll commit a fix against the crash later
On 10 Feb 2010, at 10:50, Martin Spott wrote:
I agree with Tim on the idea of trying to keep feature requests off
the bug-list. Otherwise we'll soon end up in a situation where nobody
cares about the bug tracker because _real_ bugs are going to be
difficult to identify among the pile of
I'm stuck up an Alp until Monday, but the AB is likely just the
autopilot Xml entry being accidently removed - I shall check upon my
return to reality.
As for the GPS, please do ask if things seem strange, I'm happy to
make code changes, or document things better. The departure waypoint
On 5 Feb 2010, at 21:14, syd adams adams@gmail.com wrote:
-VNAV only follows airports- but not any other Waypoints like VOR,
NDB,
fixes
Only when frq turned to VOR
VNAV shouldn't follow ANY waypoint ... so I'm assuming you mean LNAV .
If I understand Jame's gps changes ... I should
On 28 Jan 2010, at 04:00, syd adams wrote:
you can also check the instrumentation/nav/nav-loc , but it seems to stay
stuck on true if you tune another frequency that's out of range or invalid...
not sure when that broke.
My fault, just checked the code and it's trivial to fix. WIl commit
On 28 Jan 2010, at 03:45, Ron Jensen wrote:
Here is a nasal function to determine if a frequency is a localizer. It
accepts a frequency in megahertz and returns 1 if the frequency is an
ILS frequency.
var isILS=func(freq) {
if(freq 108.10) return 0;
if(freq 111.95) return 0;
var
On 28 Jan 2010, at 09:18, James Turner wrote:
My fault, just checked the code and it's trivial to fix. WIl commit it ASAP.
Committed now - also made the same fix for 'has-gs' which was similarly getting
stuck on the old value when no valid station was tuned.
James
On 28 Jan 2010, at 16:31, Curtis Olson wrote:
It's interesting though how much nasal you can actually get away with using
without making a blip on frame rates. Nasal is *very* efficient and powerful
for being an interpreted script language.
Absolutely - and I really don't want to get into
On 21 Jan 2010, at 07:59, Erik Hofman wrote:
Fly-by views are *not* okay for me, but I must point out (before Erik gets
annoyed) that I am running a few days behind CVS due to hacking on other
areas of the code. I'll pull now and report back.
You're trying to get me a heart attack, don't
On 24 Jan 2010, at 10:23, Torsten Dreyer wrote:
Enjoy some pictures of the voyage here:
http://blog.hansajet.de/archives/category/auf-nach-finkenwerder
Fantastich!
James
--
Throughout its 18-year history, RSA
On 21 Jan 2010, at 08:14, Torsten Dreyer wrote:
http://www.linuxtag.org/2010/en/program/call-for-papers.html
Has anyone submitted a FGFS centric response to the CfP? If not, should I?
I was thinking about doing so myself after Martin sent a reminder some time
ago. I decided, that
On 20 Jan 2010, at 14:19, Peter Brown wrote:
The sound on the MacOS does still have a glitch when changing views. If you
have a good patch to try I'd be more than happy to test it.
If you recall, its most typical in fly by or tower view, and if you adjust
your viewpoint in any direction
On 20 Jan 2010, at 14:28, James Turner wrote:
This is especially the case when I switch the tower location from my
departure airport to my arrival airport. I *think* fly-by views are okay, but
I'll double-check that now.
Fly-by views are *not* okay for me, but I must point out (before Erik
On 20 Jan 2010, at 22:48, dave perry wrote:
Take it for a hop and play with the improvements. The doors are operated by
either picks or by the Comanche menu.
I've been testing these changes as part of committing them, and I can't speak
highly enough as to the quality of the results - this
On 4 Jan 2010, at 14:55, Erik Hofman wrote:
Could you file a bug report at Apple?
Returning an error number when calling alGetError that is not supported
by alGetString() is a no-go.
As has been noted by other folks, the Apple OpenAL is open-source, but
unfortunately Apple are (very) bad
On 4 Jan 2010, at 16:08, James Turner wrote:
So while it's definitely worth reporting the bug, we still need to work
around the issue, using Tat's patch
Ah, I just noticed your (Erik's) commit, never mind.
I also note the error code on Mac is -43 which I have a horrible feeling
might
For some procedures work, I need to implement the following formula:
http://williams.best.vwh.net/avform.htm#Intersection
(Various other SGGeoc / SGGeodesy functions are taken from the same source)
My current implementation isn't working. At least one reason is the note on
sign
On 29 Dec 2009, at 14:28, Erik Hofman wrote:
SGSubsystemGroup::unbind ()
{
-for (unsigned int i = 0; i _members.size(); i++)
-_members[i]-subsystem-unbind();
+// reverse order to prevent order dependency problems
+for (unsigned int i = _members.size(); i 0; i--)
+
On 24 Dec 2009, at 06:36, Peter Brown wrote:
-the route manager sometimes will open with 36000 feet in the hold altitude
box, and 7240 kts in the hold speed box. Any attempt to change them will
default back to these amounts. I am trying to see if relates to any
particular aircraft, but
On 22 Dec 2009, at 14:51, Curtis Olson wrote:
With the old route manager, the first way point is where I want to go for my
first destination, because I just put it in there with that specific goal in
mind. The 2nd waypoint is also where I want my second destination to be,
again, because
On 23 Dec 2009, at 11:42, Heiko Schulz wrote:
737-300 (Using the autopilot.panel via F11)- in 19.1 the 737-300 was the
airliner with the best autopilot behavior recommended for ILS-approaches done
by ap. with my last built from 11/27/2009 the aircraft didn't responded
anymore on NAV1-Hold
On 21 Dec 2009, at 18:55, Curtis Olson wrote:
What do you think would be a sensible course of action, in the situation you
describe? Even if I choose not to add the departure airport for in-air route
activation, there's no guarantee that the first route waypoint is where you
actually want
On 22 Dec 2009, at 12:23, John Denker wrote:
I won't bother to ask why some people consider a discussion
of auto-coordination to be hijacking an auto-coordination
thread.
I think that comment was because you replied to the 'autopilot broken' thread
to start the auto-coordination discussion.
On 21 Dec 2009, at 16:33, Heiko Schulz wrote:
There were major changes on the GPS and Route-Manager since August (3 Months
ago already!)
So this has affected the the use of the autopilot as well.
All aircrafts using the generic Autopilot-panel are affected, but not those
with an own
On 21 Dec 2009, at 17:59, Heiko Schulz wrote:
It worked as long we didn't use the Route-manager. Like Curt already said,
with pending waypoints the values are overwritten, but only then.
That hasn't changed.
Okay, so that's where the bug has come from, I need to fix the logic to only
drive
On 21 Dec 2009, at 18:10, Peter Brown wrote:
One note on using route manager - in a 12/13 CVS - if includes the departure
airport as a waypoint automatically. If you activate it on the ground it
will move past it on the takeoff roll and proceed to the next waypoint. If
you don't
On 20 Dec 2009, at 00:02, John Denker wrote:
I was also informed [off list] that the code to make
reversible ILSs usable had been ignored because it was
not good enough. That is not very informative, not
very constructive. No clarification has been forthcoming
as to what makes it not
On 20 Dec 2009, at 19:08, Alex Perry wrote:
I am unable to use MSFS. Has someone checked whether they handle reversibles
with a heuristic, or are you just guessing?
Well, that was my recollection last time I used MSFS, which was 2004 (I think).
I'm assuming they used a heuristic because the
On 19 Dec 2009, at 16:19, John Denker wrote:
Maybe the code should be made more robust so that this
is not a fault condition.
This is not the first time in history that code has
needed to perform a join on two databases that are
not in one-to-one correspondence.
Well I wrote the code in
On 19 Dec 2009, at 18:38, Melchior FRANZ wrote:
+ HASHSET(ils-frequency-mhz, 3, naNum(rwy-ILS()-get_freq() /
100.0));
FAIL
Onwards and upwards (in CVS, now). Shortest code review I've ever had (so far!)
James
On 19 Dec 2009, at 18:55, Melchior FRANZ wrote:
Still wrong. Since when do we use minus signs in variable names?
Ah, that's annoying. Can't map property names to Nasal, since '-' is a token in
Nasal.
Hmmm.
ilsFrequenceyMHz?
ils_frequency_mhz?
If there's a Nasal convention here please let
On 19 Dec 2009, at 19:03, Vivian Meazza wrote:
Hey guys, don't we test code/scripts nowadays before stuffing it into CVS?
Well the C++ code works - for this kind of thing I was lazy and hoped the
person who requested the feature will test it and let me know if they encounter
problems. I also
On 17 Dec 2009, at 18:44, Curtis Olson wrote:
I don't have personal knowledge of what is correct, but this change to
glideslope range impacts our ability to practice ILS approaches and I have a
current King Air pilot complaining about the behavior. Pulling out some old
approach plates
On 14 Dec 2009, at 11:11, Stuart Buchanan wrote:
I'd appreciate feedback, even if it is only to agree with the wording of the
statement, to ensure that we have buy-in for this.
FlightGear is a open-source flight simulator that was started in 2006. It is
released under
the GNU General
On 13 Dec 2009, at 22:10, Jacob Burbach wrote:
Nan errors still abound, sound system has lots of rough edges still,
the new material system is not finished, route manager not finished,
etc, etc. Even if everything could be cleaned up by then, there would
be no time left for any real
On 11 Dec 2009, at 19:32, Csaba Halász wrote:
Also, the whole positioned code seems to be ignorant of the fact that
buckets don't have the same size. Staying with the spatialGetClosest,
it assumes it can just use NxN boxes when in fact a different row
(latitude) could have half or double the
On 10 Dec 2009, at 21:41, Scott Hamilton wrote:
I can't seem to find it in airportinfo(), this is what debug.dump shows;
{ id: 'YMML', elevation: 131.97839, lat: -37.66986124, name:
'Melbourne Intl', has_metar: 1, lon: 144.842831907, runways: {
16: { id: 16, stopway:
On 9 Dec 2009, at 00:25, Sébastien MARQUE wrote:
I've got an suggestion for the gps code: a command nearest-coord (or
better name) which would give nearest navaid for arbitrary coordinates,
given by scratch/longitude-deg and scratch/latitude-deg. It will allow
to implement a simple
On 9 Dec 2009, at 13:47, Scott Hamilton wrote:
Something I was playing around with a few months back I thought, if only I
could find the nearest VOR/NDB/FIX/APT to
some point that I am not at but will be in the near future, unfortunately
I've forgotten what it was I was trying to do,
On 8 Dec 2009, at 20:18, Alexis Bory wrote:
- Sebastien Marque: Turnpoint is managed using OBS mode, the route is still
managed by zkv500's Nasal, only obs mode is available
(seehttp://wiki.flightgear.org/index.php/GPS_internals). It should be leg
mode but I can't get it to work as I
On 2 Dec 2009, at 06:34, Ron Jensen wrote:
| 39 – model capitalization –
| observed: 19 Dec 2008
| again: 31 Oct 2009
|For example: when specifying the option --aircraft=dhc2W, the
|dhc must not be capitalized, while the W must be capitalized.
The value used for --aircraft
On 2 Dec 2009, at 07:40, Erik Hofman wrote:
Secondly, I think it would be beneficial to have the ability to
specify a sound device for a certain group. So you could, for example,
send aircraft sounds to your speakers, and radio sounds to a headset.
Could be done with the current code but
On 2 Dec 2009, at 09:19, Stuart Buchanan wrote:
Of course, if you think that dhc2-ski is better than dhc2s, then that's
obviously your decision, but that's
a different issue to the one John brought up.
Agreed on all counts - I will fix the case-sensitivity, but other issues are up
to the
On 1 Dec 2009, at 16:59, Curtis Olson wrote:
I've been observer quite frequent segfaults in the most recent version of
FlightGear. I've started running under gdb and so far the trend seems to be
that the crash is inside the pui code and as a result of clicking ok or
cancel on a dialog
On 30 Nov 2009, at 14:24, Erik Hofman wrote:
Modified Files:
main.cxx options.cxx
Log Message:
update to allow selection of a new sound device
Nice work! And the preference / settings changes too - I know this is painful
work, but it's long overdue and will really help make using
On 30 Nov 2009, at 16:43, Nicolas Quijano wrote:
The Apple OpenAL implementation is open source, btw.
http://developer.apple.com/audio/openal.html#anchor3
It is, and a kind person has even posted patches to fix the implementation:
Been getting this deadlock *most* (not all) of the time on startup, I think
since the clouds became an effect:
fg-startup-deadlock
Description: Binary data
OSG is 2.8.2 release, latest CVS FG and SG.
James
--
Let
On 27 Nov 2009, at 06:28, Tim Moore wrote:
In my git repositories on gitorious, http://gitorious.org/fg, I've been
keeping
master branches that are supposed to be stable; the intent is for them to
be a kind of rolling release candidate that could be turned into a release
in short order.
On 16 Nov 2009, at 08:53, Victhor Foster wrote:
You need to use the Route Manager dialog. The route will only
activate once the aircraft is airborne.
Uh, I hope not :) That's not the intended behaviour, and it's not what
I see. Indeed, I normally activate the route before I taxi out to
On 16 Nov 2009, at 07:43, syd adams wrote:
Just tried the b1900d after a long while , and I have no idea how to
use my own KLN90B anymore ... any pointers on how I can fix this ?
In particular , I cant set the destination waypoint , though it
appears with a search.
I assume when you talk
On 16 Nov 2009, at 11:35, Stuart Buchanan wrote:
One minor bug was that selecting a NAV ID in the GPS reset the set
altitude to the NAV
ID height, but didn't update that altitude select on the panel. I
think this might be seen as
a bug in the GPS code rather than the panel, as that's
On 16 Nov 2009, at 17:37, dave perry wrote:
Second, I have edited my local copy for cvs so that the nav-light switch
also controls instrument/pannel lights so the c172p can be flown at
night. I also point the vors to the recent changed Instruments-3d/vor
folder which you can try out
On 14 Nov 2009, at 11:08, Anders Gidenstam wrote:
Access to these properties could e.g. be via the pilot list as for MP-chat
ignore.
I'm not entirely sure it is a good idea to add this, though. OTOH if I
really do not want to see or hear pilot X, then why not give me the option
to
On 14 Nov 2009, at 21:35, Jon Stockill wrote:
I would suggest that this is a bad idea - ever increasing port
requirements are simply going to annoy the people running the servers.
It's really not the right way to solve the problem.
Indeed, this is a geek-appeal solution, not a
On 12 Nov 2009, at 22:23, daveluff wrote:
I was wondering if anybody has any problems/bugs/oddities that needs to
be addressed in the latest SoundSystem code.
Hi Erik,
I'm still unable to run without a segfault since the new sound system
was committed. Here is my call stack:
On 11 Nov 2009, at 00:49, syd adams wrote:
Sounds good to me , but I admit I've been avoiding updating until I
know what's happening to the nav system :)
Somewhat confused by this - are you waiting for it to be 'done'?
(Which is not the nature of open-source development...)
Equally, I'm
using a nasal filter to smoothly park
the
gs needle. The attached small patch overcomes this. I wanted to have
other ac developers comments before I ask James Turner to commit this
small change.
Incidentally, I was under the impression this was already the
behaviour :)
James
On 9 Nov 2009, at 10:29, Erik Hofman wrote:
allow sound effects in the configuration file to be added to the
'avionics' sample group by setting 'typeavionics/type'.
Awesome stuff, this is such a good step towards better sound handling.
James
On 9 Nov 2009, at 13:58, Geoff McLane wrote:
4. At start up, getting a whole bunch of -
voice synth: word 'airport_information' not found
voice synth: word '/_' not found
voice synth: word 'automated_weather_observation' not found
... etc
but maybe I have not 'installed' something?
That's
On 5 Nov 2009, at 23:22, Vivian Meazza wrote:
Alexis Bory has just provided us with an update to the FFG 7 model.
It is so
good I thought it worth posting a short note. You can see it here:
Nice work indeed!
--
701 - 800 of 1199 matches
Mail list logo
