OpenSceneGraph: Difference between revisions

Jump to navigation Jump to search
3,361 bytes removed ,  9 July 2024
Remove obviously obsolete texts
(→‎Downloading OpenSceneGraph: Out of date, regering to very old OSG versions)
Tags: Mobile edit Mobile web edit Advanced mobile edit
(Remove obviously obsolete texts)
Line 1: Line 1:
{{Out of date}}
[[File:Flightgear uml associations class diagram.png|thumb|270px|An [[UML Diagrams|UML]] class diagram disclosing the associations between some classes of the FlightGear source code.]]
[[File:Flightgear uml associations class diagram.png|thumb|270px|An [[UML Diagrams|UML]] class diagram disclosing the associations between some classes of the FlightGear source code.]]


= Downloading OpenSceneGraph =
Historically [[FlightGear]] has used [[PLIB]] instead of '''OpenSceneGraph'''. [[FlightGear 1.9.0]], released December 22, 2008, marked the release of the OSG version of FlightGear. While much of the conversion to OSG has happened over the years, [[PLIB]] is still used for some functions.


{{Out of date}}
== Downloading OpenSceneGraph ==


{{Note|as of 12/2017, people may have to build using at least OSG 3.4 due to some compilation issues -for details, refer to [[Howto:Building FlightGear without HiDPI support]]}}
{{Note|as of 12/2017, people may have to build using at least OSG 3.4 due to some compilation issues -for details, refer to [[Howto:Building FlightGear without HiDPI support]]}}
Line 11: Line 13:
You should use the unstable development releases (or build OSG from git) only if you intend to develop FlightGear against new features under development in OpenSceneGraph. For all other cases the latest stable release of OpenSceneGraph is usually the best option.
You should use the unstable development releases (or build OSG from git) only if you intend to develop FlightGear against new features under development in OpenSceneGraph. For all other cases the latest stable release of OpenSceneGraph is usually the best option.


== Downloading Stable OpenSceneGraph ==
=== Downloading Stable OpenSceneGraph ===
The OpenSceneGraph project uses [http://svnbook.red-bean.com/nightly/en/index.html Subversion (SVN)] to distribute their sources.
The OpenSceneGraph project uses [http://svnbook.red-bean.com/nightly/en/index.html Subversion (SVN)] to distribute their sources.


Line 28: Line 30:
  http://www.freebsd.org/cgi/pds.cgi?ports/graphics/osg
  http://www.freebsd.org/cgi/pds.cgi?ports/graphics/osg


== OpenSceneGraph developer versions ==
=== OpenSceneGraph developer versions ===
FlightGear developers may want to use a '''development release''' of OpenSceneGraph:
FlightGear developers may want to use a '''development release''' of OpenSceneGraph:


Line 41: Line 43:
     svn checkout http://svn.openscenegraph.org/osg/OpenSceneGraph/trunk OpenSceneGraph
     svn checkout http://svn.openscenegraph.org/osg/OpenSceneGraph/trunk OpenSceneGraph


= Compiling OpenSceneGraph =
== Compiling OpenSceneGraph ==


OpenSceneGraph uses cmake. Since OSG version 2.7.3 (8th Oct 2008) a relatively new version of cmake is required. According to OSGs CMakeLists.txt it's 2.6.1 but cmake 2.6.0-5 from [http://backports.org/dokuwiki/doku.php backports.org] for Debian/Etch does the trick.
OpenSceneGraph uses cmake. Since OSG version 2.7.3 (8th Oct 2008) a relatively new version of cmake is required. According to OSGs CMakeLists.txt it's 2.6.1 but cmake 2.6.0-5 from [http://backports.org/dokuwiki/doku.php backports.org] for Debian/Etch does the trick.
Line 64: Line 66:
* You don't need to build the examples, wrappers or applications.
* You don't need to build the examples, wrappers or applications.


== Installing OpenSceneGraph and FlightGear with --prefix ==
=== Installing OpenSceneGraph and FlightGear with --prefix ===


If you use --prefix to choose were to install FlightGear and do not want to install OSG globally on the system this can be done with the following method:
If you use --prefix to choose were to install FlightGear and do not want to install OSG globally on the system this can be done with the following method:
Line 93: Line 95:
Installing with --prefix is a very nice way to keep several distinct and independent versions of FlightGear around. To start a new $PREFIX directory you'll also need to install plib in it, but that is easy. Most other needed dependencies are usually available through the package system of most Linux distributions (e.g. FreeGLUT, SDL, ALSA, etc).
Installing with --prefix is a very nice way to keep several distinct and independent versions of FlightGear around. To start a new $PREFIX directory you'll also need to install plib in it, but that is easy. Most other needed dependencies are usually available through the package system of most Linux distributions (e.g. FreeGLUT, SDL, ALSA, etc).


== lib64 ==
=== lib64 ===
Content moved to [[Talk:OpenSceneGraph]] for now.
Content moved to [[Talk:OpenSceneGraph]] for now.


= Features and issues =
== External link ==
 
Historically FlightGear has used [[PLIB]] instead of '''OpenSceneGraph'''. [[FlightGear 1.9.0]], released Decemeber 22, 2008, marked the release of the OSG version of FlightGear. While much of the conversion to OSG has happened over the years, [[PLIB]] is still used for some functions.
 
Thanks to Mathias Fröhlich and Tim Moore, we can use recent OpenSceneGraph releases.
 
== Regressions in CVS/HEAD ==
This section is meant to always remain up to date with the latest version in CVS/HEAD, please make sure to add/delete items as necessary.
* feature to disable scenery rendering via /sim/rendering/draw-otw property is not working at the moment (11/2008)
 
== Current issues (very out of date) ==
 
* <strike>The 2D Panels and the rendering order of instruments ... is wrong.</strike>
 
* transparency issues:
** <strike>runway lights shine through panel:</strike>
** runway lights shine through cloud layers in an awkward way:
** 2D-cloud layers flood into cockpit
** The prop of the C172 block the view on the waves of the carrier
** The reflector gun sight on the Seahawk causes other transparent objects (carrier wake etc.) to disappear
** A new overhead window in the C172 (inside out)
 
* <strike>Runway lighting seems to have rendering artefacts on ATI Cards.</strike>
 
* <strike>Enhanced runway lighting option in the drop-down menu seems to have no effect - light always appear enhanced.</strike>
 
* <strike>Seneca II HSI: upper instrument clipping issue for NAV/HDG flags, heading bug, pointer</strike>
 
 
[[List of 'compatible' aircraft]] TO BE CONTINUED ('''NOTE:''' the list is out of date.)
 
== Missing features ==
Due to the migration from PLIB to OSG, some of the features seen in past versions of FlightGear are now temporarily non-functional. These are:
 
 
* <strike>3D clouds</strike> 3D clouds back thanks to Stuart Buchanan still have some visual artifacts
 
* <strike>Rendering of some scenes is not perfect.</strike>
 
* Shadows
 
* Exhaust shader
 
* Weather Radar is not showing any clouds
 
* cloud layers don't follow the curve of the earth
 
* Menu Items have no effect
** Enhanced Runway Lights
** Bump Mapped Clouds
 
== Miscellaneous OSG benefits ==
* Models and scenery load in a separate thread
* Tree shaders allow "forests" of trees
* Improved precipitation modeling
* "Pick" animations enable greater realism and ease of creation for 3D cockpits
* Multi-monitor views
 
Mathias: "I think that we should make use in the longer term of the Producers
capabilities for multiple view installations.
But not only multipipe installs will benefit from that. The Producer will also
help to get benefit from multicore SMP machines.
For that the following article is of huge interest:
http://www.donburns.net/OSG/Articles/OSGMP/"
 
= Getting the PLIB Code =
 
Use the tag <tt>PRE_OSG_PLIB_20061029</tt> for checking out the branch with the plib scenegraph.
 
 
For SimGear, this works (more or less) as follows:
 
 
    '''cvs -d :pserver:cvsguest@cvs.simgear.org:/var/cvs/SimGear-0.3 login'''
    '''CVS passwd: guest'''
    '''cvs -d :pserver:cvsguest@cvs.simgear.org:/var/cvs/SimGear-0.3 co source'''
    '''cd source'''
    '''cvs up -rPRE_OSG_PLIB_20061029'''
 
 
For FlightGear, you have to update the "source" directory:
 
    '''cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 login'''
    '''CVS passwd: guest'''
    '''cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co -rPRE_OSG_PLIB_20061029 source
'''
The data directory should be the CVS HEAD version. Some aircraft, however, have a PRE_OSG_PLIB_20061029 branch that works better with FlightGear/plib, e.g Hawker Hunter.
 
= External link =
* http://www.openscenegraph.org/
* http://www.openscenegraph.org/


Navigation menu