daveluff wrote:
> I'm still unable to run without a segfault since the new sound system
> was committed. Here is my call stack:
Sigh, it's starting to become a nightmare.
Erik
--
Let Crystal Reports handle the reportin
daveluff wrote:
> Erik Hofman wrote:
>
>> Hi,
>>
>> 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 i
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
Dave wrote
> -Original Message-
> From: daveluff [mailto:davel...@ntlworld.com]
> Sent: 12 November 2009 22:26
> To: FlightGear developers discussions
> Subject: Re: [Flightgear-devel] SoundSystem continued
>
> Alasdair Campbell wrote:
>
> >On Mon, 2009-11-09 at 14:56 +, James Turner
Hallo gang.
While working on figuring out my other texture issues, I've started looking at
doing cliffs for steep surfaces. The idea of automatically assigning triangles
a cliff like texture if they go beyond a certain steepness has come up before.
I've found a few threads where it's been talke
Hi All,
I'm trying some magic ju ju to make Fred re-appear :-). I've put together an
install package for Windows based on today's cvs-head here:
ftp://ftp.abbeytheatre2.org.uk/fgfs/executable/fgsetup-cvs-20090913.exe
It has known bugs in the Route Manager area - sorry. And I have chosen not
to i
On 11/11/2009 03:49 PM, Stuart Buchanan wrote:
>
> Could you put together some text I could add to The Manual please?
Here is a start, based on my still-very-limited understanding
of the situation:
0) The following two files should be distributed with FG:
cat atis.scm
(SayText "temperature o
Hi,
Program received signal SIGSEGV, Segmentation fault.
0x085fff40 in SGGeodesy::SGGeodToCart (geod=..., cart=...) at
SGGeodesy.cxx:119
119 SGGeodesy::SGGeodToCart(const SGGeod& geod, SGVec3& cart)
Current language: auto
The current source language is "auto; currently c++".
(gdb) backtrace f
On Fri, Nov 13, 2009 at 1:34 AM, Gijs de Rooy wrote:
> > Curt Olson wrote:
> > I think we also need a good slogan or motto ... I kind of like:
> >
> > FlightGear: Educate, Entertain, Inspire.
>
> On the FSweekend posters, we had printed out: "Naturally flying is free". I
> like it ;)
>
I think
> > On the FSweekend posters, we had printed out: "Naturally flying is free".
> > I like it ;)
>
> I think this might be a phrase that doesn't quite sounds as smooth in
> English as it probably does in the original Dutch. It could be my warped
> mind, but when I see the words "naturally flying" (
Hi all,
is there a setting in fgfs-construct that sets the run time for a
build. I keep having my process killed and not by the kernel.
Jason
Region point = 151.588, -32.9989, -
Triangulation with options = pczAen
Constructing Delaunay triangulation by divide-and-conquer method.
Delaunay mil
Jason Cox wrote:
> is there a setting in fgfs-construct that sets the run time for a
> build.
Yup. Exit code 137 ?
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--
--
Ok, so a quick scan for the exit code found nothing...
where abouts can I change the time out as I have be searching for a few
days
On Fri, 2009-11-13 at 21:52 +, Martin Spott wrote:
> Jason Cox wrote:
>
> > is there a setting in fgfs-construct that sets the run time for a
> > build.
>
> Y
Jason Cox wrote:
> Ok, so a quick scan for the exit code found nothing...
Ah, that's what I meant:
# ~> fgfs-construct [... parameters ...]
[...]
Killed
# ~> echo $?
> where abouts can I change the time out as I have be searching for a few
> days
Mostly from memory I'd propose to searc
you were right exit code 137
I will check the file as suggested
On Fri, 2009-11-13 at 22:38 +, Martin Spott wrote:
> Jason Cox wrote:
> > Ok, so a quick scan for the exit code found nothing...
>
> Ah, that's what I meant:
>
> # ~> fgfs-construct [... parameters ...]
> [...]
> Killed
>
I have changed the setting for both rlim_cur and rlim_max from 300 to
3
curious though is that the following section of code seems to set it to
4000 and then over write it to 300
Jason
#if defined( __CYGWIN__ ) || defined( __CYGWIN32__ ) ||
defined( _MSC_VER )
// the next bit crash
A problem shared is a problem * 0.5 apparently. With some c++ and nasal
(sneezes, dribbles and a tissue to contain tacticle stuff) then the 1/2
ratio can be rapidly reduced.
So my frustration is with the "scenery" part of FlightGear. Eg can I fly
from Cardiff to Barcelona without scenery disap
On Sat, 2009-11-14 at 10:28 +1100, Jason Cox wrote:
> I have changed the setting for both rlim_cur and rlim_max from 300 to
> 3
> curious though is that the following section of code seems to set it to
> 4000 and then over write it to 300
>
> Jason
>
>
>
> #if defined( __CYGWIN__ ) ||
Hello,
I've been reading through a lot of the TerraGear code after I've read the
center line problem but I'm interested in tackling a different problem. It
doesn't help I don't have an intimate knowledge of C++, nor have I ever
properly compiled TerraGear on Linux... so please bear with me.
Ru
Cullum,
much like yourself I am building higher res scenery.
Long story short, I changed the timeout to build tiles and found that my
scenery blew up just as yours did (http://globelock.menu.nu/fgfs.png)
have you made any progress?
Jason
On Tue, 2009-11-10 at 04:00 -0800, cullam Bruce-Lockhart
20 matches
Mail list logo
