Flightgear was unwillently started "paused", and in this state the Seneca does not come up! Some of the lights working, but no avionics power. Similar for the Cessna.
Hello,
Since 2018.1.1 I experience the following Problem: When starting flightgear directly from the surface ( without fgrun), I get a "dead" airplane. At 172P everything stays dark ( Battery switch and avionics power on), no radio, no starter.
Options passed on the command line:
- Code: Select all
--launcher
--download-dir=/home/peterb/fgfs
Options set in the launcher:
--aircraft-dir=/usr/share/games/flightgear/Aircraft/c172p
--aircraft=c172p
--fg-scenery=/home/peterb/fgfs/Scenery
--fg-scenery=/home/peterb/fgfs/Scenery/Terrasync
--fg-aircraft=/home/peterb/fgfs/Aircraft
--airport=PHNL
--disable-auto-coordination
--enable-freeze
--prop:/sim/multiplay/txhost=mpserver01.flightgear.org
--prop:/sim/multiplay/txport=5000
--callsign=D-ADA1
--enable-terrasync
--enable-fullscreen
--geometry=1920x1080
--prop:/sim/rendering/multi-sample-buffers=1
--prop:/sim/rendering/multi-samples=4
--disable-rembrandt
--disable-auto-coordination
--airport=EDFH
--timeofday=noon
--season=summer
--disable-real-weather-fetch
--prop:/nasal/local_weather/enabled=true
--metar=XXXX 012345Z 15003KT 19SM FEW072 FEW350 25/07 Q1028 NOSIG
--prop:/environment/weather-scenario=Core high pressure region
when choosing seneca II the following: Main switch and magnetos on, every circuit braker on, no avionics power, no vacuum pump, no radios except ADF radio!, which seems to have Power!
When I use Fgrun to start, everything seems normal.
- Code: Select all
/usr/games/fgfs
--fg-root=/usr/share/games/flightgear
--fg-scenery=/usr/share/games/flightgear/Scenery:/home/peterb/fgfs/Scenery
--terrasync-dir=/home/peterb/fgfs/Scenery/Terrasync
--fg-aircraft=/home/peterb/fgfs:/home/peterb/fgfs/Aircraft
--airport=EDFH
--aircraft=SenecaII
--console
--enable-random-objects
--enable-hud
--enable-anti-alias-hud
--disable-specular-highlight
--enable-ai-models
--enable-ai-traffic
--turbulence=0.05
--enable-real-weather-fetch
--enable-clouds3d
--enable-fullscreen
--prop:/sim/frame-rate-throttle-hz=60
--prop:/sim/menubar/autovisibility/enabled=1
--geometry=1920x1080
--bpp=32
--texture-filtering=8
--prop:/sim/rendering/multi-sample-buffers=1
--prop:/sim/rendering/multi-samples=2
--timeofday=noon
--enable-terrasync
--httpd=5500
--props=5501
--callsign=D-ADA1
--multiplay=out,10,localhost,5001
--multiplay=in,10,,5000
--enable-fgcom
--atlas=socket,out,5,localhost,5500,udp
Has anybody the same problem, or could explane it?
running 2018.1.1 on Ubuntu 18.04 x64, same on Suse Tumbleweed
Peter
btw, the log says
- Code: Select all
lightGear: Version 2018.1.1
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
StatsHandler::StatsHandler() Setting up GL2 compatible shaders
Starting automatic scenery download/synchronization to '/windoze/F/fgfs/Scenery/Terrasync'.
In file /windoze/F/fgfs/Aircraft/SenecaII/SenecaII-jsbsim.xml: line 534
Property gear/serviceable is already defined.
In file /windoze/F/fgfs/Aircraft/SenecaII/SenecaII-jsbsim.xml: line 742
Property ice/wing is already defined.
Multiplayer mode active!
Volcanic activity off.
Request detected to initialize Advanced Weather on startup...
Loading local weather routines...
Animated jetways ... initialized
KCS55 pictorial navigation system initialized
creating PitotIcingHandler for /systems/pitot[0]
warning: The VAD has been replaced by a hack pending a complete rewrite
KI266 dme indicator #0 initialized
Starting hard-coded terrain presampling
caught exception processing subsystem:traffic-manager
message:Bad arguments to findShortestRoute
caught exception processing subsystem:traffic-manager
message:Bad arguments to findShortestRoute