20,741
edits
Howto:Reset/re-init Troubleshooting: Difference between revisions
Jump to navigation
Jump to search
Howto:Reset/re-init Troubleshooting (view source)
Revision as of 16:08, 23 February 2016
, 23 February 2016→Motivation
| Line 62: | Line 62: | ||
| added = Jan 23rd, 2016 | | added = Jan 23rd, 2016 | ||
| script_version = 0.23 | | script_version = 0.23 | ||
}} | |||
}} | |||
{{FGCquote | |||
|1= Instead of adding just-another-feature we need to strip it down to getting a fast and constand fps rendering engine. Everything else needs to run outside the main loop and has to interact with the core by, say HLA/RTI or whatever IPC we have. | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/34793778/ | |||
| title = <nowiki>Re: [Flightgear-devel] A FGPythonSys implementation: The embedded | |||
Python interpreter as a FlightGear subsystem.</nowiki> | |||
| author = <nowiki>Torsten Dreyer</nowiki> | |||
| date = Jan 25th, 2016 | |||
| added = Jan 25th, 2016 | |||
| script_version = 0.25 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= I'd just recommend to not do it but to focus on detangling the subsystems and creating a distributes simulation instead. That's my vision. | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/34793948/ | |||
| title = <nowiki>Re: [Flightgear-devel] A FGPythonSys implementation: The embedded | |||
Python interpreter as a FlightGear subsystem.</nowiki> | |||
| author = <nowiki>Torsten Dreyer</nowiki> | |||
| date = Jan 25th, 2016 | |||
| added = Jan 25th, 2016 | |||
| script_version = 0.25 | |||
}} | }} | ||
}} | }} | ||