![]() Hooray wrote:This is not at all about "backward compatibility" - what you are asking for is sort of "forward compatibility". It can however, as could be seen in Thorsten's weather package or flug's bombable addon - both being much more complex and sophisticated than your average aircraft, but both "addons" supporting a wide range of FlightGear versions (up to a point), due to conscious design efforts.īut please don't expect 2013-era aircraft like the 707 to work in FlightGear 1.9: In the end, time is a precious resource and we cannot expect people to find it more interesting to guarantee backwards compatibility, than working on new features. But obviously it takes more time and energy to do this type of work, no matter if it's maintaining different -set.xml files for various FlightGear versions, or maintaining a certain degree of backwards compatibility in the core. There's something to be learnt from such examples. Honestly, the way aircraft development is conducted, it is challenging to accommodate such needs - because, it's also not possible to maintain/update aircraft in a semi-automated/scripted fashion, due to their arbitrary internal structure, empowered by XML, the property tree and scripting.Īt the end of the day, it's really up to aircraft developers to keep things up-to-date for different versions, that it's possible can be seen in examples like the bluebird - whose author/developer seems aware of major changes between different releases, and puts a conscious effort into abstracting away differences by using different *-set.xml files for different FG versions, and including shared/common stuff from there on. Basically, we shouldn't be removing/renaming features (think APIs), but rather provide migration layers for 1-2 release cycles - obviously, it takes more time to implement such layers that translate new features into APIs understood by aircraft that haven't been updated. by maintaining a minimal degree of backwards compatibility. It's actually a good thing, because it means that core development is making progress - the real issue here is that there's no conscious effort to prevent breakage, i.e. ![]() ![]() (It's not your fault in particular though, I'm just venting some steam.) Unfortunately it seems less and less practically possible, which quite make me understand the current situation where most aircraft developers expect the users to have the latest stable version (or even sometimes the bleeding edge GIT). The reason to have them all would be to able to try understand the differences and pitfalls in trying to get aircraft flyable on all versions. I will probably keep the old TerraSync scenery (probably by renaming the directory), as I have planned to be able to have all stable versions past 2.0.0 installed at some undefined point in the future. The reason I asked is to figure out what to add to the wiki about which version that would be the oldest one capable of using the new world scenery and TerraSync scenery from now on. And yes updating to 2.12 would be optimal, provided I can run it, but I have not gotten that far yet (though I have had it downloaded for a while). You might want to have a look at it, and fix the release if the problem is in the data files. I apologize if this is not the right thread for such bug reports, but I thought it was strongly related to the World Scenery 2.0 release. Unknown font name '', defaulting to Helveticaįgfs: runways.cxx:150: void FGRunway::processThreshold(SGPropertyNode*): Assertion `ident() = aThreshold->getStringValue("rwy")' failed. ![]() When running, it crashes with the following debug output:Ĭode: Select all Processing command line arguments (note: I've enabled automatic scenery download in the directory "/home/cjp/.fgfs/scenery/" this is probably why I'm automatically receiving the 2.0 scenery files.) prop:/sim/rendering/texture-compression=off prop:/sim/menubar/autovisibility/enabled=1 I start it with the "fgrun" FlightGear wizard. I have Flightgear 2.4.0-1, as supplied with Linux Mint 13 (probably from Ubuntu 12.04 repositories). I believe this has something to do with the World Scenery 2.0 release, since I can resolve it by manually reverting the airports directories to SVN revision 22556. I'm here because of a problem though: since November 2nd, my Flightgear no longer starts. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |