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.

Boeing 777 multiple screen crash

Postby SurferTim » Mon Dec 10, 2018 4:08 pm

I have a problem using two screens (camera views) with a B777 downloaded from the Flightgear aircraft page. I have very good experience with a single screen. Autopilot, Route manager, etc works great! I'm an ex-air traffic controller from Los Angeles Center, so IFR flight is no problem. I found a config.xml file that works great with a Citation-X, but the 777 crashes when I get to 200 feet on climbout. Any idea where I would start troubleshooting the aircraft setup? I would take a sceenshot, but the Flightgear program aborts and closes at 200 feet.

Dell i7, 16GB memory, 2TB hard drive, NVidia P600 graphics card.
Ubuntu 18.04 OS with latest updates and NVidia graphics driver installed.
Flightgear 2018-2-2

Edit: Here is the log window output:
Code: Select all
FlightGear:  Version 2018.2.2
FlightGear:  Build Type Dev
Built with GNU C++ version 7.3
Jenkins number/ID 0:none
Aircraft does not specify a minimum FG version: please add one at /sim/minimum-fg-version
Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyStarting automatic scenery download/synchronization to '/home/tim/.fgfs/TerraSync'.
Cannot find image file ""
Cannot find image file ""
Volcanic activity off.
This aircraft uses yasim version 'YASIM_VERSION_32' (1)

This aircraft does not use the latest yasim configuration version.
YASim warning: possible convergence problem.
Gtk-Message: 10:18:53.812: GtkDialog mapped without a transient parent. This is discouraged.
going to read flight-plan from:Path "/home/tim/.fgfs/Export/sfolax"
no procedures data available for KLAX
GPS saw route-manager flight-plan replaced.
route manager, current-wp is now -1
route manager, current-wp is now 0
GPS::route activated, switching to LEG mode
route-manager, activate route ok
route manager, current-wp is now 1
Last edited by SurferTim on Mon Dec 10, 2018 4:27 pm, edited 1 time in total.
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 HTLocal » Mon Dec 10, 2018 4:27 pm

Hi SurferTim,
welcome to the forums. I love to watch ATC on youtube :)

First of all, I would recommend updating to the brand new 2018-3-1 release, maybe that'll already fix your problem.
Otherwise I'm not quite sure I understand the symptoms. So you have 2 displays on your computer?
Maybe you could also share the xml that you mentioned so we can see what it tries to achieve.
HTLocal
 
Posts: 10
Joined: Sun Dec 02, 2018 11:48 am

Re: Boeing 777 multiple screen crash

Postby SurferTim » Mon Dec 10, 2018 4:35 pm

Thanks for your quick reply. I don't see a 2018-3-1 version for Ubuntu. There is a simgear 2018-3-1 available. Is that similar?

The symptoms are simple. I start Flightgear just as single screen/camera. Everything ok on both displays. I take off and at 200 feet, Flightgear aborts and closes, just as if I had selected "exit". Like I said above, it works fine with the Citation.

Edit: I tried different airports and the fail always occurs at 200 feet agl, no matter what airport elevation.

Here is the config.xml contents.
Code: Select all
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<PropertyList>
  <sim>
    <menubar>
      <visibility type="bool">false</visibility>
    </menubar>
    <frame-rate-throttle-hz type="double">25</frame-rate-throttle-hz>

    <view n="0">
      <config>
        <pitch-offset-deg>0.0</pitch-offset-deg>
      </config>
    </view>

    <rendering>
      <draw-mask>
        <aircraft type="bool">true</aircraft>
      </draw-mask>

      <!-- multithreading-mode>AutomaticSelection</multithreading-mode-->
      <!--multithreading-mode>SingleThreaded</multithreading-mode-->
      <!-- multithreading-mode>DrawThreadPerContext</multithreading-mode -->
      <multithreading-mode>CullDrawThreadPerContext</multithreading-mode>
      <!-- multithreading-mode>CullThreadPerCameraDrawThreadPerContext</multithreading-mode-->

      <camera-group>

        <window>
          <name type="string">Front</name>
          <host-name type="string"></host-name>
          <display>0</display>
          <screen>3</screen>
          <fullscreen type = "bool">false</fullscreen>
          <decoration type = "bool">false</decoration>
          <x>0</x>
          <y>0</y>
          <width>3840</width>
          <height>1080</height>
        </window>
<!--
        <window>
          <name type="string">Left</name>
          <host-name type="string"></host-name>
          <display>0</display>
          <screen>1</screen>
          <fullscreen type = "bool">false</fullscreen>
          <decoration type = "bool">false</decoration>
          <x>0</x>
          <y>0</y>
          <width>3840</width>
          <height>1200</height>
        </window>
-->
        <window>
          <name type="string">HalfLeft</name>
          <host-name type="string"></host-name>
          <display>0</display>
          <screen>2</screen>
          <fullscreen type = "bool">false</fullscreen>
          <decoration type = "bool">false</decoration>
          <x>0</x>
          <y>0</y>
          <width>1920</width>
          <height>1080</height>
        </window>


<!--
        <window>
          <name type="string">HalfRight</name>
          <host-name type="string"></host-name>
          <display>0</display>
          <screen>4</screen>
          <fullscreen type = "bool">false</fullscreen>
          <decoration type = "bool">false</decoration>
          <x>0</x>
          <y>0</y>
          <width>4096</width>
          <height>1152</height>
        </window>
-->

        <gui>
          <window>
            <name type="string">Front</name>
          </window>
        </gui>

        <camera>
          <name type="string">FrontLeft</name>
          <window>
           <name>Front</name>
          </window>

          <view>
            <heading-deg type = "double">0.0</heading-deg>
            <roll-deg type = "double">0.0</roll-deg>
            <pitch-deg type = "double">0.0</pitch-deg>
          </view>

          <master-perspective>
            <eye-distance type="double">0.7</eye-distance>
<!--
            <x-offset type="double">-0.05</x-offset>
-->
            <y-offset type="double">+-0.10</y-offset>
          </master-perspective>

          <viewport>
            <x>0</x>
            <y>0</y>
            <width>1920</width>
            <height>1080</height>
          </viewport>
          <physical-dimensions>
            <width>0.520</width>
            <height>0.325</height>
            <bezel>
              <top>0.045</top>
              <left>0.021</left>
              <bottom>0.021</bottom>
              <right>0.021</right>
            </bezel>
          </physical-dimensions>
        </camera>

        <camera>
          <name type="string">HalfLeftTop</name>
          <window>
           <name>HalfLeft</name>
          </window>

          <view>
            <heading-deg type = "double">45.0</heading-deg>
            <roll-deg type = "double">0.0</roll-deg>
            <pitch-deg type = "double">0.0</pitch-deg>
          </view>

          <left-of-perspective>
            <parent-camera>FrontLeft</parent-camera>
          </left-of-perspective>

          <viewport>
            <x>0</x>
            <y>0</y>
            <width>1920</width>
            <height>1080</height>
          </viewport>
          <physical-dimensions>
            <width>0.520</width>
            <height>0.325</height>
            <bezel>
              <top>0.045</top>
              <left>0.021</left>
              <bottom>0.021</bottom>
              <right>0.021</right>
            </bezel>
          </physical-dimensions>
        </camera>


      </camera-group>
    </rendering>

  </sim>
</PropertyList>
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 HTLocal » Mon Dec 10, 2018 4:56 pm

Oh yea, I'm also on Ubuntu and resorted to compile FG myself, because I couldn't wait until the PPA gets updated.. Simgear is like a prerequisite as far as I have understood it.

The 200 feet thing does sound strange and kind of aircraft specific. Maybe that rings a bell with someone who has more experience with the 777 than me.
HTLocal
 
Posts: 10
Joined: Sun Dec 02, 2018 11:48 am

Re: Boeing 777 multiple screen crash

Postby SurferTim » Mon Dec 10, 2018 5:05 pm

Thanks for the input. It still works great with a single display, and two displays with the Citation.

I just tried an IFR flight from LAX to SFO, and got a new error on the log display:
corrupted double-linked list
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 HTLocal » Mon Dec 10, 2018 5:06 pm

seems the autopilot will only engage if above 200ft. as in Nasal/AFDS.nas

Code: Select all
        if((output==0)and(getprop("position/gear-agl-ft")<200))
HTLocal
 
Posts: 10
Joined: Sun Dec 02, 2018 11:48 am

Re: Boeing 777 multiple screen crash

Postby SurferTim » Mon Dec 10, 2018 5:56 pm

HTLocal wrote in Mon Dec 10, 2018 5:06 pm:seems the autopilot will only engage if above 200ft. as in Nasal/AFDS.nas

Code: Select all
        if((output==0)and(getprop("position/gear-agl-ft")<200))

That was my original suspicion.

I just got another error on the log window after an abort:
double free or corruption (fasttop)
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 Isaak » Tue Dec 11, 2018 12:42 pm

This is very strange. I run FG on 2, 2 and 4 screens (with 3 Windows pc's driving them) at home and mostly fly the 777. I 've never encountered this issue.

The only properties that are linked to 200 ft AGL are indeed the autopilot and the warning system (which calls out 200 feet during approach). I 'm afraid I 'm of not much help here. Can you try again with --log-level=debug and post your log here afterwards?
Isaak
 
Posts: 335
Joined: Sat Jun 04, 2011 2:52 pm
Location: Leuven, Belgium
Callsign: OO-ISA
Version: 2019.1.1
OS: Windows 10

Re: Boeing 777 multiple screen crash

Postby SurferTim » Tue Dec 11, 2018 1:48 pm

@BEL ISAAK: I'll do as you asked, but it will be a few hours. I just "flew" a Citation from KLAX to KSFO using the same config.xml file and two screens with no problem. The Citation's autopilot has a glitch when passing nav fixes, but I can deal with that. It took a bit of experimenting to get the Citation's autopilot to use the ILS glideslope on approaches. The 777 has no problems with either.

Edit: I'm using one PC for both displays. Maybe that is causing the problem, but what puzzles me is it work fine with the Citation.
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 Isaak » Tue Dec 11, 2018 4:14 pm

Hi SurferTim, I also use one pc to drive multiple screens, in total there are 8 screens, 4 on the main and 2 on each slave pc. I look forward to your log!
Isaak
 
Posts: 335
Joined: Sat Jun 04, 2011 2:52 pm
Location: Leuven, Belgium
Callsign: OO-ISA
Version: 2019.1.1
OS: Windows 10

Re: Boeing 777 multiple screen crash

Postby SurferTim » Tue Dec 11, 2018 7:12 pm

The log file is HUGE! The forum software won't let me post it, and I wasn't surprised. The new log setting causes a freeze even before I can take off.
The last thing in the log window is
double free or corrupted
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 legoboyvdlp » Tue Dec 11, 2018 8:12 pm

Hi,
Maybe you can post the log in pastebin and send us the link?
User avatar
legoboyvdlp
 
Posts: 6487
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 SurferTim » 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
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 WoodSTokk » Wed Dec 12, 2018 3:06 pm

SurferTim wrote in Tue Dec 11, 2018 1:48 pm:The Citation's autopilot has a glitch when passing nav fixes, but I can deal with that. It took a bit of experimenting to get the Citation's autopilot to use the ILS glideslope on approaches.


If you mean the Citation II, the autopilot works good on middle to high speed. I found out that on low speed (on approach) the autopilot have a tendence to oversteer.
The best way is to catch the ILS far out of RWY and slow down later if the ILS established.
WoodSTokk
 
Posts: 194
Joined: Tue Oct 17, 2017 2:30 pm
Location: Milky Way/Sol/Earth/Europe
Callsign: OE-WST
IRC name: WoodSTokk
Version: 2018.3.1
OS: Debian Buster/Sid

Re: Boeing 777 multiple screen crash

Postby SurferTim » Wed Dec 12, 2018 10:19 pm

WoodSTokk wrote in Wed Dec 12, 2018 3:06 pm:
SurferTim wrote in Tue Dec 11, 2018 1:48 pm:The Citation's autopilot has a glitch when passing nav fixes, but I can deal with that. It took a bit of experimenting to get the Citation's autopilot to use the ILS glideslope on approaches.


If you mean the Citation II, the autopilot works good on middle to high speed. I found out that on low speed (on approach) the autopilot have a tendence to oversteer.
The best way is to catch the ILS far out of RWY and slow down later if the ILS established.

I'm flying the Citation-X. The problem I have is intercepting the glideslope. It starts descending before it intercepts it, and the pitch control doesn't seem to work very well. When I get in that close, I disable the autopilot and land manually. No problem with that part here.

I tried Flightgear 2018-3-1 on Windows 10, and was very disappointed. It won't even start the flight with any aircraft or airport. I'm back to Ubuntu 18.04.

I guess I'm stuck with a single screen with the 777. If I use multiple displays, it opens all the windows/cameras, but freezes now when I select "B777-300 -> autostart".

Edit: Just tried the B777-200F (freighter). Again, all went well until 200 feet agl, then freezes. All screens were working until then. ??
Last edited by SurferTim on Wed Dec 12, 2018 11:32 pm, edited 2 times in total.
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

Next

Return to Graphics

Who is online

Users browsing this forum: No registered users and 1 guest