Wouldn't it be useful to somehow flag the airport as
closed/restricted/whatever in the data, so that nav displays and gps/fms
units could show a different airfield symbol if desired for closed
airports? Does the data format support this?
FG could say (closed) in the end also based on the flag, if
On Friday 09 December 2011 16:49:14 HB-GRAL wrote:
> Am 08.12.11 13:36, schrieb HB-GRAL:
> > Hi all
>
> Hi again
>
> About marking "closed" airports in apt.dat:
>
> - marking the name with "[X] " might be closer to charts I guess and
> most airports marked as closed in apt.dat comes with the x
> -
Am 08.12.11 13:36, schrieb HB-GRAL:
Hi all
Hi again
About marking "closed" airports in apt.dat:
- marking the name with "[X] " might be closer to charts I guess and
most airports marked as closed in apt.dat comes with the x
- removing x and marking with "(closed)" at end of name is possible
On Fri, 2011-12-09 at 23:45 +0100, ThorstenB wrote:
> Find the script attached. The script does both - reports stereo files
> and all duplicates. You need to run it in the directory you want to search.
> Requires python. Is Linux only. Don't ask for documentation. Don't use
> the bug tracker if i
Erik Hofman wrote:
> There already is, fgdata/Sounds
> If more than 4 aircraft use the same file I'd say put them there
> instead.
Coordinating aircraft development errm, teaching pigs how to
fly !? ;-)
Martin.
--
Unix _IS_ user friendly - it's just selective about who its frien
Am 09.12.2011 22:53, schrieb Roland Häder:
On Fri, 2011-12-09 at 18:29 +0100, ThorstenB wrote:
Here's a full list of sound duplicates:
http://pastebin.com/DvCT6AT9
Can you please release this file? Or is it possible to sent it to me
directly? I would like to cleanup some of my archives.
Find
On Fri, 2011-12-09 at 18:29 +0100, ThorstenB wrote:
> Here's a full list of sound duplicates:
> http://pastebin.com/DvCT6AT9
Can you please release this file? Or is it possible to sent it to me
directly? I would like to cleanup some of my archives.
> cheers,
> Thorsten
Regards,
Roland
signatur
Am 09.12.2011 20:16, schrieb TDO Brandano:
> rain_canopy.wav seems, by its name, to be one example of a sound sample
> that won't benefit from the 3D sound engine as much as just being played
> back as a static, stereo sample.
That particular file has always been a mono file though - all 27 copies
rain_canopy.wav seems, by its name, to be one example of a sound sample that
won't benefit from the 3D sound engine as much as just being played back as a
static, stereo sample.
> From: e...@ehofman.com
> To: flightgear-devel@lists.sourceforge.net
> Date: Fri, 9 Dec 2011 18:40:18 +0100
> Subjec
On Fri, 2011-12-09 at 18:29 +0100, ThorstenB wrote:
> Yes, I'll do that. I added a MD5 checker to my script - interesting to
> see how many copies we already have. Considering the size of many sound
> files, this is also an issue which blows up our repository. Yes, I know
> it's handy to have al
Am 09.12.2011 15:48, schrieb Martin Spott:
> Maybe run an 'md5sum' over the files to detect identical ones, convert
> just a single one where duplicates are and copy that one over, in order
> to preserve the logical state of a file just being copied from a
> different aircraft.
Yes, I'll do that.
Hi Thorsten,
ThorstenB wrote:
> [...] We're going to branch off the 2.6
> release (fg/sg/fgdata) on January 17th. We could convert any remaining
> stereo sound files shortly before that, to make sure that FG2.6 doesn't
> mean a regression for many aircraft. I'm happy to run a batch job for
>
On Fri, 2011-12-09 at 15:19 +0100, ThorstenB wrote:
> I'd propose that aircraft maintainers have time to fix the stereo files
> themselves, say until early January. We're going to branch off the 2.6
> release (fg/sg/fgdata) on January 17th. We could convert any remaining
> stereo sound files sho
Am 09.12.2011 13:43, schrieb Erik Hofman:
> On Fri, 2011-12-09 at 12:21 +, TDO Brandano wrote:
>> I think the most compatible solution would be to either downmix them
>> to mono, or convert them to two mono samples to be played concurrently
>> but offset from their original position by an amoun
I'd suggest converting the sound files the s76c is fixed here ,
just not commited yet due to some other half finished changes. Most
files seem to just get copied from aircraft to aircraft , so the
problem will probably continue to grow.
On Fri, 2011-12-09 at 12:21 +, TDO Brandano wrote:
> I think the most compatible solution would be to either downmix them
> to mono, or convert them to two mono samples to be played concurrently
> but offset from their original position by an amount directly
> proportional to the distance from
I think the most compatible solution would be to either downmix them to mono,
or convert them to two mono samples to be played concurrently but offset from
their original position by an amount directly proportional to the distance from
the cockpit. A hack, of course, but would preserve a good p
On 09 Dec 2011, at 13:00, ThorstenB wrote:
> Hi,
>
>
> Another option might be to change the sound code again, so that stereo
> files aren't rejected, and only a warning is produced. But that would
> still result in loads of user bug reports, and it wouldn't fix the
> actual issue.
>
Would
Hi,
latest fgfs rejects loading stereo sound files. I guess it's because
stereo sounds don't really work with a 3D sound engine.
Stereo files still somehow worked with older fgfs versions, at least
they produced something audible, so few authors had noticed the issue so
far, and hence we now h
19 matches
Mail list logo
