to make the problem much more obvious/self-explanatory, without us having to spend several hours each month explaining why features like Canvas cannot work in FG 1. The idea is to have a handful of such images, and get those committed to $FG_ROOT/Textures, so that these splash screens can be used when showing the corresponding error message - i.e. The artwork for this, would need to be GPLed/public domain obviously, and should have the format of a conventional splash screen (512x512). It could ask you to register to get the app. Please, follow next instructions: Press the button and open the official source.

You will be taken to the product page on the official store (mostly it is an official website of the app). Now, I am looking for a funny-image that bring across the whole notion of 1) taking a modern feature/system and 2) trying to run it with heavily outdated stuff. To download and install Inkscape for PC, click on the 'Get Inkscape' button.

More recently (in fact, yesterday), we began prototyping an error dialog to make this much more obvious, and to terminate FG when people are trying to do this: Microsoft word 2000 trying to open recent word documents The common theme, we're using to explain this is bring up an example like an old device, trying to support modern technology -for example:

we'd need a time machine to change FlightGear 1.xx to support features used on 3.8 aircraft.įor a basic summary, see. We usually call this 'Forward compatibility' - i.e. This cannot work usually, because the aircraft contains features and code that is only supported by fairly recent FlightGear versions. Su15, F15, SpaceShuttle) with extremely outdated binaries (e.g. Ok, here's the deal: We get to see an increasing number of users on the forum who are trying to run recently released aircraft (e.g.

Inkscape for mac 10.11.6