20,741
edits
CompositeViewer support: Difference between revisions
Jump to navigation
Jump to search
m
→Status updates
mNo edit summary |
m (→Status updates) |
||
| Line 54: | Line 54: | ||
This is primarily needed/useful when views may need acccess to scenery (tiles) that are no longer in the cache of the main aircraft, for instance a tower view of the destination airport, or payload-specific views (think missiles) that may be out of range, and thus need their own scenery DB pager. In other words, CompositeViewer (CV) support is needed whenever a view can no longer be easily defined/described as a "child view" of the main aircraft. | This is primarily needed/useful when views may need acccess to scenery (tiles) that are no longer in the cache of the main aircraft, for instance a tower view of the destination airport, or payload-specific views (think missiles) that may be out of range, and thus need their own scenery DB pager. In other words, CompositeViewer (CV) support is needed whenever a view can no longer be easily defined/described as a "child view" of the main aircraft. | ||
=== Status updates === | === Status updates === | ||
* 2021-08-27: Fernando has begun working on moving Canvas cameras out of the scene graph into dedicated PRERENDER cams (This was a long-standing issue where Canvas cameras were rendered multiple times, once per slave camera. In the case of the Classic pipeline they were being rendered twice.), see: | |||
** {{flightgear commit|83b0a3}} | |||
** {{simgear commit|a97e14}} | |||
* 2021-08-13: Flickering (and eventually crashing) of Canvas avionics/displays (textures) in conjunction with CompositeViewer use seems related to using some of the more sophisticated OSG threading modes in combination with vector graphics (based on Shiva via [[Canvas Path]] elements) that are lacking serialization, which shows up when OSG tries to render frames concurrently.<ref>https://forum.flightgear.org/viewtopic.php?f=4&t=39475&p=390829#p390828</ref>, for now please use single-threaded mode only because Shiva cannot be considered thread-safe, i.e. needs explicit serialization in conjunction with OSG threading <ref>https://forum.flightgear.org/viewtopic.php?f=71&t=39535&start=15#p390395</ref> | * 2021-08-13: Flickering (and eventually crashing) of Canvas avionics/displays (textures) in conjunction with CompositeViewer use seems related to using some of the more sophisticated OSG threading modes in combination with vector graphics (based on Shiva via [[Canvas Path]] elements) that are lacking serialization, which shows up when OSG tries to render frames concurrently.<ref>https://forum.flightgear.org/viewtopic.php?f=4&t=39475&p=390829#p390828</ref>, for now please use single-threaded mode only because Shiva cannot be considered thread-safe, i.e. needs explicit serialization in conjunction with OSG threading <ref>https://forum.flightgear.org/viewtopic.php?f=71&t=39535&start=15#p390395</ref> | ||
* 2021-08-06: Various improvements to extra views - see: {{flightgear commit|7ed93e4e64d}} | * 2021-08-06: Various improvements to extra views - see: {{flightgear commit|7ed93e4e64d}} | ||