20,741
edits
FGPythonSys: Difference between revisions
Jump to navigation
Jump to search
m
→FFGo launcher: http://forum.flightgear.org/viewtopic.php?f=5&t=5350&p=41424&hilit=TerraGear+Python#p41424
m (→Development) |
m (→FFGo launcher: http://forum.flightgear.org/viewtopic.php?f=5&t=5350&p=41424&hilit=TerraGear+Python#p41424) |
||
| Line 185: | Line 185: | ||
| date = Aug 4th, 2015 | | date = Aug 4th, 2015 | ||
| added = Aug 4th, 2015 | | added = Aug 4th, 2015 | ||
| script_version = 0.23 | |||
}} | |||
}} | |||
=== TerraGear GUI === | |||
It's worth pointing out, there's plenty of people who would like to work on scenery, but find the setup and import / processing / export steps very tricky - especially if they've no experience with GRASS (or QGIS). Any scripts or workflow documentation that knowledgeable people make available is a huge benefit. (I also think there's probably some easy hacks that could be made to the terra-gear tools to simplify the commands and file structure, but that's a discussion for another time) | |||
{{FGCquote | |||
|1= If I were to start writing terragear today, I would definitely start down that path in python. Obviously we can't do anything too intensive per-frame in a scripting language. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=270386#p270386 | |||
| title = <nowiki>Re: FGPython an propose for </nowiki> | |||
| author = <nowiki>curt</nowiki> | |||
| date = Dec 28th, 2015 | |||
| added = Dec 28th, 2015 | |||
| script_version = 0.23 | | script_version = 0.23 | ||
}} | }} | ||