Since I don't have to any cloud location, I'll paste the log in stages if I can.Ĭode: Select all general:3:/home/kwanza/rpmbuild/BUILD/flightgear-2018.2.2/src/Main/main.cxx:493:FlightGear: Version 2018.2.2 I forgot to mention that I am running openSUSE Linux 15.0 and I use the commands fgfs or fgfs -launcher. Should I delete all the scenery data and reinstall the SD version? Is there a way to use just the airport scenery (runways and buildings) without the general landscape which could be simply be rendered as some bland tile just like the oceans are? Or perhaps, should FG limit the number of loops it takes when searching tiles? SGMaterialCache::~SGMaterialCache() size=291įGScenery::scenery_available: waiting on tile managerįor the "high definition" aircraft, I get:Īdding subsystem to group with name 'xxx', but name() returns ''įailed to open file at /usr/share/flightgear/Nasal/canvas/wxr_api.xml Schedule_scenery: Scheduling tile at bucket:-158:0, 21:2 return false For the scenery, I get the following messages: There seems to a problem of the simulator entering into some endless loops either triggered by the scenery or YASim. For the default Cessna, it gets past "Loading scenery" and then freezes solid before the aircraft interior appears (I launched it via command line - not the launcher)Īgain it is always a read/write problem. For the 757 it gets further and freezes at "Finalizing subsystems" For the 777 it will freeze at "Initializing subsystems" Now I cannot even get past the splash screen with freezes at different points, e.g: However, my diagnosis was probably incomplete since the problems persist and perhaps got worse. Any hints please? kwanza Posts: 75 Joined: Tue 8:07 am I suspect I need to patch on the source code to simply nullify terrasync. So I need something to stop it from the read/write loop or messing with my scenery files. My guess is that it tries to sync the scenery whenever I launch it. Clearly, FG does not respect the "-disable-terrasync" flag. I don't want it to update the scenery automatically. I originally used the version 1.0 scenery, but FG keeps replacing it with the the HD version irrespective of whether I use the "-disable-terrasync" option either via command line or through the launcher. So I suspected that the scenery was the issue. I normally launch FG will the "cpulimit" utility so that it is automatically killed if it uses up to much CPU. ![]() I have noticed that the computer is in a interminable loop writing/reading something from the disk when this happens. However, it might freeze again at some later random point. This freezes are random and I can sometimes get past that point and actually fly something. My problem now is that on starting FG, it will sometimes freeze at the point of "Loading Scenery". Prior to the 2018 series, I never had a problem with running FlightGear on this hardware. I compiled FlightGear from source on openSUSE 15.0 Linux running on old Intel Core2 and Nvidia GeForce GTX 550 Ti. Firstly, I'll describe the problem I'm having.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |