Board index FlightGear Support Graphics

Boeing 777 multiple screen crash

Graphics issues like: bad framerates, weird colors, OpenGL errors etc. Bad graphics ar usually the result of bad graphics cards or drivers.
Forum rules
In order to help you, we need to know a lot of information. Make sure to include answers to at least the following questions in your initial post.

- what OS (Windows Xp/Vista, Mac etc.) are you running?
- what FlightGear version do you use?
- what graphics card do you have?
- does the problem occur with any aircraft, at any airport?
- is there any output printed to the console (black window)?
- copy&paste your commandline (tick the "Show commandline box on the last page of FGRun or the "Others" section on the Mac launcher).
- please upload a screenshot of the problem.

If you experience FlightGear crashes, please report a bug using the issue tracker (can be also used for feature requests).
To run FlightGear on old computers with bad OpenGL support, please take a look at this wiki article. If you are seeing corrupted/broken textures, please see this article.

Note: If you did not get a reponse, even after 7 days, you may want to check out the FlightGear mailing lists to ask your question there.

Re: Boeing 777 multiple screen crash

Postby legoboyvdlp » Wed Dec 12, 2018 10:29 pm

Hi,
What is the problem with 2018.3?
I don't think anyone else has reported any problems so far, please let us know what went wrong so it can be resolved if necessary :)
User avatar
legoboyvdlp
 
Posts: 6407
Joined: Sat Jul 26, 2014 1:28 am
Callsign: YV-LEGO
Version: 2018.3.1
OS: Windows 10 HP

Re: Boeing 777 multiple screen crash

Postby wkitty42 » Wed Dec 12, 2018 10:37 pm

SurferTim wrote in Tue Dec 11, 2018 9:28 pm:
legoboyvdlp wrote in Tue Dec 11, 2018 8:12 pm:Hi,
Maybe you can post the log in pastebin and send us the link?

Good idea. Uploaded to dropbox.
https://www.dropbox.com/s/0d6c9w35009u6ub/fgfs.log?dl=0

here's why you can't do multiple screens...
Code: Select all
opengl:3:/build/flightgear-nFZcIF/flightgear-2018.2.2/src/Viewer/fg_os_osgviewer.cxx:209:Error: Unable to open display ":0.3".

opengl:3:/build/flightgear-nFZcIF/flightgear-2018.2.2/src/Viewer/fg_os_osgviewer.cxx:209:Error: Unable to open display ":0.2".

fix that and that should work...

The last thing in the log window is
double free or corrupted

we need to see the rest of that entry... it is not in the log file you posted...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 5124
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Boeing 777 multiple screen crash

Postby SurferTim » Wed Dec 12, 2018 11:16 pm

here's why you can't do multiple screens...
Code: Select all
opengl:3:/build/flightgear-nFZcIF/flightgear-2018.2.2/src/Viewer/fg_os_osgviewer.cxx:209:Error: Unable to open display ":0.3".

opengl:3:/build/flightgear-nFZcIF/flightgear-2018.2.2/src/Viewer/fg_os_osgviewer.cxx:209:Error: Unable to open display ":0.2".

fix that and that should work...

The last thing in the log window is
double free or corrupted
we need to see the rest of that entry... it is not in the log file you posted...

There is no "rest of that entry". At that point the program has crashed and exited as if I had quit, and that is the last entry.

Like I said before, I have no problem with multiple displays with the Citation-X. At first, I had no problems with the B777 until I got to 200 feet agl.
Fly low, fly slow, land on a dime. Twin Otter.
SurferTim
 
Posts: 77
Joined: Sun Dec 09, 2018 5:49 pm
Location: Miramar Beach, FL
Callsign: N2ST/Pirate
Version: 2018-3-1
OS: Ubuntu 18.04

Re: Boeing 777 multiple screen crash

Postby wkitty42 » Thu Dec 13, 2018 12:31 am

if this is on linux, look and see if you can find a core file... probably in your FG's bin directory with the FG binary... if you can find it, we can look at it with gdb and see what happened...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 5124
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Boeing 777 multiple screen crash

Postby SurferTim » Thu Dec 13, 2018 12:50 am

The fgfs executable is in /usr/games. Should I upload it to dropbox?
Fly low, fly slow, land on a dime. Twin Otter.
SurferTim
 
Posts: 77
Joined: Sun Dec 09, 2018 5:49 pm
Location: Miramar Beach, FL
Callsign: N2ST/Pirate
Version: 2018-3-1
OS: Ubuntu 18.04

Re: Boeing 777 multiple screen crash

Postby SurferTim » Thu Dec 13, 2018 1:15 pm

OK, I'm going through the start messages. I've turned this:
Code: Select all
PNG lib warning : iCCP: known incorrect sRGB profile
PNG lib warning : iCCP: known incorrect sRGB profile
PNG lib warning : iCCP: known incorrect sRGB profile
Scaling image '/usr/share/games/flightgear/Aircraft/777/Models/Textures/Cockpit/tcas-digits.png' from (573,255) to (512,256)
Scaling image '/usr/share/games/flightgear/Aircraft/777/Models/Instruments/EFB/Displays/Blank_Test.jpg' from (511,695) to (512,512)
Scaling image '/usr/share/games/flightgear/Aircraft/777/Models/Instruments/EFB/Displays/Keyboard_1.jpg' from (511,695) to (512,512)
Scaling image '/usr/share/games/flightgear/Aircraft/777/Models/Instruments/EFB/manual.jpg' from (1024,11370) to (1024,8192)

to this by rescaling the images with GIMP:
Code: Select all
PNG lib warning : iCCP: known incorrect sRGB profile
PNG lib warning : iCCP: known incorrect sRGB profile

The log shows this:
Code: Select all
opengl:3:/build/flightgear-nFZcIF/flightgear-2018.2.2/src/Viewer/fg_os_osgviewer.cxx:209:
opengl:4:/build/flightgear-nFZcIF/flightgear-2018.2.2/src/Viewer/fg_os_osgviewer.cxx:209:PNG lib warning : iCCP: known incorrect sRGB profile

opengl:4:/build/flightgear-nFZcIF/flightgear-2018.2.2/src/Viewer/fg_os_osgviewer.cxx:209:PNG lib warning : iCCP: known incorrect sRGB profile

What needs to be done to eliminate these messages?
Fly low, fly slow, land on a dime. Twin Otter.
SurferTim
 
Posts: 77
Joined: Sun Dec 09, 2018 5:49 pm
Location: Miramar Beach, FL
Callsign: N2ST/Pirate
Version: 2018-3-1
OS: Ubuntu 18.04

Re: Boeing 777 multiple screen crash

Postby SurferTim » Fri Dec 14, 2018 2:38 pm

It may be my Intel i7 16GB RAM is just not up to the task. I ran "top" and the single screen is running at 98% CPU. It appears I need more butt for multiple screens. Anybody know what CPU can keep up?
Fly low, fly slow, land on a dime. Twin Otter.
SurferTim
 
Posts: 77
Joined: Sun Dec 09, 2018 5:49 pm
Location: Miramar Beach, FL
Callsign: N2ST/Pirate
Version: 2018-3-1
OS: Ubuntu 18.04

Re: Boeing 777 multiple screen crash

Postby wkitty42 » Fri Dec 14, 2018 11:25 pm

SurferTim wrote in Thu Dec 13, 2018 12:50 am:The fgfs executable is in /usr/games. Should I upload it to dropbox?

not the FG executable... the core file if you found one... depending on the system, it may be found elsewhere but i don't know where to tell you to look... maybe in /tmp or /var/tmp but it might be better to run a full disk search looking for a file named "core" (without the quotes) and see if any you find have a timestamp matching the time of your crash... that core file should be all that's needed to at least see the error and the backtrace...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 5124
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Boeing 777 multiple screen crash

Postby wkitty42 » Fri Dec 14, 2018 11:31 pm

SurferTim wrote in Thu Dec 13, 2018 1:15 pm:
Code: Select all
Scaling image '/usr/share/games/flightgear/Aircraft/777/Models/Textures/Cockpit/tcas-digits.png' from (573,255) to (512,256)
Scaling image '/usr/share/games/flightgear/Aircraft/777/Models/Instruments/EFB/Displays/Blank_Test.jpg' from (511,695) to (512,512)
Scaling image '/usr/share/games/flightgear/Aircraft/777/Models/Instruments/EFB/Displays/Keyboard_1.jpg' from (511,695) to (512,512)
Scaling image '/usr/share/games/flightgear/Aircraft/777/Models/Instruments/EFB/manual.jpg' from (1024,11370) to (1024,8192)

yes, texture files should be a power of 2 in size... might want to let the devs of this craft know about this...

SurferTim wrote in Thu Dec 13, 2018 1:15 pm:
Code: Select all
PNG lib warning : iCCP: known incorrect sRGB profile
PNG lib warning : iCCP: known incorrect sRGB profile
[...]What needs to be done to eliminate these messages?

this came about about a year or so ago and is due to that graphics library getting stricter... these are safe to ignore... i do not know what the exact fix is that needs to be made to the graphics files, though... i think i recall someone saying they stripped that stuff off of the graphic file and it didn't change anything other than getting rid of the message since the problem no longer existed... that was way back when these log notices first appeared and were being discussed around this community...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 5124
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Boeing 777 multiple screen crash

Postby wkitty42 » Fri Dec 14, 2018 11:37 pm

SurferTim wrote in Fri Dec 14, 2018 2:38 pm:It may be my Intel i7 16GB RAM is just not up to the task. I ran "top" and the single screen is running at 98% CPU. It appears I need more butt for multiple screens. Anybody know what CPU can keep up?

i have a poor video card (NVIDIA GT-730) but it is running on an AMD FX-8350 4ghz 8-core cpu... i, too, have 16gig of RAM... my main problem is FPS and that's due to my weak video card... it works and i'm able to fly but it could be a ""bit"" better...

FG is CPU bound for most systems... i don't think i've seen any posts in the years since i've been here that showed any GPU bottlenecks... there are some things that can be done to help tone down the CPU bottleneck, though... turning off random buildings, the new OSM stuff and AI Traffic as well as using basic weather instead of detailed weather and other similar features that really add to the sim...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 5124
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Boeing 777 multiple screen crash

Postby SurferTim » Sat Dec 15, 2018 12:03 am

@wkitty42: I found no core file for the time of the crash anywhere on the disk.

This is the last line in the fgfs.log
Code: Select all
terrain:3:/build/simgear-mm91nf/simgear-2018.2.2/simgear/scene/tgdb/ReaderWriterSTG.cxx:517:  Generating ocean tile: w160n20/w159n20/351165

This time it just froze after I used autostart. It didn't exit, just froze.
Fly low, fly slow, land on a dime. Twin Otter.
SurferTim
 
Posts: 77
Joined: Sun Dec 09, 2018 5:49 pm
Location: Miramar Beach, FL
Callsign: N2ST/Pirate
Version: 2018-3-1
OS: Ubuntu 18.04

Re: Boeing 777 multiple screen crash

Postby wkitty42 » Sat Dec 15, 2018 5:13 pm

ok... do you run your FG from the console command line (eg: ~/flightgear-dev/next/run_fgfs.sh --launcher) or from an icon you click?
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 5124
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Boeing 777 multiple screen crash

Postby SurferTim » Sat Dec 15, 2018 6:27 pm

From a terminal
Code: Select all
fgrun


Edit: Also tried
Code: Select all
fgfs --aircraft=777-300 --config=/home/tim/Downloads/config.xml

Opens the displays, but freezes when I autostart.
Fly low, fly slow, land on a dime. Twin Otter.
SurferTim
 
Posts: 77
Joined: Sun Dec 09, 2018 5:49 pm
Location: Miramar Beach, FL
Callsign: N2ST/Pirate
Version: 2018-3-1
OS: Ubuntu 18.04

Re: Boeing 777 multiple screen crash

Postby wkitty42 » Sun Dec 16, 2018 6:12 pm

oh... ok... if you were using the new launcher instead of the unsupported and ancient fgrun, i'd show you how to tee the console output to a log file and then we could see what's going on a little easier... it should certainly record the crash stuff...

when you try the second way and it freezes, you should be able to ALT-TAB to the command console you opened FG in... in there you should easily see the output... then you could run ps and find the FG PID to kill FG with... but we gotta see that error or there's nothing we can do to help :(
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 5124
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Boeing 777 multiple screen crash

Postby legoboyvdlp » Sun Dec 16, 2018 7:16 pm

If you are using FGRUN, what version of flightgear are you on?
User avatar
legoboyvdlp
 
Posts: 6407
Joined: Sat Jul 26, 2014 1:28 am
Callsign: YV-LEGO
Version: 2018.3.1
OS: Windows 10 HP

PreviousNext

Return to Graphics

Who is online

Users browsing this forum: No registered users and 1 guest