Board index FlightGear Support Installation Windows

Win 10 FG 2020.3.11 clean install hangs after "Fly!"

Installing FlightGear, scenery, aircraft etc. on Windows.

Win 10 FG 2020.3.11 clean install hangs after "Fly!"

Postby Simworld2020 » Fri Jan 21, 2022 8:08 pm

Hello,

On a clean install of 2020.3.11, at default airport in hawaii with no options activated, no terrasynch, no real weather, default rendering, no addons, FG starts normally and lets me choose options, but then hangs and does not respond anymore, the window turns white and I have to use task manager to shut it down.

This happens exactly at the time when the startup splash screen begins to dissolve and the cockpit starts to become visible.

Here is the info from the command line:

Code: Select all
--launcher --prop:/nasal/local_weather/enabled=false --metar=XXXX 012345Z 15003KT 19SM FEW072 FEW350 25/07 Q1028 NOSIG --prop:/environment/weather-scenario=Core high pressure region --timeofday=morning --disable-rembrandt --prop:/sim/rendering/texture-cache/cache-enabled=false --disable-terrasync --disable-sentry --aircraft-dir=C:/Program Files/FlightGear 2020.3.11/data/Aircraft/c172p --aircraft=c172p --airport=PHTO --runway=08 --fg-aircraft=C:/Users/LENOVO/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.stable_2020 --log-level=debug
 


And here is the last part of the log (I had to delete the beginning of the log because my message was too long):

Code: Select all
   70.91 [INFO]:nasal     C:/Program Files/FlightGear 2020.3.11/data/Aircraft/Generic/Human/Nasal/walker-animate.nas:2255:     found trigger: loading animation for landing to position 6
   70.91 [INFO]:nasal     C:/Program Files/FlightGear 2020.3.11/data/Aircraft/Generic/Human/Nasal/walker-animate.nas:2268:     found trigger: loading animation for crashing to position 7
   70.97 [WARN]:io        C:\Jenkins\workspace\Windows-release\simgear\simgear\scene\material\mipmap.cxx:272: mipmapping: texture size not a power-of-two: C:\Program Files\FlightGear 2020.3.11\data\Scenery\Objects\w160n10\w156n19\KSJC_tower.rgb
   77.46 [INFO]:nasal     C:/Program Files/FlightGear 2020.3.11/data/Aircraft/c172p/Models/Interior/Panel/Instruments/garmin196/garmin196.nas:2990: Garmin 196 loading cities
   78.18 [INFO]:nasal     C:/Program Files/FlightGear 2020.3.11/data/Aircraft/c172p/Models/Interior/Panel/Instruments/garmin196/garmin196.nas:3006: Garmin 196 loading cities done
   78.18 [INFO]:nasal     C:/Program Files/FlightGear 2020.3.11/data/Aircraft/c172p/Nasal/engine.nas:85: Primer reset to 0


Note: The program will run in Win7 compatibility mode, but with serious lag spikes, I don't want to know why that happens, I prefer to understand and resolve why this is happening in Win 10.

All of my drivers are updated according to Windows.

Any insights appreciated!
Flying DHC-6, MD-11 and A320-family
FG 2020.3.11 / 2020.4.0 nightly
Lenovo Thinkpad W540
Windows 10 Pro vers. 21H2 - 64 bit
Intel core i7-4800MQ @ 2.7 GHz
24 Gb DDR3 RAM
NVIDIA Quadro K2100M/2Gb RAM
Simworld2020
 
Posts: 81
Joined: Tue Dec 08, 2020 11:59 pm

Re: Win 10 FG 2020.3.11 clean install hangs after "Fly!"

Postby xDraconian » Fri Jan 21, 2022 11:57 pm

First thing to fix is metar and weather-scenario. Options cannot contain spaces unless you place them within quotes.

--metar="XXXX 012345Z 15003KT 19SM FEW072 FEW350 25/07 Q1028 NOSIG"
--prop:/environment/weather-scenario="Core high pressure region"

After making this adjustment, does it change the behavior?
xDraconian
 
Posts: 406
Joined: Sun Jan 21, 2018 6:53 am
Version: Git
OS: Linux Mint

Re: Win 10 FG 2020.3.11 clean install hangs after "Fly!"

Postby Simworld2020 » Sat Jan 22, 2022 1:18 am

xDraconian wrote in Fri Jan 21, 2022 11:57 pm:First thing to fix is metar and weather-scenario. Options cannot contain spaces unless you place them within quotes.

--metar="XXXX 012345Z 15003KT 19SM FEW072 FEW350 25/07 Q1028 NOSIG"
--prop:/environment/weather-scenario="Core high pressure region"


That is interesting.
I did not enter these commands myself in the "additional settings" window in the launcher, except for the last one "--log-level=debug". All of the others were created automatically by FG according to the current settings of the sim. I was able to copy them to the clipboard and paste them here using the menu option in the "three dots" menu in the upper left hand corner of the launcher just before clicking the "Fly!" button.

To test further on what you noticed, I ran FG in Win7 compatibility mode, it runs. But again I collected the command line text that FG offered, and I'm pasting it below:

Code: Select all
--launcher --prop:/nasal/local_weather/enabled=false --metar=XXXX 012345Z 15003KT 19SM FEW072 FEW350 25/07 Q1028 NOSIG --prop:/environment/weather-scenario=Core high pressure region --timeofday=morning --disable-rembrandt --prop:/sim/rendering/texture-cache/cache-enabled=false --disable-terrasync --disable-sentry --aircraft-dir=C:/Program Files/FlightGear 2020.3.11/data/Aircraft/c172p --aircraft=c172p --airport=PHTO --runway=08 --fg-aircraft=C:/Users/LENOVO/Desktop/SIM/MyAircraft/Aircraft --fg-aircraft=C:/Users/LENOVO/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.stable_2020 --log-level=debug


And in the METAR and weather scenario settings, the spaces still appear and no quotation marks to contain that text, but the sim did not hang and I was able to fly.
Flying DHC-6, MD-11 and A320-family
FG 2020.3.11 / 2020.4.0 nightly
Lenovo Thinkpad W540
Windows 10 Pro vers. 21H2 - 64 bit
Intel core i7-4800MQ @ 2.7 GHz
24 Gb DDR3 RAM
NVIDIA Quadro K2100M/2Gb RAM
Simworld2020
 
Posts: 81
Joined: Tue Dec 08, 2020 11:59 pm


Return to Windows

Who is online

Users browsing this forum: No registered users and 1 guest