20,741
edits
FlightGear run levels: Difference between revisions
Jump to navigation
Jump to search
→Problem
| Line 16: | Line 16: | ||
Also, this work should align well with other currently ongoing plans, such as for example decoupling the viewer from the rest of the simulation loop: | Also, this work should align well with other currently ongoing plans, such as for example decoupling the viewer from the rest of the simulation loop: | ||
{{cquote|I have now checked in a small tool in flightgear that can be used just like osgviewer. The huge difference is that it also works for btg and with some knowledge about the internals of the model loading process also for stg files. | |||
The tool is aimed at people working on scenery and willing to see how their scenery modifications will look like. The can do so now without starting flightgear. | |||
This is a basic version of that tool that might grow it there is a need. I hope to include more flightgear internal scenery loading stuff so that you can at some time also load aircraft models an see if the static parts animations/transforms/postprocessing steps are as expected without the need to start the whole simulation.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg22293.html |title=fgviewer|author=Mathias Fröhlich |date=Fri, 22 May 2009}}</ref>}} | |||
{{cquote|I understand the idea behind the 'fgviewer' tool as creating a distinct viewer component (yet still in the early stage of development) which, while still remaining compilant with the FlightGear environment, is trying to adopt as little dependencies from FlightGear as possible and therefore does not necessarily has to follow every rule of "how things are done in fgfs" in order to achieve its fine goal. | {{cquote|I understand the idea behind the 'fgviewer' tool as creating a distinct viewer component (yet still in the early stage of development) which, while still remaining compilant with the FlightGear environment, is trying to adopt as little dependencies from FlightGear as possible and therefore does not necessarily has to follow every rule of "how things are done in fgfs" in order to achieve its fine goal. | ||
| Line 22: | Line 26: | ||
{{cquote|I also think it's a good idea to factor out the dependencies that the visual part of flightgear has on the whole flightgear implementation. It's not right at the head of my queue, but I support the idea and will look for ways to move it along.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23067.html |title=[Flightgear-devel] fgviewer|author=Tim Moore |date=11 Aug 2009}}</ref>}} | {{cquote|I also think it's a good idea to factor out the dependencies that the visual part of flightgear has on the whole flightgear implementation. It's not right at the head of my queue, but I support the idea and will look for ways to move it along.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23067.html |title=[Flightgear-devel] fgviewer|author=Tim Moore |date=11 Aug 2009}}</ref>}} | ||
{{cquote|I can see several components in this area: The viewer. That was the original reason I started fgviewer. I want to have a | |||
pure viewer application that does not do any simulation.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg32973.html |title=FlightGear Manager...|author=Mathias Fröhlich |date=Sat, 25 Jun 2011}}</ref>}} | |||
{{cquote|Currently I for myself am more working on pulling out different components from the simulation. As a side effect I am doing that work on fgviewer which should do a standalone viewer component. I cannot recommend to use fgviewer for anything today because plenty of stuff is missing. But that was the place that I thought would be a good start to implement this kind of doing | {{cquote|Currently I for myself am more working on pulling out different components from the simulation. As a side effect I am doing that work on fgviewer which should do a standalone viewer component. I cannot recommend to use fgviewer for anything today because plenty of stuff is missing. But that was the place that I thought would be a good start to implement this kind of doing | ||