Hi all,
I am trying to compile FG under Xubuntu 12.04 using Brisa's script (version
1.31). At
first sight the compilation went fine, however sound is not working: when I run
fgfs I
get the following error and no sound:
AL lib: oss.c:169: Could not open /dev/dsp: No such file or directory
Hi Ignacio,
My old .alsoftrc was forcing everything to be played through OSS (I guess that
used to
make sense back when OSS was the only reliable option, but now OSS seems to be
broken).
I simply deleted the .alsoftrc file from my home directory. Now OpenAL sees all
the
available options, and
recently.
Pete
On Sat, Nov 12, 2011 at 2:38 PM, Martin Spott martin.sp...@mgras.netwrote:
Hi Maxime and others,
Maxime Guillaud wrote:
You can find my code here [...]
I'm just starting to recover from a couple of _really_ tight days
(including a nice PostgreSQL
Peter Sadrozinski psadrozin...@gmail.com wrote:
I would experiment with removing the code that removes the node. You'll be
trading one error for another, but it may help track this down.
Actually, this is exactly what one of my commits is doing:
Hi Martin,
Martin Spott martin.sp...@mgras.net wrote:
I know it's really cool to maintain private source repositories ;-)
but for increasing the overall success of building FlightGear
scenery I'd think it would be really beneficial to keep the various
development efforts in close
James Turner zakal...@mac.com wrote:
Onwards with fixing the fgfs-construct crashes!
I have had pretty good luck building complex scenery with a modified version of
fgfs-construct. Here is what I did:
Following advice by Peter Sadrozinski here on the list, I started from the code
in
On Sat, 15 Oct 2011 08:53:45 + (UTC)
Martin Spott martin.sp...@mgras.net wrote:
I think the only solution is to make GPC obsolete - either by replacing
GPC by something different but functional equivalent or simply (TM ;-)
by avoiding any polygon clipping in 'fgfs-construct' overall.
For
Hi Cullam,
Curtis Olson wrote:
Just a real quick reply here ... there is some code setup so the
process will kill itself if it runs longer than some period or
consumes too much memory. This was setup because some data cases
would blow up and lead to infinite loops and infinite memory
Martin Spott wrote:
Maxime Guillaud wrote:
I'd be happy to contribute to this. I will start by making available a
write-up of my mapping between the Corine classes and the FG materials,
since I spent quite some time on it.
Oh yes, please. Feel free to re-use as much as you like from
Hi all,
I am in the process of creating custom scenery for France (see
http://wiki.flightgear.org/index.php/Custom_France_Scenery), and I am
looking for advice regarding which material to use for rocky areas in
mountains. I think that the rest of the scenery looks quite fine, but
this
Hi Martin,
Martin Spott wrote:
At the current state, the latest release packages don't know about a
rock surface (material) type and therefore the users of release
packages will be unable to deal with Scenery which contains the such a
type. Thus, in order to ship proper rock surface with the
Martin Spott wrote:
I'm well familiar with reading French - thanks for the pointer !
Apparently these use terms are quite different from those on the EEA
site. This really looks like we should incorporate French CORINE data
into our collection of land cover data for the World Scenery. I'll be
constant from 1e-14 to 1e-12 (patch
attached).
Regards,
Maxime
Maxime Guillaud wrote:
Curtis Olson wrote:
A bucket coordinate of -593:2 suggests that this shapefile may contain
some bogus data. (or there could be a bug leading up to this) but I
believe the portion prior to the : represents
Hi all,
shape-decode has been crashing on me for a certain shapefile and I can
not figure out why. I am using terragear-cs downloaded today from the
GIT repository. The rest of the toolchain runs fine.
shape-decode runs for a while and stops with the following error:
[...]
distance = 239.828
Curtis Olson wrote:
A bucket coordinate of -593:2 suggests that this shapefile may contain
some bogus data. (or there could be a bug leading up to this) but I
believe the portion prior to the : represents a whole degree
coordinate of the bucket, so this should range from -180 to +179 for
Hello,
Following my recent uncovering of detailed landcover information for
France (see
http://www.flightgear.org/forums/viewtopic.php?f=5t=5105sid=c3a960f7f3ee2f652973410a6d06ce9b),
I proceeded to generate custom scenery integrating this data.
Following the tutorial from the wiki
16 matches
Mail list logo
