Board index FlightGear Support Installation

FG2018.1.1 Don't Start after activating of ALS

Need help getting up and running? Installing FlightGear, add-on planes, sceneries etc.
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?

Please, also see Requesting Technical Help.

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.

FG2018.1.1 Don't Start after activating of ALS

Postby powoflight » Tue May 29, 2018 9:34 am

Hopefully this is the right subforum.
I am using Win7 / 16GB Ram and nvidia 1060

After using 2017.3.1 and earlier Versions i upgrade now to 2018.1.1

I am activating ALS . It works perfect. If i stop FG and restart FG . It hangs by : This is the last part from fgfs.log
Code: Select all
nasal:5:C:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:467:Joystick T16000M
nasal:5:C:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:467:sim/version/flightgear
nasal:5:C:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:467:     aircraft: UFO
nasal:5:C:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:467:     aircraftversion:
nasal:5:C:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:467:SEARCH Aircraft sim/aircraft  -> FIND: UFO
nasal:5:C:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:467:test:
flight:3:C:\Jenkins\workspace\Windows-release\flightgear\src\FDM\fdm_shell.cxx:112:FDM connection to the AI manager: SUCCESS
navaid:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Airports\xmlloader.cxx:52:reading groundnet data from Path "D:/FG/SC/SC_HD/Airports/L/O/W/LOWW.groundnet.xml"
navaid:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Airports\xmlloader.cxx:62:parsing groundnet XML took 0
ai:3:C:\Jenkins\workspace\Windows-release\flightgear\src\AIModel\AIManager.cxx:168:loading scenario 'nimitz_demo'
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:983:Subsystems postinit took:10
general:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:992:

view:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress finalize-position
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:2, 48:0
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:2, 48:1
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:504:FGTileMgr: at lon = 16.5756deg, lat = 48.1091deg, elev = -3047.7m, scheduling needed for:16:2, 48:0, visibility=32000
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:293:scheduling needed tiles for 16:2, 48:0, tile-width-m:18576.7, tile-height-m:13914.9
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:0, 47:5
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:0, 47:6
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:0, 47:7
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:0, 48:0
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:0, 48:1
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:0, 48:2
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:0, 48:3
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:1, 47:5
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:1, 47:6
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:1, 47:7
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:1, 48:0
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:1, 48:1
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:1, 48:2
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:1, 48:3
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:2, 47:5
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:2, 47:6
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:2, 47:7
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:2, 48:2
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:2, 48:3
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:3, 47:5
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:3, 47:6
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:3, 47:7
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:3, 48:0
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:3, 48:1
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:3, 48:2
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:16:3, 48:3
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:17:0, 47:5
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:17:0, 47:6
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:17:0, 47:7
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:17:0, 48:0
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:17:0, 48:1
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:17:0, 48:2
terrain:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:17:0, 48:3


FG do not load stg files
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 3220072.stg

I have to kill the exe and delete navdata_2018_1.cache and autosave_2018_1.xml and use fg without ALS

My Start parameters: bat file
Code: Select all
"D:\FG\FlightGear2018_1_1\bin\fgfs.exe"^
    --fg-root=D:\FG\FlightGear2018_1_1\data^
    --fg-scenery=D:\FG\SC\SC_HD^
    --terrasync-dir=D:\FG\SC\Terrasync^
    --fg-aircraft=D:\FG\Aircraft^
    --airport=LOWW^
    --aircraft=UFO^
    --log-level=debug^
    --console^
    --geometry=1200x750^
    --bpp=32^
   --httpd=8080


I can reproduce this error.
Is this bug known or /and should i update to 2018.2 ?
powoflight
 
Posts: 84
Joined: Fri Mar 25, 2016 10:04 am
Location: LOWW
Version: 2018.3.2
OS: win7 Ubuntu 18.04

Re: FG2018.1.1 Don't Start after activating of ALS

Postby wkitty42 » Tue May 29, 2018 12:32 pm

AFAICS, it is not a bug...
are you running the latest drivers for your video card?

why do you not turn on ALS (and ensure Rembrandt is turned off) on your command line? don't forget your '^' if you copy these lines to your BAT file...
Code: Select all
--disable-rembrandt
--prop=/sim/rendering/shaders/skydome=true
we can also enable the ALS custom shader settings and set the sliders with props... i can show you if you want but let's see if we can get ALS working for you first...

why do you not use the launcher? you can set all of your command line options in it quite easily and flipping between the default renderer, Rembrandt and ALS is just the flick of a switch...

unless that stg file is corrupted, i think loading it is just where FG happens to be in its process when it locks up... in other words, probably not the reason for the lockup...

i would definitely try 2018.2.1 and in a few days/weeks 2018.2.2 which will be out to fix some bugs in 2018.2.1...

you should not ever need to delete the navdata cache file... it never needed to be deleted... deleting the autosave settings could possibly help if there are conflicting settings stored in it... generally, though, it does not need to be deleted...



HINT: you could also add your terrasync-dir path to your fg-scenery path so you can use your terrasync scenery when/if you have terrasync turned off ;)
Code: Select all
--fg-scenery=D:\FG\SC\SC_HD;D:\FG\SC\Terrasync
"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: 5330
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: FG2018.1.1 Don't Start after activating of ALS

Postby powoflight » Wed May 30, 2018 11:02 am

are you running the latest drivers for your video card?

see Answer: why do you not use the launcher?

why do you not turn on ALS (and ensure Rembrandt is turned off) on your command line?

Have done this, but there is no difference. Same result.

why do you not use the launcher? you can set all of your command line options in it quite easily and flipping between the default renderer, Rembrandt and ALS is just the flick of a switch...

If i am using the launcher, then everthing is ok!! :) Sorry I forgot to mention that
But for development reasons i am using bat files now for 4 Years. This means too, that this bat file works in
Version 3.4, 3.6RC , FG 2016.1 , 2016.2, 2017.2.1 and 2017.3.1. but not in FG2018.1 and 2018.2 . ( I use some kind of parallel installation in WIN7)

you should not ever need to delete the navdata cache file... it never needed to be deleted...

Yes, I know that, but if FG crashes, that's the last option. Was often mentioned in the forum. But we can forget this item ...

HINT: you could also add your terrasync-dir path to your fg-scenery path so you can use your terrasync scenery when/if you have terrasync turned off ;)

I have allready downloaded the whole world mit Terramaster. ...
I use this directory in my bat file.
Code: Select all
--fg-scenery=D:\FG\SC\SC_HD^


i would definitely try 2018.2.1

I have download FG 2018.2.1 but more or less same behavier...

Here are the logfiles if start of FG is
OK: fgfs.log
NOT OK: fgfs_0.log
https://c.gmx.net/@327459158418791162/O ... mNjYWEFBXg

I have a guess (autosave_2018_2.xml). But first have to verify it.
powoflight
 
Posts: 84
Joined: Fri Mar 25, 2016 10:04 am
Location: LOWW
Version: 2018.3.2
OS: win7 Ubuntu 18.04

Re: FG2018.1.1 Don't Start after activating of ALS

Postby wkitty42 » Thu May 31, 2018 12:48 pm

powoflight wrote in Wed May 30, 2018 11:02 am:
why do you not use the launcher? you can set all of your command line options in it quite easily and flipping between the default renderer, Rembrandt and ALS is just the flick of a switch...

If i am using the launcher, then everthing is ok!! :) Sorry I forgot to mention that

that's ok :)

powoflight wrote in Wed May 30, 2018 11:02 am:But for development reasons i am using bat files now for 4 Years. This means too, that this bat file works in
Version 3.4, 3.6RC , FG 2016.1 , 2016.2, 2017.2.1 and 2017.3.1. but not in FG2018.1 and 2018.2 . ( I use some kind of parallel installation in WIN7)

there should not be a problem, then... but since there is, more data is needed... see below...

powoflight wrote in Wed May 30, 2018 11:02 am:
you should not ever need to delete the navdata cache file... it never needed to be deleted...

Yes, I know that, but if FG crashes, that's the last option. Was often mentioned in the forum. But we can forget this item ...

not a problem... FWIW: it was given as misguided information for recovering... it was never the cache database that needed to be deleted...

powoflight wrote in Wed May 30, 2018 11:02 am:
HINT: you could also add your terrasync-dir path to your fg-scenery path so you can use your terrasync scenery when/if you have terrasync turned off ;)

I have allready downloaded the whole world mit Terramaster. ...
I use this directory in my bat file.
Code: Select all
--fg-scenery=D:\FG\SC\SC_HD^

i might have misread something...

powoflight wrote in Wed May 30, 2018 11:02 am:
i would definitely try 2018.2.1

I have download FG 2018.2.1 but more or less same behavier...

Here are the logfiles if start of FG is
OK: fgfs.log
NOT OK: fgfs_0.log
https://c.gmx.net/@327459158418791162/O ... mNjYWEFBXg

ahhh... you should grep out the options from the beginning of the log and compare them to those you use in your .bat file... from the linked log files, those options are the same... now, here's something else... are you using a rc file? when the launcher is used, FG will ignore rc files... since you're starting from a bat file, the rc file will be read and used... both of those logs show that you have ALS and Rembrandt disabled...

start from the launcher with ALS enabled and let's get those options from the log file when you exit... then we can compare them with those you have in your rc and/or bat files...
Code: Select all
egrep -e "options\.cxx" fgfs.log



this section is also interesting... it is from the fgfs.log you shared... the other log didn't get this far... i don't think this would cause FG to crash, though...
Code: Select all
opengl:3:C:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\fg_os_osgviewer.cxx:209:
opengl:4:C:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\fg_os_osgviewer.cxx:209:GEOMETRY glCompileShader "D:/FG/FlightGear2018_2_1/data/Shaders/landmass.geom" FAILED

opengl:4:C:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\fg_os_osgviewer.cxx:209:GEOMETRY Shader "D:/FG/FlightGear2018_2_1/data/Shaders/landmass.geom" infolog:
0(47) : warning C7533: global variable gl_FrontColor is deprecated after version 120
0(50) : error C7616: global variable gl_TexCoord is removed after version 140
0(68) : error C7616: global variable gl_ModelViewMatrix is removed after version 140
0(69) : error C7616: global variable gl_ModelViewProjectionMatrix is removed after version 140
0(81) : error C7616: global variable gl_NormalMatrix is removed after version 140


powoflight wrote in Wed May 30, 2018 11:02 am:I have a guess (autosave_2018_2.xml). But first have to verify it.

you could remove/rename it to ensure that it is not restoring a bad set of settings... however, once they are working properly, they should be automatically saved in there at the next proper exit of the sim... remember that if you remove/rename it, you will have to configure everything again since FG will start off in default mode looking for everything in the expected default places...
"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: 5330
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: FG2018.1.1 Don't Start after activating of ALS

Postby powoflight » Fri Jun 01, 2018 7:38 am

Hi wkitty42

Thanks for your help. I will check it .
In the meantime, I've done more checks. Fg does not start with the bat file any more, for example when I put in the bat --fg-aircraft = D: \ FG \ Aircraft ^ or change someting in the Shader options menu.
.
Deleting autosave_2018_2.xml. Same behaviour, do not start with the bat file. (Yes I have to configure all again)
Deleting navdata_2018_2.cache. Now FG starts with the bat file. (Build the cache new. Ok takes time)
Maybe I'm looking for the wrong place? Maybe it is something else? I mean not he ALS..

But in meantime I find a Solution. I found the hint there viewtopic.php?f=11&t=34056.
I use now this bat file and everything works perfect. (Take the best from 2 worlds!).
As you see i start the launcher but with my parameters.

Code: Select all
D:\FG\FlightGear2018_2_1\bin\fgfs.exe --launcher  --fg-aircraft=D:\FG\Aircraft^
 --fg-scenery=D:\VMOrdner\OSM\WIEN_OUT;^
 --fg-scenery=D:\FG\SC\SC_AIRPORTS_XPLANE\XPLANE_ALL_AIRPORTS;^
 --fg-scenery=D:\FG\SC\SC_HD^
 --airport=LOWW^
 --aircraft=ufo^
 --timeofday=noon^
 --prop:double:/sim/rendering/static-lod/detailed=5000^
 --prop:double:/sim/rendering/static-lod/rough=10000^
 --prop:/sim/rendering/max-paged-lod=400^
 --httpd=8080


So i don't know. Should we investigate this phenomena or should somebody write a wiki like now we can use the launcher with parameters from the http://wiki.flightgear.org/Command_line_options and everything is allright? (For Version 2018.1 and upwards)

PS:
Code: Select all
 now, here's something else... are you using a rc file? when the launcher is used, FG will ignore rc files... since you're starting from a bat file, the rc file will be read and used...

Where i can find a description about rc file? I don't know now the rc file and where i find it in Win7?

Bernhard
powoflight
 
Posts: 84
Joined: Fri Mar 25, 2016 10:04 am
Location: LOWW
Version: 2018.3.2
OS: win7 Ubuntu 18.04

Re: FG2018.1.1 Don't Start after activating of ALS

Postby wkitty42 » Fri Jun 01, 2018 10:24 am

first, if you're going to use the launcher, you can put most all of your parameters into the "Settings->Additional settings" box in the launcher... some of them won't be needed since you can choose them in the launcher...

if you're not going to use the launcher but are going to use rc files, the rc files are just the list of parameters like you're using... my .fgfsrc file and the contents of my "Settings->Additional settings" box in the launcher are identical except my rc file also contains fg-root, fg-scenery and fg-aircraft paths... they are defined elsewhere in the launcher and are not needed in the additional setting box...

this page has info but may be a bit outdated... it does at least describe the format as well as the placement... http://wiki.flightgear.org/Fgfsrc
"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: 5330
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: FG2018.1.1 Don't Start after activating of ALS

Postby powoflight » Sat Jun 02, 2018 11:32 am

Perfect. I will try the rc files. But in anyway i am lucky , because the launcher version works for my needs.
powoflight
 
Posts: 84
Joined: Fri Mar 25, 2016 10:04 am
Location: LOWW
Version: 2018.3.2
OS: win7 Ubuntu 18.04


Return to Installation

Who is online

Users browsing this forum: No registered users and 1 guest