FlightGear 2016.3.1 "Rio de Janeiro" released

[Octal450]

But FGrun is simpler. And faster for me. For example,
when I make nasal scripts, I often need to relaunch FGFS many times. FGrun says open when FGFS launches, therefore, I just pushe run and it opens again!

I will not be upgrading unless I can get the console window open. That is BS! Why would you remove this!

[Hooray]

I think Nasal scripts should meanwhile reload during reset - so that may be much easier than actually exiting/restarting fgfs.
If in doubt, file a feature request to expose this as a fgcommand/menubar item, i.e. something like "reload scripts"

[Octal450]

Or a *reaload nasal* button under Debug. It's the one thing you can't reload. (besides textures)

I still need the console to find problems!

[PINTO]

For reals, if you were using FGRun, use FFGo. The console is persistent between restarts.

[Octal450]

No cannot use FFGo.

Python never works for me.
I don't want to open commandline to start FFGo, too long of the time.

I want the reason for console removal pls! @Torsten

Josh

[CaptB]

Just tested today, FGFS works like a charm, a big thanks to the team!

I am a little bit disappointed that the windows installer still does not give an option to choose the TerraSync and friends directories and just assumes the default location, which is not the best idea since it's the same drive where the system lives and I for instance would prefer to have it on a separate partition or drive. The qt launcher layout and organization continues to be a bit counter intuitive, Add-ons tab especially.

[skelehat]

When will be debian packages available? I'd compile it myself but the data download always gets stuck. Can't wait to try!

[elgaton]

Usually, the PPA is updated a few days after the release (it is managed by a single developer, who needs to build and test the packages manually).

A tip for the data download: instead of downloading the fgdata repository from Git, you can get this boilerplate download, which contains just the .git directory (ready to be checked out). Being this a plain HTTP download, you should be able to resume it, and it should not get stuck.

After downloading the file, you should be able to perform the checkout as follows:

Code: Select all

mkdir fgdata
tar xvf ../fgdata-ng-boilerplate.git.tar
git pull
git checkout -- .


[CaptB]

I just noticed that in the windows qt launcher no aircraft images are displayed. As I hover the path separator for all aircraft paths is the *nix type, maybe that is the problem?

[skelehat]

After downloading the file, you should be able to perform the checkout as follows:

Code: Select all

mkdir fgdata
tar xvf ../fgdata-ng-boilerplate.git.tar
git pull
git checkout -- .


I tried this but at git pull I get stuck at:
Receiving objects: 72% (4726/6477), 584.93 MiB | 157.00 KiB/s

So I'll just wait for that package I guess.

[elgaton]

There's another way - I think I can create a "bundle" of all objects that were changed between the latest revision in the boilerplate and now and put in on Dropbox, or, alternatively, ask the developers on the -devel mailing list to create an updated boilerplate (that would be even better).

Let me know which solution would be best for you.

[ctesc356]

I still need the console to find problems!

Hello,
see: http://wiki.flightgear.org/FlightGear_Qt_launcher

Enabling console display on Windows systems
To enable console display on Windows, right-click on the FlightGear shortcut on the Desktop and click Properties. In the Target box under the Shortcut tab, add --console at the end and click OK.

[Octal450]

The --console tag was removed. So this won't work.

[D-ABBA]

Hi
thanks for the new version...

I fetch the Rio Version 2016.3.1 and was suprised. I am able to install the new version (Parallel to version 2016.2.1).
After launch 2016.3.1 (using fgrun.exe, also fgfs.exe) I get the message "fgrun.exe no longer works" and FlightGear aborted. I am very disappointed.
In the past I have always installed the latest version next to the old version. No documentation responded to my problem.
Even the latest nightly 2016.4.0 behaves erratically.
I am very relieved that the version 2016.2.1 is still working.

All win10 user have some problems ????

Thanks for your responce and help.
Sincerly
D-ABBA

OS WIN10, 64bit, nvidea graficcard....

[Alant]

The --console tag was removed. So this won't work.

See http://wiki.flightgear.org/Howto:Showing_the_FlightGear_console_on_Windows