Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Can't get it up

Featured Replies

I ran fgrun and a box popped up that wanted me to enter the Executeable, the FG_ROOT and FG_SCENERY. Not sure why it asked but I put fgrun for the executeable, then went to the root box after that and used what was already entered there, which was the Flight Gear usr/bin folder. After that I tried to enter information from the scenery folder but it showed no files right down to the last directory. I checked the folder and it's not empty. After clicking OK and dropping back to the main dialog there was not an active Next button which I assume would have either started the game or gone on to some next step, so I'm stuck. I don't know what I'm doing at all. Can you tell me if I'm not doing it right or what's wrong? Oh. Suse 10 and I just untarred the program to the directory I wanted it in which was home/scott/programs/games/flightgear.

>I ran fgrun and a box popped up that wanted me to enter the>Executeable, the FG_ROOT and FG_SCENERY. Not sure why it asked>but I put fgrun for the executeable,you were already executing fgrun, so no need to put fgrun in that box, rather you WANT TO execute FlightGear (fgfs), so you need to put the fgfs executable's path there.>then went to the root box>after that and used what was already entered there, which was>the Flight Gear usr/bin folder.This again seems wrong, you would most likely want to put the path to $FG_ROOT there, which (depending on your distro) may be something like /usr/local/FlightGearIf you don't know or don't remember where you installed the base pacakge, you can probably find the correct path by doing something like:$ slocate preferences.xml>After that I tried to enter>information from the scenery folder but it showed no files>right down to the last directory.this should be normal (because you failed to provide the correct path to $FG_ROOT).>I checked the folder and it's not empty./usr/bin ?Yes, this should not be empty at all, however it contains mainly executable files, but you need to tell the fgfs executable where it can find its base package, this is where FG holds its own data.>After clicking OK and dropping back to the>main dialog there was not an active Next button which I assume>would have either started the game or gone on to some next>step, so I'm stuck.>> I don't know what I'm doing at all. Can you tell me if I'm>not doing it right or what's wrong?Well, here's some fgrun documentation:http://www.seedwiki.com/wiki/flight_gear/f...rol?wpid=246132> Oh. Suse 10 and I just untarred the program to the directory>I wanted it in which was>home/scott/programs/games/flightgear.If you need further help, please try to provide the information suggested on the following page:http://www.seedwiki.com/wiki/flight_gear/h...you?wpid=247004

Ok I changed the executeable, but no luck.I have the game in home/scott/programs/games/flightgear...not usr/local/flightgear. I pointed the FG_ROOT to flightgear/usr/bin in the home/scott/programs/games/ directory because it came up there by default (I assumed because that was where I had run fgrun from) and because I was told the root directory was where the binaries were. If I don't enter an executeable it defaults to /home scott/ as the FG_ROOT I now have tried changing the root to simply home/scott/programs/games/flightgear but it didn't help. When I said I checked the folder and they were not empty I meant the scenery folder. Sorry. I'm not sure what telling it where the root folder is has to do with not being able to find scenery in the scenery folder, but in any case I'm still coming up empty. I'll look at your links here. Thanks.

You should really try to provide as much information as possible, only telling us:>Ok I changed the executeable, but no luck.doesn't tell us anything about the actual path/file you are using now.>I have the game in home/scott/programs/games/flightgear...not>usr/local/flightgear. okay, so the whole base package is located under ~/programs/games/flightgear ?> I pointed the FG_ROOT to flightgear/usr/bin in the>home/scott/programs/games/ directory because it came up there>by default (I assumed because that was where I had run fgrun>from) and because I was told the root directory was where the>binaries were.I am not sure where you were told this, however $FG_ROOT should always point to the base package (which is the "data" sub folder).>If I don't enter an executeable it defaults to>/home scott/ as the FG_ROOT> I now have tried changing the root to simply>home/scott/programs/games/flightgear but it didn't help.well, it's hard to provide any competent feedback without knowing all the details. However, *IF* you have installed FlightGear correctly, I would recommend to try the following:1) run $whereis fgfs and put the result in the box for the executable2) locate $FG_ROOT using $slocate data/preferences.xml and put the result into the box for $FG_ROOT3) try to run fgrun/fgfs(this works only provided that you have only one version of FG installed!)> When I said I checked the folder and they were not empty I>meant the scenery folder. Sorry.no problem, but please note that you can simplify the task of helping you addressing any issues tremendously, if you try to be extremely concise and thorough in your descriptions. We cannot know anything about your machine/setup that you don't tell us, so it is generally much better to mention everything that might be relevant, rather than simply ommitting details that you may not consider important.>I'm not sure what telling it where the root folder is has to>do with not being able to find scenery in the scenery folder,>but in any case I'm still coming up empty.this again depends on the startup settings you are using, that is if you are using any non-standard scenery, installed outside of $FG_ROOT. The SFO scenery however should always be installed within $FG_ROOT by default.

>You should really try to provide as much information as possible, only telling us:>Ok I changed the executeable, but no luck.doesn't tell us anything about the actual path/file you are using now.From my first post: "Oh. Suse 10 and I just untarred the program to the directory I wanted it in which was home/scott/programs/games/flightgear. I ran fgrun and a box popped up that wanted me to enter the Executeable, the FG_ROOT and FG_SCENERY. " I just assumed that you expected the binaries all to be in the /flightgear/usr/bin folder and that you wouldn't have expected me to change the directory location and not tell you. Yes, the directory is ~/programs/games/flightgear. Everything that is in the entire game directory came with it in the tar file, including scenery.>1) run $whereis fgfs and put the result in the box for the executable. Results = "bash: fgfs: command not found". I have observed the file "fgfs" in the bin folder.>2) locate $FG_ROOT using $slocate data/preferences.xml and put the result into the box for $FG_ROOT. Results = "bash: data/preferences.xml: No such file or directory". I have looked in the data folder. There is no preferences.xml there. I changed the FG_ROOT to the data folder with same results as before.BUT...I found preferences.xml manually in the flightgear/usr/share/flightgear folder entered that location as FG_ROOT and it auto put in scenery and gave me next button. However, after I entered in some info it asked about planes and location screen rez etc and it started to load, it stopped and gave me a console with errors. I will have to assimilate all this and if I cannot resolve it myself I will get back to you.Thank you again..

This is the output of the console that appears with the opening splash screen after hitting the "Run" button.opening file: /home/scott/Programs/Games/FlightGear/usr/share/FlightGear/Navaids/carrier_nav.dat/home/scott/Programs/Games/FlightGear/usr/share/FlightGear/Navaids/TACAN_freq.datReading xml electrical system model from /home/scott/Programs/Games/FlightGear/usr/share/FlightGear/Aircraft/Generic/generic-electrical.xmlInitialising callsign using 'Aircraft/737/Models/boeing733.xml'freeglut (fgfs): Failed to create cursor It stops here and fails to run.

>freeglut (fgfs): Failed to create cursorThat's the infamous freeglut bug. You are using freeglut 2.4, which is broken. Try an older version (2.2) or a newer one (CVS). If you compile from sources, try to use SDL instead (--enable-sdl). It's not a FlightGear bug.

and don't know how to change versions. Sdl is on the system. Are you saying I can use it instead of freeglut to run the game? If so, I'm not sure how to utilize that command you provided.

> Don't know how to change versions. Sdl is on the system. Are> you saying I can use it instead?Yes, but only if you compile the sources yourself. If you are a newbie then this is not an option for you. Better try to get a newer freeglut release then, or use "unfree" glut.

.

Well, yes-at least if you have already a recent version of SDL.On the other hand, FlightGear has a number of dependencies such as SimGear, PLIB, OpenAL,PThreads that will also need to be satisfied.Usually, the easiest way to compile FG from scratch is to simply get all the latest dependencies and compile them from scratch, too.With the exception of SimGear and maybe PLIB, you will probably only have to do this once. If you simply check out all the latest dependencies from CVS you can easily update and rebuild all sources quite quickly.

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.