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.

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby wkitty42 » Thu Mar 22, 2018 7:16 pm

how new of a binary are you running, @RJ5576? can you try a new nightly build? maybe wait until tomorrow after jenkins builds a new one with today's and yesterday's changes?
"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: 9146
Joined: Fri Feb 20, 2015 4:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 20.04

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby RJ5576 » Thu Mar 22, 2018 8:05 pm

I built it yesterday from the tarballs in the "release-candidate" folder of the SF repository.
RJ5576
 
Posts: 86
Joined: Wed Feb 20, 2013 4:24 am
Location: Between KSEA and KPDX
Callsign: RJ5576
Version: 2018.1.1
OS: Linux Mint Sylvia

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby Clive2670 » Thu Mar 22, 2018 9:36 pm

Obviously some major issues still with this release (First instalment of the 2018 versions) as it is now running about 6 weeks behind schedule (of launch date) any sort of ideas of the ballpark date of release yet? It's just an idea....But how about just two releases a year instead of four One in January and one in July maybe, As then there is less pressure on everyone within the team, and it gives enough time to test the release before the date "due" Also it will take into account any third party issues that may arise. As it was a third party issue this time that has put it back wasn't it? Was it servers being upgraded or moving addresses at github or Jenkins or something like that? Lets put it another way "How many updates to any FREEWARE program would you expect in a year?" {Me none} Also PAIDWARE you are lucky to get maybe 2 updates a year!!! So maybe be a little more realistic on updates like 2 instead of 4!!! THIS IS NOT MEANT AS AN ATTACK ON THE TEAM This is just a point of view, I am more than happy with Flightgear :D :D :D Just don't see the point of the team pulling their hair out trying to meet deadlines...more so when they have other commitments in life, Such as a fulltime job, Family, and their sanity! All that to one side keep up the good work EVERYONE on the the Flightgear Team and thank you for a wonderful simulator!!!
Thanks Clive aka: G-BLS01
Can be seen flying the Boeing 777-200LR
Toshiba laptop,
Intel i5 4210U,
16Gb RAM,
AMD R7-M260 graphics 2Gb RAM
Clive2670
 
Posts: 589
Joined: Mon Feb 08, 2016 8:11 pm
Location: Anywhere in the World at some point on Flightgear!
Callsign: G-BLS01
Version: 2018.3.1
OS: Windows 10 64bit

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby Octal450 » Thu Mar 22, 2018 10:26 pm

+1 Clive,
I think 4 is beginning to show it's weak points... while it's nice to get new Developer stuff, and bugfixes, we have not had an FGFS Release in a really long time, and now I already see people using a "2018.2" simulator. I've also seen no clues on the mailing list about this. (but I admit I haven't read it thoroughly recently)

Does anyone know if 2018.1 is also now cancelled?

I think 2 releases might make more sense... gives much more time to get things done, and then if it's ready another release in between?

Kind Regards,
Josh
Skillset: JSBsim Flight Dynamics, Systems, Canvas, Autoflight/Control, Instrumentation, Animations
Aircraft: A320-family, MD-11, MD-80, Contribs in a few others

Octal450's GitHub|Launcher Catalog
|Airbus Dev Discord|Octal450 Hangar Dev Discord
User avatar
Octal450
 
Posts: 5583
Joined: Tue Oct 06, 2015 1:51 pm
Location: Huntsville, AL
Callsign: WTF411
Version: next
OS: Windows 11

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby wkitty42 » Thu Mar 22, 2018 11:43 pm

RJ5576 wrote in Thu Mar 22, 2018 8:05 pm:I built it yesterday from the tarballs in the "release-candidate" folder of the SF repository.

yeah, get a new one now or as soon as possible... there's been some commits today that work towards fixing a bug in the launcher when clicking the [Fly!] button...
"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: 9146
Joined: Fri Feb 20, 2015 4:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 20.04

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby wkitty42 » Thu Mar 22, 2018 11:55 pm

no one is trying to meet any deadlines... if a feature is not ready, it is simply rolled back until after the release and then rolled back in... we've already seen that a few times... i've got freeware and paidware stuff here that used to get updated almost every week... that's slowed down a bit as the developers have gotten more and more busy with their real life jobs and families...

we (TINW) are the testers... that's why the RCs are put out there... developers will generally make sure the updates compile and don't exhibit any glaring errors... after that, it is up to us (TINU) to exercise the product and report any problems...

2018.1.1 is still in RC status... bug fixes have been ported back to it and are being worked on as they are solved...
2018.2.0 is the "next" branch of the code... it will become 2018.2.1 when it gets to that point... anyone running 2018.2 right now is running bleeding edge alpha code... there will be some cuts and bleeding... especially now as the launcher is evolving...

welcome to the rolling updates world... it is quite different than the one with little to no word of development and only one release a year ;)
Last edited by wkitty42 on Thu Apr 12, 2018 1:41 pm, edited 1 time in total.
"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: 9146
Joined: Fri Feb 20, 2015 4:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 20.04

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby RJ5576 » Fri Mar 23, 2018 12:53 am

wkitty42 wrote in Thu Mar 22, 2018 11:43 pm:
RJ5576 wrote in Thu Mar 22, 2018 8:05 pm:I built it yesterday from the tarballs in the "release-candidate" folder of the SF repository.

yeah, get a new one now or as soon as possible... there's been some commits today that work towards fixing a bug in the launcher when clicking the [Fly!] button...


How would I do that?
RJ5576
 
Posts: 86
Joined: Wed Feb 20, 2013 4:24 am
Location: Between KSEA and KPDX
Callsign: RJ5576
Version: 2018.1.1
OS: Linux Mint Sylvia

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby wkitty42 » Sat Mar 24, 2018 4:03 pm

what do you mean? you get it just like you got the one that's broken... if you're doing tarballs, you go get a new set of tarballs and build new binaries... if you're getting the nightly binary builds, you get a new one of those and install it...

truth be told, if you're going to run the bleeding edge stuff, you'd be better off pulling the repositories and building a new binary when there's new commits added to the repo... doing the repo thing is a lot better than doing tarballs... why? you have to download the entire tarball each time whereas when pulling the updates from the repos, you only have those few little changes to pull... the difference in a few k compared to several megabytes is... ummm... well... ;)
Last edited by wkitty42 on Sun Mar 25, 2018 7:26 pm, edited 1 time in total.
"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: 9146
Joined: Fri Feb 20, 2015 4:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 20.04

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby Clive2670 » Sun Mar 25, 2018 7:20 pm

For the record I have been testing 2018.2.0 which I downloaded the 22/03/18 "nightly build" From SF. I have been testing this all weekend and it has run on my machine with no error that I am aware. Maybe this feedback will be of some help to the Devs'
Thanks Clive aka: G-BLS01
Can be seen flying the Boeing 777-200LR
Toshiba laptop,
Intel i5 4210U,
16Gb RAM,
AMD R7-M260 graphics 2Gb RAM
Clive2670
 
Posts: 589
Joined: Mon Feb 08, 2016 8:11 pm
Location: Anywhere in the World at some point on Flightgear!
Callsign: G-BLS01
Version: 2018.3.1
OS: Windows 10 64bit

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby bob755 » Wed Apr 11, 2018 1:47 pm

Installed 2018.2.0 build 2973

This may be a known issue but the selected airport location is not persisted.
When FG is restarted, it reverts to the default PHNL airport.
bob755
 
Posts: 139
Joined: Mon Oct 30, 2017 2:21 pm

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby wkitty42 » Wed Apr 11, 2018 5:05 pm

@bob755: you are using the built-in launcher, right?
"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: 9146
Joined: Fri Feb 20, 2015 4:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 20.04

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby bob755 » Wed Apr 11, 2018 5:09 pm

wkitty42 wrote in Wed Apr 11, 2018 5:05 pm:@bob755: you are using the built-in launcher, right?

Yes.
bob755
 
Posts: 139
Joined: Mon Oct 30, 2017 2:21 pm

FlightGear 2018.1.1 Released

Postby Necolatis » Wed Apr 11, 2018 5:36 pm

In case you missed it, 2018.1.1 have been released, also the website seems to have been updated.
"Airplane travel is nature's way of making you look like your passport photo."
— Al Gore
User avatar
Necolatis
 
Posts: 2233
Joined: Mon Oct 29, 2012 1:40 am
Location: EKOD
Callsign: Leto
IRC name: Neco
Version: 2020.3.19
OS: Windows 10

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby wkitty42 » Wed Apr 11, 2018 9:02 pm

@bob755, what OS are you on?
how are you exiting the sim? via the proper exit option or clicking the 'X' in the frame to close the window?
"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: 9146
Joined: Fri Feb 20, 2015 4:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 20.04

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby bob755 » Thu Apr 12, 2018 9:38 am

@wkitty42,

OS is Windows 7. I checked again, exiting via the Quit menu choice but the location is still not persisted.
The aircraft type and other settings such as the add-ons are kept. Only the location defaults back each time.
The list of previously used location is also preserved.

I don't know if this is related but I was previously using 2017.3.1. I installed 2018.2.0 without deinstalling 2017. The installation folders are different and I deleted the contents of .../AppData/Roaming/flightgear.org before launching for the fist time.

Update: I don't know what happened but I cut/pasted the shortcut from the desktop to a folder and when I stated FG it popped up a message saying it was migrating settings an now the location is persisted.
bob755
 
Posts: 139
Joined: Mon Oct 30, 2017 2:21 pm

PreviousNext

Return to Development

Who is online

Users browsing this forum: No registered users and 8 guests