Board index FlightGear Development Scenery

2018.3 Release

Questions and discussion about enhancing and populating the FlightGear world.

Re: 2018.3 Release

Postby BEL ISAAK » Sat Nov 10, 2018 8:58 pm

You have to subscribe to the mailinglist, you can do that here. Be advised that you will receive tons of emails so some message rules might come in handy.
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: 2018.3 Release

Postby Picun_1812 » Mon Nov 12, 2018 3:33 pm

Hello everyone, thank you very much for the great job you do!

I downloaded the candidate launch of 2018.3.0 in Windows 10 and I have noticed a possible error. In the new flight planner, if you press <see route> before entering data, Flightgear closes automatically without any error.
Picun_1812
 
Posts: 7
Joined: Thu May 10, 2018 7:45 pm

Re: 2018.3 Release

Postby lucrus » Mon Nov 12, 2018 6:06 pm

I've build 2018.3 from sources on Linux (because I wanted to test it, but I couldn't find any 2018.3 precompiled Linux downloads). During startup, when it shows "initializing subsystems", it immediately shuts down and reports the following on the terminal:

Code: Select all
lucio@fx:~/programmi/flightgear/exe$ bin/fgfs
FlightGear:  Version 2018.3.1
FlightGear:  Build Type Dev
Built with GNU C++ version 8.2
Jenkins number/ID 0:none
Settings migrated: Saved settings were migrated from a previous version of FlightGear. If you encounter any problems when using the system, try restoring the default settings, before reporting a problem. Saved settings can affect the appearance, performance and features of the simulator.
FGPropertyManager::GetNode() No node found for hydro/active-norm
Error: caught signal 11:
  /lib/x86_64-linux-gnu/libc.so.6 : ()+0x35fc0
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6 : __dynamic_cast()+0x17
  bin/fgfs : ()+0x1f0565f
  bin/fgfs : SGTextureStateAttributeVisitor::apply(int, std::map<std::pair<osg::StateAttribute::Type, unsigned int>, std::pair<osg::ref_ptr<osg::StateAttribute>, unsigned int>, std::less<std::pair<osg::StateAttribute::Type, unsigned int> >, std::allocator<std::pair<std::pair<osg::StateAttribute::Type, unsigned int> const, std::pair<osg::ref_ptr<osg::StateAttribute>, unsigned int> > > >&)+0x85
  bin/fgfs : SGTextureStateAttributeVisitor::apply(std::vector<std::map<std::pair<osg::StateAttribute::Type, unsigned int>, std::pair<osg::ref_ptr<osg::StateAttribute>, unsigned int>, std::less<std::pair<osg::StateAttribute::Type, unsigned int> >, std::allocator<std::pair<std::pair<osg::StateAttribute::Type, unsigned int> const, std::pair<osg::ref_ptr<osg::StateAttribute>, unsigned int> > > >, std::allocator<std::map<std::pair<osg::StateAttribute::Type, unsigned int>, std::pair<osg::ref_ptr<osg::StateAttribute>, unsigned int>, std::less<std::pair<osg::StateAttribute::Type, unsigned int> >, std::allocator<std::pair<std::pair<osg::StateAttribute::Type, unsigned int> const, std::pair<osg::ref_ptr<osg::StateAttribute>, unsigned int> > > > > >&)+0x64
  bin/fgfs : SGTextureStateAttributeVisitor::apply(osg::StateSet*)+0x43
  bin/fgfs : ()+0x1f0571f
  bin/fgfs : SGTextureStateAttributeVisitor::apply(osg::Geode&)+0x98
  /usr/lib/x86_64-linux-gnu/libosgDB.so.100 : osg::Geode::accept(osg::NodeVisitor&)+0x89
  /usr/lib/x86_64-linux-gnu/libosg.so.100 : osg::Group::traverse(osg::NodeVisitor&)+0x33
  bin/fgfs : osg::NodeVisitor::traverse(osg::Node&)+0x69
  bin/fgfs : SGTextureStateAttributeVisitor::apply(osg::Node&)+0x4f
  bin/fgfs : osg::Group::accept(osg::NodeVisitor&)+0x58
  /usr/lib/x86_64-linux-gnu/libosg.so.100 : osg::Group::traverse(osg::NodeVisitor&)+0x33
  bin/fgfs : osg::NodeVisitor::traverse(osg::Node&)+0x69
  bin/fgfs : SGTextureStateAttributeVisitor::apply(osg::Node&)+0x4f
  bin/fgfs : osg::Group::accept(osg::NodeVisitor&)+0x58
  /usr/lib/x86_64-linux-gnu/libosg.so.100 : osg::Group::traverse(osg::NodeVisitor&)+0x33
  bin/fgfs : osg::NodeVisitor::traverse(osg::Node&)+0x69
  bin/fgfs : SGTextureStateAttributeVisitor::apply(osg::Node&)+0x4f
  bin/fgfs : osg::Group::accept(osg::NodeVisitor&)+0x58
  /usr/lib/x86_64-linux-gnu/libosg.so.100 : osg::Group::traverse(osg::NodeVisitor&)+0x33
  bin/fgfs : osg::NodeVisitor::traverse(osg::Node&)+0x69
  bin/fgfs : SGTextureStateAttributeVisitor::apply(osg::Node&)+0x4f
  bin/fgfs : osg::Group::accept(osg::NodeVisitor&)+0x58
  bin/fgfs : simgear::OptimizeModelPolicy::optimize(osg::Node*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osgDB::Options const*)+0x8b
  bin/fgfs : ACOptimizePolicy::optimize(osg::Node*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osgDB::Options const*)+0x31
  bin/fgfs : simgear::ModelRegistryCallback<ACProcessPolicy, simgear::DefaultCachePolicy, ACOptimizePolicy, simgear::OSGSubstitutePolicy, simgear::BuildLeafBVHPolicy>::readNode(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osgDB::Options const*)+0x26e
  bin/fgfs : simgear::ModelRegistry::readNode(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osgDB::Options const*)+0x139
  /usr/lib/x86_64-linux-gnu/libosgDB.so.100 : osgDB::readNodeFile(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osgDB::Options const*)+0x1c1
  bin/fgfs : ()+0x1f23f94
  bin/fgfs : simgear::SGReaderWriterXML::readNode(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osgDB::Options const*) const+0x11b
  bin/fgfs : simgear::ModelRegistryCallback<simgear::DefaultProcessPolicy, simgear::NoCachePolicy, simgear::NoOptimizePolicy, simgear::NoSubstitutePolicy, simgear::BuildLeafBVHPolicy>::loadUsingReaderWriter(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osgDB::Options const*)+0x90
  bin/fgfs : simgear::ModelRegistryCallback<simgear::DefaultProcessPolicy, simgear::NoCachePolicy, simgear::NoOptimizePolicy, simgear::NoSubstitutePolicy, simgear::BuildLeafBVHPolicy>::readNode(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osgDB::Options const*)+0x186
  bin/fgfs : simgear::ModelRegistry::readNode(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osgDB::Options const*)+0x139
  /usr/lib/x86_64-linux-gnu/libosgDB.so.100 : osgDB::readRefNodeFile(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osgDB::Options const*)+0x1d1
  bin/fgfs : ()+0x1eaa59e
  bin/fgfs : simgear::SGModelLib::loadModel(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, SGPropertyNode*, simgear::SGModelData*, bool)+0x193
  bin/fgfs : ()+0x156734d
  bin/fgfs : FGAircraftModel::init()+0x483
  bin/fgfs : SGSubsystem::incrementalInit()+0x23
  bin/fgfs : SGSubsystemGroup::incrementalInit()+0x148
  bin/fgfs : SGSubsystemMgr::incrementalInit()+0x52
  bin/fgfs : ()+0x1a587df
  bin/fgfs : fgOSMainLoop()+0xce
  bin/fgfs : fgMainInit(int, char**)+0x9d1
  bin/fgfs : main()+0x20b
  /lib/x86_64-linux-gnu/libc.so.6 : __libc_start_main()+0xe7
  bin/fgfs : _start()+0x2a
lucrus
 
Posts: 1
Joined: Mon Nov 12, 2018 5:54 pm

Re: 2018.3 Release

Postby GhostRider » Mon Nov 19, 2018 10:29 pm

Has FlightGear gone dark?
GhostRider
 
Posts: 117
Joined: Mon Jul 08, 2013 8:11 pm
Location: KDFW
Version: 2017.2.1
OS: Windows

Re: 2018.3 Release

Postby FlugHund » Tue Nov 20, 2018 7:06 am

lucrus wrote in Mon Nov 12, 2018 6:06 pm:
Code: Select all
Settings migrated: Saved settings were migrated from a previous version of FlightGear. If you encounter any problems when using the system, try restoring the default settings, before reporting a problem. Saved settings can affect the appearance, performance and features of the simulator.


Have you tried that? (remove ~/.fgfs/autosave*)
Plus try strarting it with the Ufo (--ufo)
User avatar
FlugHund
 
Posts: 497
Joined: Thu Mar 01, 2007 3:27 pm
Callsign: D-HUND
IRC name: D-HUND / debdog
Version: next
OS: Devuan

Re: 2018.3 Release

Postby GhostRider » Tue Nov 20, 2018 3:30 pm

What I meant to say has FlightGear run into a lot of problems with the new release? I downloaded the FG 2018.3 .exe file. When I launched the program all I got was a blank window? Just wondering.
GhostRider
 
Posts: 117
Joined: Mon Jul 08, 2013 8:11 pm
Location: KDFW
Version: 2017.2.1
OS: Windows

Re: 2018.3 Release

Postby FlugHund » Tue Nov 20, 2018 3:47 pm

User avatar
FlugHund
 
Posts: 497
Joined: Thu Mar 01, 2007 3:27 pm
Callsign: D-HUND
IRC name: D-HUND / debdog
Version: next
OS: Devuan

Re: 2018.3 Release

Postby GhostRider » Tue Nov 20, 2018 10:34 pm

Thanks.
I guess we are running into infringement rights or something like that. You notice the "server" is "off limits".
GhostRider
 
Posts: 117
Joined: Mon Jul 08, 2013 8:11 pm
Location: KDFW
Version: 2017.2.1
OS: Windows

Re: 2018.3 Release

Postby legoboyvdlp » Wed Nov 21, 2018 12:22 am

What do you mean? I don't notice any servers down :?
User avatar
legoboyvdlp
 
Posts: 5826
Joined: Sat Jul 26, 2014 1:28 am
Callsign: YV-LEGO
Version: 2018.3.1
OS: Windows 10 HP

Re: 2018.3 Release

Postby jtprophet » Wed Nov 21, 2018 2:11 pm

Good morning folks,

I can validate GhostRider's claims with the blank canvas; I just downloaded the latest RC and after setup I am seeing the same thing trying to launch with the launcher switch in the shortcut.

John.
jtprophet
 
Posts: 100
Joined: Mon Apr 04, 2016 2:21 pm

Re: 2018.3 Release

Postby PINTO » Wed Nov 21, 2018 7:48 pm

I am using 2018.3.1rc with FFGo and it is working fine (Win10) - I wonder if there is a problem with the QT launcher.
Actively developing the MiG-21bis (link to repo) (link to thread)

http://opredflag.com is an active flightgear dogfighting community (using a system that isn’t bombable)
User avatar
PINTO
 
Posts: 923
Joined: Wed Oct 21, 2015 6:28 pm
Callsign: pinto
Version: 2016.3.0
OS: Win10

Re: 2018.3 Release

Postby legoboyvdlp » Wed Nov 21, 2018 7:57 pm

Yes, it is a problem with the launcher.
FlightGear itself runs fine.
User avatar
legoboyvdlp
 
Posts: 5826
Joined: Sat Jul 26, 2014 1:28 am
Callsign: YV-LEGO
Version: 2018.3.1
OS: Windows 10 HP

Re: 2018.3 Release

Postby Captain97 » Mon Nov 26, 2018 1:20 am

Okay, so I am running the Mac release of 2018.3, with MacOS version 10.14 (also known as MacOS Mojave). In recent days, the game has started to become laggy, and slow. It has even crashed a few times. However, when I delete the 2018.3, and download 2018.2.2 it works fine. No lagging, glitching, or crashing.
Captain97
 
Posts: 32
Joined: Sun Nov 05, 2017 10:33 pm

Re: 2018.3 Release

Postby pavlin » Mon Nov 26, 2018 11:23 pm

I clear my cache so it can run smoothly.
PavlinS has back. Every Friday and Saturday watch me live at my YouTube at this link:
https://www.youtube.com/c/PavlinStanchev/live
During Christmas and New Years holidays expect me live on 22,23,24,25,26 and 30,31 December and at 01.01. 2019!
User avatar
pavlin
 
Posts: 41
Joined: Tue Sep 25, 2018 3:34 pm
Location: Sofia, Bulgaria [LBSF]
Callsign: PavlinS
Version: 2018 3.1
OS: Windows 10 Pro

Re: 2018.3 Release

Postby AAL545 » Tue Nov 27, 2018 5:00 am

I clear my cache so it can run smoothly.



Hi Pavlins,

Cache on FG or your browser?
Not sure if you can clear the cache on FG!


AAL4955
AAL545
 
Posts: 84
Joined: Tue Aug 08, 2017 4:14 am

PreviousNext

Return to Scenery

Who is online

Users browsing this forum: No registered users and 4 guests