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 Apr 12, 2018 12:46 pm

i was just fixing to say that there is migration code in the binaries so removing previous configuration data should not be necessary any more like it may have been at some point in the past... uninstalling previous versions should not be necessary... perhaps your shortcut hadn't been updated? i dunno and don't have any way to test them...
"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: 4755
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 bob755 » Thu Apr 12, 2018 2:48 pm

I decided to move to the stable release 2018.1.1.
With the version 2017.3.1, I've been successfully trying the connection to VatSim using this tutorial: http://thejabberwocky.net/viewtopic.php?f=23&t=1032

When I try with 2018.1.1 there is a telnet connection problem between FG and SquawkGear when FG is started:

2018.1.1 :
Image

2017.3.1:
Image

The command line options are the same for both:

"C:\Program Files\FlightGear 2018.1.1\bin\fgfs.exe" --launcher --generic=socket,out,1,127.0.0.1,1863,tcp,squawk --telnet=socket,in,1,127.0.0.1,5900,tcp --multiplay=out,10,mpserver01.flightgear.org,0 --multiplay=in,10,,5000 --telnet=5401
bob755
 
Posts: 139
Joined: Mon Oct 30, 2017 1:21 pm

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby wkitty42 » Thu Apr 12, 2018 3:44 pm

yeah, you'll want to look and see if there's an area here on these forums for VATSIM related discussions... if there is, post your problem there instead of in this topic... this topic can actually be closed now since the release is out and we don't need to test the RCs any more ;) if there's no area available here for VATSIM stuff, you'll probably have to ask over there on that other forum for assistance...

i don't know anything about VATSIM so i can't really help there but i will ask how you're passing the related parameters to FG... are you putting them into the "Additional Settings" section of the launcher's "Settings" tab?


[edit]

ahhh... i see your command line at the bottom of your post... i don't see anything immediately wrong with it but that doesn't mean much in this case...
"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: 4755
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 bob755 » Thu Apr 12, 2018 3:56 pm

The thing is that it works fine with 2017.3.1.
It seems to be a Telnet issue between FG and Sqawkgear so isn't really VatSim.

I don't know anything about Sqawkgear but it appears that FG is initiating a connection to port 55225. This doesn't appear to be happening with FG 2018.1.1
bob755
 
Posts: 139
Joined: Mon Oct 30, 2017 1:21 pm

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby BEL ISAAK » Thu Apr 12, 2018 4:18 pm

Last week I managed to finally make connection to VATSIM, it runs fine on my (Win 10) computer and FG 2018.1.1. Did you not forget to copy the squawk.xml, radios.xml etc files from your Squawkgear install folder to fgdata?
User avatar
BEL ISAAK
 
Posts: 208
Joined: Sat Jun 04, 2011 2:52 pm
Location: Leuven, Belgium
Callsign: OO-ISA
Version: 2018.2.2
OS: Windows 10

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby bob755 » Thu Apr 12, 2018 6:54 pm

BEL ISAAK wrote in Thu Apr 12, 2018 4:18 pm:Last week I managed to finally make connection to VATSIM, it runs fine on my (Win 10) computer and FG 2018.1.1. Did you not forget to copy the squawk.xml, radios.xml etc files from your Squawkgear install folder to fgdata?


Exactly!! I completely forgot this.

Thanks very much
bob755
 
Posts: 139
Joined: Mon Oct 30, 2017 1:21 pm

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby camileck » Fri Apr 13, 2018 12:06 am

When the *. deb packages (Ubuntu) can be expected?
camileck
 
Posts: 47
Joined: Thu Jul 27, 2017 8:17 pm

Re: FlightGear 2018.1.1 Release Candidate: Please test!

Postby wkitty42 » Fri Apr 13, 2018 4:50 pm

the .deb for the release? i don't know... i don't know who manages that... the only one i know of is the PPA operated by saircot here in the forum... i don't remember the digits on the end of their handle :( you can search their name in the members list and inquire of them if they know...
"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: 4755
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 camileck » Fri Apr 13, 2018 5:32 pm

That's exactly what I did, I hope he does not mind if I post his reply here :) :

Hi,

I'll be uploading the new version this weekend.
camileck
 
Posts: 47
Joined: Thu Jul 27, 2017 8:17 pm

Previous

Return to Development

Who is online

Users browsing this forum: No registered users and 3 guests