Re: [Flightgear-devel] FlightGear/PLIB/CVS: Enabling 3D Clouds results in Floating point interrupt (SIGFPE) [PATCH]

2007-05-31 Thread Nick Warne
On Thursday 31 May 2007 09:40:47 Steve Hosgood wrote: > >Hi Durk , > >make sure the cloud cache and resolution aren't zero before enabling > > them > > Please (before 0.9.11-pre2), could someone slip in some code to the effect: > > if (cloud_cache == 0 || resolution == 0) > grey_out_menu_i

Re: [Flightgear-devel] FlightGear/PLIB/CVS: Enabling 3D Clouds results in Floating point interrupt (SIGFPE)

2007-05-31 Thread Steve Hosgood
syd & sandy wrote: View->Render Options->Enable 3D Clouds I'm getting a repeated printout saying: "Floating point interrupt (SIGFPE)", and FlightGear freezes. I've installed Simgear-plib (CVS as of yesterday), and FlightGear-Plib source, CVS as of yesterday. System is Linux, Suse 10.2, g

Re: [Flightgear-devel] FlightGear/PLIB/CVS: Enabling 3D Clouds results in Floating point interrupt (SIGFPE)

2007-05-31 Thread syd & sandy
On Thu, 31 May 2007 08:57:15 +0200 Durk Talsma <[EMAIL PROTECTED]> wrote: > Hi Everybody, > > I'm still catching-up in installing a plib based FlightGear, after my crazy > travel schedule the last few weeks. I didn't have the time to check whether > this error has already been reported, but I'm

Re: [Flightgear-devel] FlightGear/PLIB/CVS: Enabling 3D Clouds results in Floating point interrupt (SIGFPE)

2007-05-31 Thread Nick Warne
Hi Durk, On Thursday 31 May 2007 07:57:15 Durk Talsma wrote: > > View->Render Options->Enable 3D Clouds > > I'm getting a repeated printout saying: "Floating point interrupt > (SIGFPE)", and FlightGear freezes. Before you change to 3D clouds, ensure one of the file size cache settings (I forge

[Flightgear-devel] FlightGear/PLIB/CVS: Enabling 3D Clouds results in Floating point interrupt (SIGFPE)

2007-05-30 Thread Durk Talsma
Hi Everybody, I'm still catching-up in installing a plib based FlightGear, after my crazy travel schedule the last few weeks. I didn't have the time to check whether this error has already been reported, but I'm encountering the following problem. Starting-up and running flightgear works just