Board index FlightGear Development

FlightGear 2018.1.1 Release Candidate: Please test!

FlightGear is opensource, so you can be the developer. In the need for help on anything? We are here to help you.
Forum rules
Core development is discussed on the official FlightGear-Devel development mailing list.

Bugs can be reported in the bug tracker.

FlightGear 2018.1.1 Release Candidate: Please test!

Postby BEL ISAAK » Fri Feb 23, 2018 8:16 am

Hi all,

Torsten managed to build the first release candidates for the upcoming FlightGear 2018.1.1 release:

Hi,

after some really annoying issues following SourceForge move to a new datacenter, I finally managed to bake the release candidates for OSX and Windows.
They are available at our usual place: https://sourceforge.net/projects/flight ... candidate/

If you don't mind a 1.6GB download, please give it a try and report if it at lest
- Download and install cleanly (fresh install and update)
- Spawns a C172 at PHNL
- There is nice looking Hawaii scenery around you

Regards
Torsten
--
Torsten Dreyer


Please, feel free to test these release candidates and report any issues on the Developers Mailing List. We did already find some issues and SourceForge (our host) is having difficult times, so it might take some time to get the stable release out. This means testing the candidates is crucial to rule out possible bugs.
User avatar
BEL ISAAK
 
Posts: 179
Joined: Sat Jun 04, 2011 2:52 pm
Location: Leuven, Belgium
Callsign: OO-ISA
Version: 2017.3.1
OS: Windows

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby Catalanoic » Fri Feb 23, 2018 1:31 pm

I can't see PHIK Hickam airbase next to PHNL.
User avatar
Catalanoic
 
Posts: 988
Joined: Mon Mar 05, 2012 12:33 am
Location: Barcelona (LEBL)
Callsign: Catalanoic
Version: 2017.3
OS: Lubuntu/Windows 7

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby wkitty42 » Fri Feb 23, 2018 6:01 pm

IIRC, they share the same runway and some land area... in Google Maps and Google Earth, there is no longer a separate airport indicator for PHIK...
"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: 4641
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby Clive2670 » Fri Feb 23, 2018 6:27 pm

Downloaded now going to trial!
Thanks Clive aka: G-BLS01, BIGJET1
Can be seen flying the Boeing 777-200LR
Toshiba laptop,
Intel i5 4210U,
16Gb RAM,
AMD R7-M260 graphics 2Gb RAM
User avatar
Clive2670
 
Posts: 577
Joined: Mon Feb 08, 2016 7:11 pm
Location: Anywhere in the World at some point on Flightgear!
Callsign: G-BLS01, BIGJET1
Version: 2018.1.1
OS: Windows 10 64bit

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby Clive2670 » Fri Feb 23, 2018 6:44 pm

when i go to "install" the flightgear default aircraft hangar I keep getting back a box telling me that the "provided hangar is for a different version of flightgear (This is version 2018.1.1) Any ideas?
Thanks Clive aka: G-BLS01, BIGJET1
Can be seen flying the Boeing 777-200LR
Toshiba laptop,
Intel i5 4210U,
16Gb RAM,
AMD R7-M260 graphics 2Gb RAM
User avatar
Clive2670
 
Posts: 577
Joined: Mon Feb 08, 2016 7:11 pm
Location: Anywhere in the World at some point on Flightgear!
Callsign: G-BLS01, BIGJET1
Version: 2018.1.1
OS: Windows 10 64bit

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby Thorsten » Fri Feb 23, 2018 6:46 pm

Sounds like it'll change as soon as the RC becomes a R - just don't install and test with the aircraft you already have.
Thorsten
 
Posts: 9753
Joined: Mon Nov 02, 2009 8:33 am

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby Clive2670 » Fri Feb 23, 2018 6:50 pm

OK thanks Thorsten, Any ideas when full version is due out?
Thanks Clive aka: G-BLS01, BIGJET1
Can be seen flying the Boeing 777-200LR
Toshiba laptop,
Intel i5 4210U,
16Gb RAM,
AMD R7-M260 graphics 2Gb RAM
User avatar
Clive2670
 
Posts: 577
Joined: Mon Feb 08, 2016 7:11 pm
Location: Anywhere in the World at some point on Flightgear!
Callsign: G-BLS01, BIGJET1
Version: 2018.1.1
OS: Windows 10 64bit

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby Thorsten » Fri Feb 23, 2018 6:54 pm

Since I've reported what might be a pretty serious bug in the launcher, it depends on how quickly this can be dealt with some way or the other. Currently the process is on hold pending an investigation into this.
Thorsten
 
Posts: 9753
Joined: Mon Nov 02, 2009 8:33 am

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby Clive2670 » Fri Feb 23, 2018 7:22 pm

OK cheers keep up all the hard work (Everyone involved) as any release is worth the wait, if it means it is near on bug free!
Thanks Clive aka: G-BLS01, BIGJET1
Can be seen flying the Boeing 777-200LR
Toshiba laptop,
Intel i5 4210U,
16Gb RAM,
AMD R7-M260 graphics 2Gb RAM
User avatar
Clive2670
 
Posts: 577
Joined: Mon Feb 08, 2016 7:11 pm
Location: Anywhere in the World at some point on Flightgear!
Callsign: G-BLS01, BIGJET1
Version: 2018.1.1
OS: Windows 10 64bit

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby Catalanoic » Fri Feb 23, 2018 7:49 pm

@wkitty42: Yes, but the layout in actual FG for the PHIK is inexistent, so you may see some buildings and objects on grass or outside PHNL boundaries. Despite nice work from xDraconian but unshipped we havent seen any improvement on that old layout for years. anyway the whole island looks increible nice and at least that release candidate works well on my system.
User avatar
Catalanoic
 
Posts: 988
Joined: Mon Mar 05, 2012 12:33 am
Location: Barcelona (LEBL)
Callsign: Catalanoic
Version: 2017.3
OS: Lubuntu/Windows 7

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby yanes » Fri Feb 23, 2018 9:17 pm

Sorry , I'm not at home (currently on broadband connection) , But I want to ask if it's built on osg 3.4 and if yes , is the incompatibility/bug in the osgtext fixed .

Thanks, & keep up the good job !
User avatar
yanes
 
Posts: 108
Joined: Tue Sep 02, 2014 1:14 pm
Location: Tunisia
Callsign: YANES
Version: 2018.2.2
OS: Linux

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby legoboyvdlp » Sat Feb 24, 2018 1:34 am

@Thorsten with regards to what was put on the blog, if the airports were regenerated, what happened to the default airport itself... PHNL? ;)

Unfortunately, at least right now, I don't think the new layout made it into the scenery that ships with FlightGear... unless I made some error with my priority settings on the scenery.
User avatar
legoboyvdlp
 
Posts: 5516
Joined: Sat Jul 26, 2014 1:28 am
Callsign: YV-LEGO
Version: 2018.3.1
OS: Windows 10 HP

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby Thorsten » Sat Feb 24, 2018 6:57 am

I learned myself a day ago to my surprise that Torsten did in fact not include the re-generated Oahu scenery on terrasync or into the RC - I was under the assumption from previous exchanges that xDraconian's project gets in for the release.
Thorsten
 
Posts: 9753
Joined: Mon Nov 02, 2009 8:33 am

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby mermar » Sat Feb 24, 2018 11:56 am

Any of
Code: Select all
--prop:/sim/rendering/multi-samples=8
--prop:/sim/rendering/multi-sample-buffers=1
causes segfault.

Code: Select all
Reading symbols from ./install/flightgear/bin/fgfs...done.
[New LWP 18256]
[New LWP 18260]
[New LWP 18275]
[New LWP 18277]
[New LWP 18279]
[New LWP 18276]
[New LWP 18278]
[New LWP 18280]
[New LWP 18281]
[New LWP 18282]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `./fgfs --fg-root=/data2/fgfs/next/install/flightgear/bin/../fgdata/ --prop:/sim'.

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000557b2b00ed25 in osg::ref_ptr<osg::GraphicsContext>::operator-> (this=<optimized out>)
    at /usr/include/osg/ref_ptr:91
91           T* operator->() const { return _ptr; }
[Current thread is 1 (Thread 0x7f84bdcbd480 (LWP 18256))]
(gdb) bt
#0  0x0000557b2b00ed25 in osg::ref_ptr<osg::GraphicsContext>::operator-> (this=<optimized out>)
    at /usr/include/osg/ref_ptr:91
#1  guiInit () at /data2/fgfs/next/flightgear/src/GUI/gui.cxx:175
#2  0x0000557b2ae2beb5 in fgIdleFunction () at /data2/fgfs/next/flightgear/src/Main/main.cxx:257
#3  0x0000557b2b5a7238 in fgOSMainLoop ()
    at /data2/fgfs/next/flightgear/src/Viewer/fg_os_osgviewer.cxx:342
#4  0x0000557b2ae3151f in fgMainInit (argc=<optimized out>, argv=<optimized out>)
    at /data2/fgfs/next/flightgear/src/Main/main.cxx:615
#5  0x0000557b2add4051 in main (argc=11, argv=0x7ffd7b031968)
    at /data2/fgfs/next/flightgear/src/Main/bootstrap.cxx:341

Ubuntu 17.10 with Wayland.
mermar
 
Posts: 9
Joined: Sat Mar 19, 2016 7:58 am

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby BEL ISAAK » Sat Feb 24, 2018 5:14 pm

One graphical bug I encounterd is this one: in the 777, on the PFD and the EICAS (not on the ND), text previously colored green or magenta is now colored white (e.g. speed, altitude, radio altitude, QNH...) I didn't modify anything in the aircraft files while transitioning to 2018.1.1. Does anyone have any idea where I should look to find the cause? Switching between ALS and default renderer doesn't seem to solve anything.

Thanks a lot!

Image
User avatar
BEL ISAAK
 
Posts: 179
Joined: Sat Jun 04, 2011 2:52 pm
Location: Leuven, Belgium
Callsign: OO-ISA
Version: 2017.3.1
OS: Windows

Next

Return to Development

Who is online

Users browsing this forum: No registered users and 1 guest