Now when it comes to debugging stuff like this I'm a newbie.When I select the default c172p aircraft everything works fine. But if I select say the f16 or A-10 then fgfs crashes.Here's the output from gdb.
Loading program into debugger…
Program loaded.sharedlibrary apply-load-rules all
Attaching
Arthur Wiebe wrote:
Now when it comes to debugging stuff like this I'm a newbie.
When I select the default c172p aircraft everything works fine. But if I
select say the f16 or A-10 then fgfs crashes.
Here's the output from gdb.
http://www.codecomments.com/archive242-2004-4-170396.html
The
OK,But then why when I select the A-10 or f16 fgfs crashes? But when selecting the c172p and j3cub there is no problem?I'll do a bit more testing.It almost seems to be a problem with the actual aircraft.
On 11/11/05, Erik Hofman [EMAIL PROTECTED] wrote:
Arthur Wiebe wrote: Now when it comes to
Arthur Wiebe wrote:
OK,
But then why when I select the A-10 or f16 fgfs crashes? But when
selecting the c172p and j3cub there is no problem?
The only commonality between the A-10 and f-16 is the turbine sound file??
Erik
___
Flightgear-devel
I've compiled a list of all the aircraft included in fgfs-base 0.9.9pre3 that do and don't work:+737-.#A-10cl-A-10cl-A-10fl+bo105+c172p-2dpanel+c172p+c310-yasim+c310dpm-3d-c310-3d
OK I found the problem. I hope.In A-10cl-set.xml I removed the following line: splash-textureAircraft/A-10/A-10-splash.rgb/splash-textureAnd it worked. So it seems something is broken in whatever loads these rgb files.
The file does not look corrupted as it opens fine in QuickTime.On 11/11/05,
On Friday 11 Nov 2005 17:35, Erik Hofman wrote:
Arthur Wiebe wrote:
OK,
But then why when I select the A-10 or f16 fgfs crashes? But
when selecting the c172p and j3cub there is no problem?
The only commonality between the A-10 and f-16 is the turbine
sound file??
Erik
Agreed - I
