Board index FlightGear The FlightGear project

Why is the Ubuntu FlightGear package an older version?

Questions about the FlightGear organisation, website, wiki etc.

Re: METAR not working

Postby SurferTim » Sat Aug 10, 2019 9:58 am

Alant wrote in Sat Aug 10, 2019 9:52 am:Please read the wiki article. The script builds either the latest development or the release version. You can choose..

i have the Ubuntu "current stable version" 2018.3.1 from the saircot ppa.

The development version was full of bugs last I checked.

If this is all so easy (as I have said before), why is the "current stable version" not on the saircot ppa?
Fly low, fly slow, land on a dime. Twin Otter.
SurferTim
 
Posts: 395
Joined: Sun Dec 09, 2018 5:49 pm
Location: Miramar Beach, FL
Callsign: Pirate
Version: 2019.2.0
OS: Ubuntu 18.04

Re: METAR not working

Postby SurferTim » Sat Aug 10, 2019 10:58 am

SWING AND A MISS!! STRIKE 2!!

The download_and_compile.sh script worked! It installed v2019.2.0. Then why the "STRIKE 2"? No data files are available for that version.

When I run the run_fgfs.sh, it pops up a window asking for data files, and a download button if you don't have them yet. Click on the download button and FAIL! A fancy version of error 404. No data files. :cry:
Fly low, fly slow, land on a dime. Twin Otter.
SurferTim
 
Posts: 395
Joined: Sun Dec 09, 2018 5:49 pm
Location: Miramar Beach, FL
Callsign: Pirate
Version: 2019.2.0
OS: Ubuntu 18.04

Re: METAR not working

Postby Alant » Sat Aug 10, 2019 11:13 am

A git pull from https://git.code.sf.net/p/flightgear/fgdata will give you that version of fgdata.
Alant
 
Posts: 914
Joined: Wed Jun 23, 2010 5:58 am
Location: Portugal
Callsign: Tarnish99
Version: from Git
OS: Windows 10

Re: METAR not working

Postby legoboyvdlp » Sat Aug 10, 2019 11:55 am

SurferTim wrote in Sat Aug 10, 2019 9:58 am:The development version was full of bugs last I checked.

If this is all so easy (as I have said before), why is the "current stable version" not on the saircot ppa?


because you're talking to people here who have no control over saircot's ppa, not to saircot...?

And are these bugs linux-specific, because 2019.2 is rather stable right now.
User avatar
legoboyvdlp
 
Posts: 7129
Joined: Sat Jul 26, 2014 1:28 am
Callsign: YV-LEGO
Version: 2018.3.1
OS: Windows 10 HP

Re: METAR not working

Postby SurferTim » Sat Aug 10, 2019 12:32 pm

I tried communicating with saircot with only partial results. At one point he recommended I purge my copy of flightgear and reinstall. That didn't go well at first. Much swearing, wailing, and gnashing of teeth. :cry:

So far, this download_and_compile.sh script is about as close as I have come to upgrading. The data is all I have remaining to download, but have run into a bit of difficulty with that. I'll let you know how I did.
Fly low, fly slow, land on a dime. Twin Otter.
SurferTim
 
Posts: 395
Joined: Sun Dec 09, 2018 5:49 pm
Location: Miramar Beach, FL
Callsign: Pirate
Version: 2019.2.0
OS: Ubuntu 18.04

Re: METAR not working

Postby legoboyvdlp » Sat Aug 10, 2019 12:34 pm

was that his response when you asked him if he could upgrade to 2018.3.3...?
User avatar
legoboyvdlp
 
Posts: 7129
Joined: Sat Jul 26, 2014 1:28 am
Callsign: YV-LEGO
Version: 2018.3.1
OS: Windows 10 HP

Re: METAR not working

Postby SurferTim » Sat Aug 10, 2019 12:37 pm

legoboyvdlp wrote in Sat Aug 10, 2019 12:34 pm:was that his response when you asked him if he could upgrade to 2018.3.3...?

No. That was a while ago when the daily beta failed and I had to back up to a stable version (2018.3.1). No response since.

If this script works, that is the ticket. Once I had the beta version purged, the script worked, except the data.
Fly low, fly slow, land on a dime. Twin Otter.
SurferTim
 
Posts: 395
Joined: Sun Dec 09, 2018 5:49 pm
Location: Miramar Beach, FL
Callsign: Pirate
Version: 2019.2.0
OS: Ubuntu 18.04

Re: METAR not working

Postby legoboyvdlp » Sat Aug 10, 2019 12:40 pm

Ah ok. I still don't get why that means he can't upgrade his PPA to the newest version though. It might be worth asking him again.
User avatar
legoboyvdlp
 
Posts: 7129
Joined: Sat Jul 26, 2014 1:28 am
Callsign: YV-LEGO
Version: 2018.3.1
OS: Windows 10 HP

Re: METAR not working

Postby SurferTim » Sat Aug 10, 2019 1:06 pm

OK, I had to change to git call a bit to get it to work:
Code: Select all
git clone git://git.code.sf.net/p/flightgear/fgdata


The download_and_compile.sh script needs to be edited to use that call. Otherwise, it will fail.

I am now running 2019.2.0. I'll take a lap around the Caribbean to see how well it works.
Fly low, fly slow, land on a dime. Twin Otter.
SurferTim
 
Posts: 395
Joined: Sun Dec 09, 2018 5:49 pm
Location: Miramar Beach, FL
Callsign: Pirate
Version: 2019.2.0
OS: Ubuntu 18.04

Re: METAR not working

Postby wkitty42 » Sat Aug 10, 2019 8:55 pm

SurferTim wrote in Sat Aug 10, 2019 10:58 am:The download_and_compile.sh script worked! It installed v2019.2.0. Then why the "STRIKE 2"? No data files are available for that version.

what options have you told the dnc script to use?

i generally use these in my wrapper script to i build the same every time... the following is for a normal release type build...
Code: Select all
CFLAGS="-march=native" CPPFLAGS="-march=native" $MYFGBASEDIR/dnc.sh -a n -p n -j $(($(nproc)-1)) -b RelWithDebInfo -f Release PLIB OSG SIMGEAR FGFS DATA
"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: 5722
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: METAR not working

Postby SurferTim » Sat Aug 10, 2019 9:18 pm

Eventually, this did it.
Code: Select all
./download_and_compile.sh --git-clone-default-proto=git SIMGEAR FGFS DATA


It worked on Ubuntu 18.04, but I still have trouble with Ubuntu 16.04. No big deal though.
Fly low, fly slow, land on a dime. Twin Otter.
SurferTim
 
Posts: 395
Joined: Sun Dec 09, 2018 5:49 pm
Location: Miramar Beach, FL
Callsign: Pirate
Version: 2019.2.0
OS: Ubuntu 18.04

Re: Why is the Ubuntu FlightGear package an older version?

Postby V12 » Tue Aug 13, 2019 3:47 pm

SurferTim ?
What is Your opinion from that new version ? Is there jittering, frame pausing and other glitches known from 2018.X.X. version ? Have You better fps ?
Fly high, fly fast - fly Concorde !
User avatar
V12
 
Posts: 1592
Joined: Thu Jan 12, 2017 4:27 pm
Location: LZIB
Callsign: BAWV12

Re: METAR not working

Postby xDraconian » Fri Sep 13, 2019 7:09 pm

wkitty42 wrote in Sat Aug 10, 2019 8:55 pm:i generally use these in my wrapper script to i build the same every time... the following is for a normal release type build...
Code: Select all
CFLAGS="-march=native" CPPFLAGS="-march=native" $MYFGBASEDIR/dnc.sh -a n -p n -j $(($(nproc)-1)) -b RelWithDebInfo -f Release PLIB OSG SIMGEAR FGFS DATA


@wkitty,
"-march=native" may not be doing what you think it is doing. It will produce good code, but not necessarily the best code for your hardware.

Run this code to see what GCC believes your chipset is:
Code: Select all
gcc -march=native -Q --help=target | grep -- '-march='

broadwell

Run this code to see what hardware the code is being tuned for:
Code: Select all
gcc -march=native -Q --help=target | grep -- '-mtune='

generic

Run this to understand what family of instructions is being generated:
Code: Select all
gcc -mtune=generic -Q --help=target | grep -- '-march='

x86-64

So this implies that the compiler is generating code that is optimized generically for all x86-64 machines but will run best on the broadwell chipset.

Run this to get a better optimization strategy:
Code: Select all
gcc -march=broadwell -Q --help=target | grep -- '-mtune='

broadwell

This implies that the compiler is generating code that is optimized for broadwell machines that support the broadwell chipset or better. The code will fail to execute on any machine not supporting the broadwell instruction set.

Scott
xDraconian
 
Posts: 240
Joined: Sun Jan 21, 2018 5:53 am
Version: Git
OS: Linux Mint

Re: METAR not working

Postby wkitty42 » Sat Sep 14, 2019 9:15 pm

xDraconian wrote in Fri Sep 13, 2019 7:09 pm:
wkitty42 wrote in Sat Aug 10, 2019 8:55 pm:i generally use these in my wrapper script to i build the same every time... the following is for a normal release type build...
Code: Select all
CFLAGS="-march=native" CPPFLAGS="-march=native" $MYFGBASEDIR/dnc.sh -a n -p n -j $(($(nproc)-1)) -b RelWithDebInfo -f Release PLIB OSG SIMGEAR FGFS DATA


@wkitty,
"-march=native" may not be doing what you think it is doing. It will produce good code, but not necessarily the best code for your hardware.

i got it from the dev mailing list and tried it... it seems to work fine so i've simply left it in place...

xDraconian wrote in Fri Sep 13, 2019 7:09 pm:Run this code to see what GCC believes your chipset is:
[trim]
So this implies that the compiler is generating code that is optimized generically for all x86-64 machines but will run best on the broadwell chipset.

Code: Select all
gcc -march=native -Q --help=target | grep -- '-march='
  -march=                               bdver2

gcc -march=native -Q --help=target | grep -- '-mtune='
  -mtune=                               bdver2

gcc -mtune=generic -Q --help=target | grep -- '-march='
  -march=                               x86-64


xDraconian wrote in Fri Sep 13, 2019 7:09 pm:Run this to get a better optimization strategy:
Code: Select all
gcc -march=broadwell -Q --help=target | grep -- '-mtune='

This implies that the compiler is generating code that is optimized for broadwell machines that support the broadwell chipset or better. The code will fail to execute on any machine not supporting the broadwell instruction set.

i think you are saying that i should use "-march=bdver2" for my system to get the best code generated?? when i run this command with "bdver2" as indicated by the other output, i get this...
Code: Select all
gcc -march=bdver2 -Q --help=target | grep -- '-mtune='
  -mtune=                     

comparing the full output of "-march=native", "-march=broadwell", and "-march=bdver" certainly shows some things being disabled between "-march=native" and "broadwell" and "bdver2"...

i'm not compiling for any other machines than my own right now... if/when i have others that want to run the latest FG, i set up a full build configuration on their machine and build it for their environment...

Code: Select all
--- march-native.txt    2019-09-14 16:54:34.066746825 -0400
+++ march-broadwell.txt 2019-09-14 16:54:53.966747196 -0400
-  -mabm                                [enabled]
+  -mabm                                [disabled]
-  -maes                                [enabled]
+  -maes                                [disabled]
-  -march=                              bdver2
+  -march=                              broadwell
-  -mavx                                [enabled]
+  -mavx                                [disabled]
-  -mbmi                                [enabled]
+  -mbmi                                [disabled]
-  -mcx16                               [enabled]
+  -mcx16                               [disabled]
-  -mf16c                               [enabled]
+  -mf16c                               [disabled]
-  -mfma                                [enabled]
+  -mfma                                [disabled]
-  -mfma4                               [enabled]
+  -mfma4                               [disabled]
-  -mfxsr                               [enabled]
+  -mfxsr                               [disabled]
-  -mlwp                                [enabled]
+  -mlwp                                [disabled]
-  -mlzcnt                              [enabled]
+  -mlzcnt                              [disabled]
-  -mno-sse4                            [disabled]
+  -mno-sse4                            [enabled]
-  -mpclmul                             [enabled]
+  -mpclmul                             [disabled]
-  -mpopcnt                             [enabled]
+  -mpopcnt                             [disabled]
-  -mprfchw                             [enabled]
+  -mprfchw                             [disabled]
-  -msahf                               [enabled]
+  -msahf                               [disabled]
-  -msse                                [enabled]
+  -msse                                [disabled]
-  -msse2                               [enabled]
+  -msse2                               [disabled]
-  -msse3                               [enabled]
+  -msse3                               [disabled]
-  -msse4                               [enabled]
+  -msse4                               [disabled]
-  -msse4.1                             [enabled]
+  -msse4.1                             [disabled]
-  -msse4.2                             [enabled]
+  -msse4.2                             [disabled]
-  -msse4a                              [enabled]
+  -msse4a                              [disabled]
-  -mssse3                              [enabled]
+  -mssse3                              [disabled]
-  -mtbm                                [enabled]
+  -mtbm                                [disabled]
-  -mtune=                              bdver2
+  -mtune=                     
-  -mxop                                [enabled]
+  -mxop                                [disabled]
-  -mxsave                              [enabled]
+  -mxsave                              [disabled]


Code: Select all
diff -Naur march-native.txt march-bdver2.txt | egrep -e "^[-+]"
--- march-native.txt    2019-09-14 16:54:34.066746825 -0400
+++ march-bdver2.txt    2019-09-14 16:55:08.090747459 -0400
-  -mabm                                [enabled]
+  -mabm                                [disabled]
-  -maes                                [enabled]
+  -maes                                [disabled]
-  -mavx                                [enabled]
+  -mavx                                [disabled]
-  -mbmi                                [enabled]
+  -mbmi                                [disabled]
-  -mcx16                               [enabled]
+  -mcx16                               [disabled]
-  -mf16c                               [enabled]
+  -mf16c                               [disabled]
-  -mfma                                [enabled]
+  -mfma                                [disabled]
-  -mfma4                               [enabled]
+  -mfma4                               [disabled]
-  -mfxsr                               [enabled]
+  -mfxsr                               [disabled]
-  -mlwp                                [enabled]
+  -mlwp                                [disabled]
-  -mlzcnt                              [enabled]
+  -mlzcnt                              [disabled]
-  -mno-sse4                            [disabled]
+  -mno-sse4                            [enabled]
-  -mpclmul                             [enabled]
+  -mpclmul                             [disabled]
-  -mpopcnt                             [enabled]
+  -mpopcnt                             [disabled]
-  -mprfchw                             [enabled]
+  -mprfchw                             [disabled]
-  -msahf                               [enabled]
+  -msahf                               [disabled]
-  -msse                                [enabled]
+  -msse                                [disabled]
-  -msse2                               [enabled]
+  -msse2                               [disabled]
-  -msse3                               [enabled]
+  -msse3                               [disabled]
-  -msse4                               [enabled]
+  -msse4                               [disabled]
-  -msse4.1                             [enabled]
+  -msse4.1                             [disabled]
-  -msse4.2                             [enabled]
+  -msse4.2                             [disabled]
-  -msse4a                              [enabled]
+  -msse4a                              [disabled]
-  -mssse3                              [enabled]
+  -mssse3                              [disabled]
-  -mtbm                                [enabled]
+  -mtbm                                [disabled]
-  -mtune=                              bdver2
+  -mtune=                     
-  -mxop                                [enabled]
+  -mxop                                [disabled]
-  -mxsave                              [enabled]
+  -mxsave                              [disabled]


Code: Select all
diff -Naur march-broadwell.txt march-bdver2.txt | egrep -e "^[-+]"
--- march-broadwell.txt 2019-09-14 16:54:53.966747196 -0400
+++ march-bdver2.txt    2019-09-14 16:55:08.090747459 -0400
-  -march=                              broadwell
+  -march=                              bdver2

so it appears that my bdver2 is very closely related to broadwell... also that there is no sse4 available (no-sse4 is now enabled)... hummm...
"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: 5722
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: METAR not working

Postby xDraconian » Sun Sep 15, 2019 1:38 am

Code: Select all
gcc -march=native -Q --help=target | grep -- '-march='
  -march=                               bdver2

gcc -march=native -Q --help=target | grep -- '-mtune='
  -mtune=                               bdver2

given: -march=native
results in: -march=bdver2 and -mtune=bdver2

These are the desired results, so you can keep using -march=native.
xDraconian
 
Posts: 240
Joined: Sun Jan 21, 2018 5:53 am
Version: Git
OS: Linux Mint

PreviousNext

Return to The FlightGear project

Who is online

Users browsing this forum: Leon Portier and 2 guests