I’m using Flightgear 2.8 with OpenSuse 12.2, KDE3.
I’ve installed Flightgear and uncompressed the Scenery tarballs into the /usr/share/flightgear/Scenery directory, and the additional Aircraft tarballs into the /usr/share/flightgear/Aircraft Directory.
The installation manual says I have to set some environment variables next.
First it tells me to set FG_ROOT to the data subdirectory of where I installed FlightGear. FlightGear is installed to /usr/share/flightgear. The manual says I should be looking for a data subdirectory called data, but there isn’t one. Do I just use /usr/share/flightgear?
It’s the same with Scenery files - for FG_SCENERY - there is no data subdirectory for usr/share/flightgear but there is usr/share/flightgear/Scenery, which I assume is what I use.
The manual also talks about adding /use/local/share/Flightgear/lib to my LD_LIBRARY_PATH.
I have no idea what the LD_LIBRARY_PATH is and where to find it. Nor is there any directory labelled lib in /usr/share/flightgear. There is one labelled lib in /usr/local.
Now I need to know how do I add the path and how do I set the environmental variables. I assume I need to do this as root, yes?
Anyone want to lead me along?
Thanks,
Bob
You don’t need to configure any environment variables when you’re using the binaries from the FlightGear RPM package. The package is fully configured, so it already “knows” the directories where to find its data (in /usr/share/flightgear), scenery and aircraft. The thing about environment variables applies to users who are not using a preconfigured RPM package, and need to do stuff manually.
When you’re new to FlightGear, you may also want to install the “fgrun” package, a graphical launcher GUI for FlightGear - so you can select aircraft and start-up locations without having to use FG command-line parameters. fgrun is also available in openSUSE’s “games” repository.
cheers,
Thorsten
Same question here: how did you install FG, where did you get it from. This, software.opensuse.org: Download openSUSE 12.2, is the place where every software search should start.
On 2012-10-14 15:36, thorstenbr wrote:
> When you’re new to FlightGear, you may also want to install the “fgrun”
> package, a graphical launcher GUI for FlightGear - so you can select
> aircraft and start-up locations without having to use FG command-line
> parameters. fgrun is also available in openSUSE’s “games” repository.
There are two in the game repo: fgrun, and FGx
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On 2012-10-14 15:36, thorstenbr wrote:
> When you’re new to FlightGear, you may also want to install the “fgrun”
> package, a graphical launcher GUI for FlightGear - so you can select
> aircraft and start-up locations without having to use FG command-line
> parameters. fgrun is also available in openSUSE’s “games” repository.
cer@Telcontar:~> fgrun &
[1] 23585
cer@Telcontar:~> fgrun: symbol lookup error: /usr/lib64/libfltk.so.1.3:
undefined symbol: FcPatternCreate
and:
cer@Telcontar:~> fgfs &
[1] 23627
cer@Telcontar:~> KI266 dme indicator #0 initialized
loading scenario 'nimitz_demo'
Error: Audio device not available, trying default
Initializing Nasal Electrical System
join_values_nofail:398 - failed to coalesce values
join_values_nofail:398 - failed to coalesce values
[1]+ Segmentation fault fgfs
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On 2012-10-14 18:43, Carlos E. R. wrote:
>
>
> [1]+ Segmentation fault fgfs
>
> <0.6> 2012-10-14 18:38:50 Telcontar kernel - - - fgfs[23627]: segfault at 0 ip 00007f0755e1e946 sp 00007fffd80ad250 error 6 in nouveau_dri.so[7f0755c00000+c46000]
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
I just tried the latest packages for 12.1/x86_64. They are running fine. A missing symbol suggests your installation is inconsistent, i.e. you haven’t updated some packages, which fgrun depends upon or you have installed mismatching packages from another source (such as packman). My guess is your “libfltk1” packages doesn’t match the “fontconfig” package on your system (check/update with yast).
This is caused by the nouveau graphics driver. I don’t think you’d get good frame rate with the nouveau drivers with FlightGear anyway. Try the proprietary NVIDIA drivers, they are running fine with FlightGear.
cheers,
Thorsten
On 2012-10-14 21:06, thorstenbr wrote:
> This is caused by the nouveau graphics driver. I don’t think you’d get
> good frame rate with the nouveau drivers with FlightGear anyway. Try
> the proprietary NVIDIA drivers, they are running fine with FlightGear.
I can’t. I’d be happy with a low refresh rate.
I’ll report issue in bugzilla.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)