I've only specified --fg-root=pathtoflightgear . it also returns the
same result with different aircraft.
I'll test it on my home pc ... hopefully it will have a different result
Danie
On Thu, 2005-06-02 at 14:11 +0200, Erik Hofman wrote:
> Danie Heath wrote:
> > Nope ... this is a clean ins
Danie Heath wrote:
Nope ... this is a clean installation directly from the CVS. I haven't
edited any of the files.
What command line options are specified and which aircraft is used.
Also, is it the same behavior for other aircraft types?
Erik
___
Nope ... this is a clean installation directly from the CVS. I haven't
edited any of the files.
But will check them anyway ...
Danie
On Thu, 2005-06-02 at 13:48 +0200, Erik Hofman wrote:
> Danie Heath wrote:
> > Ok, brilliant here's the output with --log-level=info
>
> Unfortunately t
Danie Heath wrote:
Ok, brilliant here's the output with --log-level=info
Unfortunately this doesn't reveal too much. Is there any chance you have
modified an xml configuration file? Sometimes an error in an XML file
can cause a segmentation fault. One way to check them is by loading
Danie Heath wrote:
> I get a segmentation fault when trying to run flightgear. It occurs
> while the splash screen is displayed. I am using :
>
> ./fgfs --fg-root=pathtoflightgear
>
> I have synched with CVS to get the latest source. I am running on a
> Packard Bell B3410 laptop with Fedora Co
Ok, brilliant here's the output with --log-level=info
No type supplied for layer Pitch trim down annunciator assuming
"texture"
No type supplied for layer IN HG Anunciator assuming "texture"
No type supplied for layer hPa Anunciator assuming "texture"
Reading binding property-toggle
Readi
Danie Heath wrote:
Hi guys,
I get a segmentation fault when trying to run flightgear. It occurs
while the splash screen is displayed. I am using :
./fgfs --fg-root=pathtoflightgear
I have synched with CVS to get the latest source. I am running on a
Packard Bell B3410 laptop with Fedora Core
