Board index FlightGear Release candidates 2.8

.DDS Support? [Installation trouble due to new(?) feature]  Topic is solved

This is the archive of topics about the 2.8 release candidates.

Re: .DDS Support? [Installation trouble due to new(?) featur

Postby kyokoyama » Fri Jul 13, 2012 10:07 pm

Gijs wrote in Fri Jul 13, 2012 7:17 pm:What's --generic=socket,in,5,,5500,tcp, doing there? It lacks a protocol file at the end (after tcp,). Go to Advanced > Input/Output on the last page of FGRun and remove it.

I think that's from an old version of FGcom while it still required that command line... I'll see how it goes after removal.

EDIT
That got rid of the mystery message, thanks, but FG still crashes.

This time, I used the 777 for debug. Startup sounds are there, but once the splash screen is supposed to fade away, it crashes again like before.

Here's the console message again:
Code: Select all
Dir::children: FindFirstFile failed:C:/Program Files (x86)/FlightGear/data/Aircr
aft
Failed to create beacon for unknown runway 'KONT 26L OM'.
Failed to create beacon for unknown runway 'KONT 26R OM'.
Failed to create beacon for unknown runway 'KSAV 01  OM'.
Failed to create beacon for unknown runway 'KSAV 10  OM'.
Failed to create beacon for unknown runway 'PAYA 11  OM'.
Failed to create beacon for unknown runway 'WARQ 26  OM'.
Failed to create beacon for unknown runway 'WARR 10  OM'.
Failed to create beacon for unknown runway 'ZULS 27R OM'.
Failed to create beacon for unknown runway 'EDDB 07  MM'.
Failed to create beacon for unknown runway 'EDDB 25  MM'.
Failed to create beacon for unknown runway 'KIAD 01C MM'.
Failed to create beacon for unknown runway 'KONT 08L MM'.
Failed to create beacon for unknown runway 'KONT 26L MM'.
Failed to create beacon for unknown runway 'KONT 26R MM'.
Failed to create beacon for unknown runway 'KSAV 01  MM'.
Failed to create beacon for unknown runway 'KSAV 10  MM'.
Failed to create beacon for unknown runway 'PAED 06  MM'.
Failed to create beacon for unknown runway 'PAYA 11  MM'.
Failed to create beacon for unknown runway 'WADD 27  MM'.
Failed to create beacon for unknown runway 'WALL 25  MM'.
Failed to create beacon for unknown runway 'WAOO 10  MM'.
Failed to create beacon for unknown runway 'WAOP 34  MM'.
Failed to create beacon for unknown runway 'WARJ 09  MM'.
Failed to create beacon for unknown runway 'WARQ 26  MM'.
Failed to create beacon for unknown runway 'WARR 10  MM'.
Failed to create beacon for unknown runway 'WIDD 04  MM'.
Failed to create beacon for unknown runway 'WIHH 24  MM'.
Failed to create beacon for unknown runway 'KIAD 19C IM'.
Failed to create beacon for unknown runway 'KONT 26L IM'.
Skipping bad material entry params
Dir::children: FindFirstFile failed:C:/Program Files (x86)/FlightGear/data/Aircr
aft/777/gui/dialogs
Failed to tie property /environment/attention to object methods
Duplicate autopilot component MetarController:layer:wind-from-heading-deg, renam
ed to MetarController:layer:wind-from-heading-deg_0
Duplicate autopilot component MetarController:layer:wind-from-heading-deg, renam
ed to MetarController:layer:wind-from-heading-deg_1
Duplicate autopilot component MetarController:layer:wind-from-heading-deg, renam
ed to MetarController:layer:wind-from-heading-deg_2
Duplicate autopilot component MetarController:layer:wind-from-heading-deg, renam
ed to MetarController:layer:wind-from-heading-deg_3
Duplicate autopilot component MetarController:layer:wind-from-heading-deg, renam
ed to MetarController:layer:wind-from-heading-deg_4
Duplicate autopilot component MetarController:layer:wind-speed-kt, renamed to Me
tarController:layer:wind-speed-kt_0
Duplicate autopilot component MetarController:layer:wind-speed-kt, renamed to Me
tarController:layer:wind-speed-kt_1
Duplicate autopilot component MetarController:layer:wind-speed-kt, renamed to Me
tarController:layer:wind-speed-kt_2
Duplicate autopilot component MetarController:layer:wind-speed-kt, renamed to Me
tarController:layer:wind-speed-kt_3
Duplicate autopilot component MetarController:layer:wind-speed-kt, renamed to Me
tarController:layer:wind-speed-kt_4
Duplicate autopilot component MetarController:clouds:altitude_interpolate, renam
ed to MetarController:clouds:altitude_interpolate_0
Duplicate autopilot component MetarController:clouds:altitude_interpolate, renam
ed to MetarController:clouds:altitude_interpolate_1
Duplicate autopilot component MetarController:clouds:altitude_interpolate, renam
ed to MetarController:clouds:altitude_interpolate_2
Duplicate autopilot component MetarController:clouds:altitude_interpolate, renam
ed to MetarController:clouds:altitude_interpolate_3
Duplicate autopilot component MetarController:clouds:thickness, renamed to Metar
Controller:clouds:thickness_0
Duplicate autopilot component MetarController:clouds:thickness, renamed to Metar
Controller:clouds:thickness_1
Duplicate autopilot component MetarController:clouds:thickness, renamed to Metar
Controller:clouds:thickness_2
Duplicate autopilot component MetarController:clouds:thickness, renamed to Metar
Controller:clouds:thickness_3
Duplicate autopilot component MetarController:clouds:coverage, renamed to MetarC
ontroller:clouds:coverage_0
Duplicate autopilot component MetarController:clouds:coverage, renamed to MetarC
ontroller:clouds:coverage_1
Duplicate autopilot component MetarController:clouds:coverage, renamed to MetarC
ontroller:clouds:coverage_2
Duplicate autopilot component MetarController:clouds:coverage, renamed to MetarC
ontroller:clouds:coverage_3
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp/ID
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp/ID
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp/ID
Animated jetways ... initialized
Warning Electronic System ... ok
loading scenario 'nimitz_demo'
Failed to tie property /ai[0]/models[0]/carrier[0]/controls[0]/constants[0]/rudd
er[0]
Failed to tie property /ai[0]/models[0]/carrier[1]/controls[0]/constants[0]/rudd
er[0]
Image "C:/Program Files (x86)/FlightGear/data/Textures.high/Terrain/snow3.dds"
uses compressed textures which cannot be supported on some systems.
Please decompress this texture for improved portability.
Image "C:/Program Files (x86)/FlightGear/data/Textures.high/Terrain/transition1.
dds"
uses compressed textures which cannot be supported on some systems.
Please decompress this texture for improved portability.
Image "C:/Program Files (x86)/FlightGear/data/Textures.high/Terrain/grass12.dds"

uses compressed textures which cannot be supported on some systems.
Please decompress this texture for improved portability.
fgUntie: unknown property /engines/engine[0]/mp-osi
fgUntie: unknown property /engines/engine[0]/oil-temperature-degf
fgUntie: unknown property /engines/engine[1]/mp-osi
fgUntie: unknown property /engines/engine[1]/oil-temperature-degf
fgUntie: unknown property /engines/engine[2]/fuel-flow-gph
fgUntie: unknown property /engines/engine[2]/rpm
fgUntie: unknown property /engines/engine[2]/mp-osi
fgUntie: unknown property /engines/engine[2]/egt-degf
fgUntie: unknown property /engines/engine[2]/oil-temperature-degf
Electrical System ... ok
AFDS System ... check
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp[1]/longit
ude-deg
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp[1]/longit
ude-deg
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp[1]/longit
ude-deg
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp[1]/latitu
de-deg
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp[1]/latitu
de-deg
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp[1]/latitu
de-deg
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp[1]/altitu
de-ft
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp[1]/altitu
de-ft
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp[1]/altitu
de-ft


Beacon creation, auto-compressed textures, autopilot system, GPS, AI and weather control... I'm sorry to keep bothering y'all, but I'm still completely stumped.
Any other ideas?
Look for "B-BIRD" "N127KY" or "AVA0004" -that's me.

Despite having over 1700 posts here, I am not even close to being the most skilled guy here... I'm just words and bad drawing, not experience. :P
kyokoyama
 
Posts: 1988
Joined: Sun May 03, 2009 2:16 am
Location: Earth
Callsign: B-BIRD, N127KY
Version: 2.12.1
OS: Windows Vista

Re: .DDS Support? [Installation trouble due to new(?) featur

Postby i4dnf » Sat Jul 14, 2012 2:12 am

Just a hunch, can you check memory usage of the flightgear process, and see how much it's using when it crashes?
i4dnf
Retired
 
Posts: 745
Joined: Wed Sep 09, 2009 7:17 am
Location: LRBS
Callsign: YR-I4D
Version: GIT
OS: Gentoo Linux ~amd64

Re: .DDS Support? [Installation trouble due to new(?) featur

Postby kyokoyama » Sat Jul 14, 2012 4:02 am

CPU usage spikes at ~25% when I clicked "run", but then it hovers at 15~20% most of the time. However, it spiked to about 50% for a few instances.

However, the physical memory use (RAM) went from 1.60GB at startup to 2.23GB at the moment it crashed... (this dropped to 1.70GB once I stopped the crashed simulator window)
I have no idea how to find out about the GPU's memory usage, though. How could I do this? (or rather, is that important to begin with?)
Look for "B-BIRD" "N127KY" or "AVA0004" -that's me.

Despite having over 1700 posts here, I am not even close to being the most skilled guy here... I'm just words and bad drawing, not experience. :P
kyokoyama
 
Posts: 1988
Joined: Sun May 03, 2009 2:16 am
Location: Earth
Callsign: B-BIRD, N127KY
Version: 2.12.1
OS: Windows Vista

Re: .DDS Support? [Installation trouble due to new(?) featur

Postby ThorstenB » Sat Jul 14, 2012 7:43 am

I don't think the standard log output helps in this case.
Can you try to generate some sort of crash log - "Dr. Watson" did the job for earlier Windows versions (up to XP). I think there's some kind of new method for Vista and newer.
We'd be able to see exactly where in the code your process is crashing then.
User avatar
ThorstenB
 
Posts: 160
Joined: Fri Nov 19, 2010 9:49 am
Location: Germany
Callsign: D-TB7
Version: GIT
OS: openSUSE

Re: .DDS Support? [Installation trouble due to new(?) featur

Postby i4dnf » Sat Jul 14, 2012 8:26 am

2,23GB looks like the memory limit for 32bit processes on windows.
Try choosing another start position.
If it starts then, try to lower the random buildings density (and the tree density) in View-> rendering options.
i4dnf
Retired
 
Posts: 745
Joined: Wed Sep 09, 2009 7:17 am
Location: LRBS
Callsign: YR-I4D
Version: GIT
OS: Gentoo Linux ~amd64

Re: .DDS Support? [Installation trouble due to new(?) featur

Postby ThorstenB » Sat Jul 14, 2012 9:13 am

i4dnf wrote in Sat Jul 14, 2012 8:26 am:2,23GB looks like the memory limit for 32bit processes on windows.
Try choosing another start position.
If it starts then, try to lower the random buildings density (and the tree density) in View-> rendering options.

Or add this to your command-line:
Code: Select all
--prop:bool:/sim/rendering/random-buildings=false
User avatar
ThorstenB
 
Posts: 160
Joined: Fri Nov 19, 2010 9:49 am
Location: Germany
Callsign: D-TB7
Version: GIT
OS: openSUSE

Re: .DDS Support? [Installation trouble due to new(?) featur

Postby kyokoyama » Sat Jul 14, 2012 3:57 pm

Alright, I used TBPB (my testing airport; I have old TerraSync data for there that should still work) instead of KNUQ as before, and turned random buildings off.
Still crashes mysteriously.

I got the dump file and the report.wer in one ZIP file at the link below. This is what you all meant, right?
http://www.mediafire.com/?3lwhbrd5dd9wdu7
Look for "B-BIRD" "N127KY" or "AVA0004" -that's me.

Despite having over 1700 posts here, I am not even close to being the most skilled guy here... I'm just words and bad drawing, not experience. :P
kyokoyama
 
Posts: 1988
Joined: Sun May 03, 2009 2:16 am
Location: Earth
Callsign: B-BIRD, N127KY
Version: 2.12.1
OS: Windows Vista

Re: .DDS Support? [Installation trouble due to new(?) featur

Postby kyokoyama » Sun Jul 15, 2012 11:16 pm

UPDATE
I tried the new 2.8.0 RC3 release... but the same problem is STILL there.

Here's the console message:
Code: Select all
Dir::children: FindFirstFile failed:C:/Program Files (x86)/FlightGear/data/Aircr
aft
Failed to create beacon for unknown runway 'KONT 26L OM'.
Failed to create beacon for unknown runway 'KONT 26R OM'.
Failed to create beacon for unknown runway 'KSAV 01  OM'.
Failed to create beacon for unknown runway 'KSAV 10  OM'.
Failed to create beacon for unknown runway 'PAYA 11  OM'.
Failed to create beacon for unknown runway 'WARQ 26  OM'.
Failed to create beacon for unknown runway 'WARR 10  OM'.
Failed to create beacon for unknown runway 'ZULS 27R OM'.
Failed to create beacon for unknown runway 'EDDB 07  MM'.
Failed to create beacon for unknown runway 'EDDB 25  MM'.
Failed to create beacon for unknown runway 'KIAD 01C MM'.
Failed to create beacon for unknown runway 'KONT 08L MM'.
Failed to create beacon for unknown runway 'KONT 26L MM'.
Failed to create beacon for unknown runway 'KONT 26R MM'.
Failed to create beacon for unknown runway 'KSAV 01  MM'.
Failed to create beacon for unknown runway 'KSAV 10  MM'.
Failed to create beacon for unknown runway 'PAED 06  MM'.
Failed to create beacon for unknown runway 'PAYA 11  MM'.
Failed to create beacon for unknown runway 'WADD 27  MM'.
Failed to create beacon for unknown runway 'WALL 25  MM'.
Failed to create beacon for unknown runway 'WAOO 10  MM'.
Failed to create beacon for unknown runway 'WAOP 34  MM'.
Failed to create beacon for unknown runway 'WARJ 09  MM'.
Failed to create beacon for unknown runway 'WARQ 26  MM'.
Failed to create beacon for unknown runway 'WARR 10  MM'.
Failed to create beacon for unknown runway 'WIDD 04  MM'.
Failed to create beacon for unknown runway 'WIHH 24  MM'.
Failed to create beacon for unknown runway 'KIAD 19C IM'.
Failed to create beacon for unknown runway 'KONT 26L IM'.
Skipping bad material entry params
Dir::children: FindFirstFile failed:C:/Program Files (x86)/FlightGear/data/Aircr
aft/777/gui/dialogs
Failed to tie property /environment/attention to object methods
Duplicate autopilot component MetarController:layer:wind-from-heading-deg, renam
ed to MetarController:layer:wind-from-heading-deg_0
Duplicate autopilot component MetarController:layer:wind-from-heading-deg, renam
ed to MetarController:layer:wind-from-heading-deg_1
Duplicate autopilot component MetarController:layer:wind-from-heading-deg, renam
ed to MetarController:layer:wind-from-heading-deg_2
Duplicate autopilot component MetarController:layer:wind-from-heading-deg, renam
ed to MetarController:layer:wind-from-heading-deg_3
Duplicate autopilot component MetarController:layer:wind-from-heading-deg, renam
ed to MetarController:layer:wind-from-heading-deg_4
Duplicate autopilot component MetarController:layer:wind-speed-kt, renamed to Me
tarController:layer:wind-speed-kt_0
Duplicate autopilot component MetarController:layer:wind-speed-kt, renamed to Me
tarController:layer:wind-speed-kt_1
Duplicate autopilot component MetarController:layer:wind-speed-kt, renamed to Me
tarController:layer:wind-speed-kt_2
Duplicate autopilot component MetarController:layer:wind-speed-kt, renamed to Me
tarController:layer:wind-speed-kt_3
Duplicate autopilot component MetarController:layer:wind-speed-kt, renamed to Me
tarController:layer:wind-speed-kt_4
Duplicate autopilot component MetarController:clouds:altitude_interpolate, renam
ed to MetarController:clouds:altitude_interpolate_0
Duplicate autopilot component MetarController:clouds:altitude_interpolate, renam
ed to MetarController:clouds:altitude_interpolate_1
Duplicate autopilot component MetarController:clouds:altitude_interpolate, renam
ed to MetarController:clouds:altitude_interpolate_2
Duplicate autopilot component MetarController:clouds:altitude_interpolate, renam
ed to MetarController:clouds:altitude_interpolate_3
Duplicate autopilot component MetarController:clouds:thickness, renamed to Metar
Controller:clouds:thickness_0
Duplicate autopilot component MetarController:clouds:thickness, renamed to Metar
Controller:clouds:thickness_1
Duplicate autopilot component MetarController:clouds:thickness, renamed to Metar
Controller:clouds:thickness_2
Duplicate autopilot component MetarController:clouds:thickness, renamed to Metar
Controller:clouds:thickness_3
Duplicate autopilot component MetarController:clouds:coverage, renamed to MetarC
ontroller:clouds:coverage_0
Duplicate autopilot component MetarController:clouds:coverage, renamed to MetarC
ontroller:clouds:coverage_1
Duplicate autopilot component MetarController:clouds:coverage, renamed to MetarC
ontroller:clouds:coverage_2
Duplicate autopilot component MetarController:clouds:coverage, renamed to MetarC
ontroller:clouds:coverage_3
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp/ID
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp/ID
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp/ID
Animated jetways ... initialized
Warning Electronic System ... ok
loading scenario 'nimitz_demo'
Failed to tie property /ai[0]/models[0]/carrier[0]/controls[0]/constants[0]/rudd
er[0]
Failed to tie property /ai[0]/models[0]/carrier[1]/controls[0]/constants[0]/rudd
er[0]
fgUntie: unknown property /engines/engine[0]/mp-osi
fgUntie: unknown property /engines/engine[0]/oil-temperature-degf
fgUntie: unknown property /engines/engine[1]/mp-osi
fgUntie: unknown property /engines/engine[1]/oil-temperature-degf
fgUntie: unknown property /engines/engine[2]/fuel-flow-gph
fgUntie: unknown property /engines/engine[2]/rpm
fgUntie: unknown property /engines/engine[2]/mp-osi
fgUntie: unknown property /engines/engine[2]/egt-degf
fgUntie: unknown property /engines/engine[2]/oil-temperature-degf
Electrical System ... ok
AFDS System ... check
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp[1]/longit
ude-deg
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp[1]/longit
ude-deg
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp[1]/longit
ude-deg
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp[1]/latitu
de-deg
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp[1]/latitu
de-deg
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp[1]/latitu
de-deg
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp[1]/altitu
de-ft
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp[1]/altitu
de-ft
GPS: someone accessed a deprecated property:/instrumentation/gps/wp/wp[1]/altitu
de-ft

Look for "B-BIRD" "N127KY" or "AVA0004" -that's me.

Despite having over 1700 posts here, I am not even close to being the most skilled guy here... I'm just words and bad drawing, not experience. :P
kyokoyama
 
Posts: 1988
Joined: Sun May 03, 2009 2:16 am
Location: Earth
Callsign: B-BIRD, N127KY
Version: 2.12.1
OS: Windows Vista

Re: .DDS Support? [Installation trouble due to new(?) featur  

Postby kyokoyama » Sat Jul 21, 2012 4:28 pm

https://code.google.com/p/flightgear-bugs/issues/detail?id=807
Thanks to (I think this is) Brett, I finally got the problem fixed!

Long story short, after running directly from the command line and running some tests, I figured out the shaders were the true cause of this problem; I had to update the AMD (ATI) Catalyst software to version 11.4 (there's some kind of compatibility problem with versions 11.5 and above, apparently?) -this instantly fixed the problem, and even gave me better rendering performance than in 2.6.

Thank you! :D
Look for "B-BIRD" "N127KY" or "AVA0004" -that's me.

Despite having over 1700 posts here, I am not even close to being the most skilled guy here... I'm just words and bad drawing, not experience. :P
kyokoyama
 
Posts: 1988
Joined: Sun May 03, 2009 2:16 am
Location: Earth
Callsign: B-BIRD, N127KY
Version: 2.12.1
OS: Windows Vista

Previous

Return to 2.8

Who is online

Users browsing this forum: No registered users and 1 guest