20,741
edits
CompositeViewer support: Difference between revisions
Jump to navigation
Jump to search
m
→Status
m (→Status) |
m (→Status) |
||
| Line 80: | Line 80: | ||
Also, a number of senior contributors have previously pointed out how our existing tile manager/paging infrastructure may not yet be in shape for a CompositeViewer port, poweroftwo's osgEarth port however is using OSG's PagedLOD exclusively, and osgEarth itself is known to support CompositeViewer<ref>https://github.com/gwaldron/osgearth/issues/1300#issuecomment-565734550</ref>, too: https://gitlab.com/poweroftwo | Also, a number of senior contributors have previously pointed out how our existing tile manager/paging infrastructure may not yet be in shape for a CompositeViewer port, poweroftwo's osgEarth port however is using OSG's PagedLOD exclusively, and osgEarth itself is known to support CompositeViewer<ref>https://github.com/gwaldron/osgearth/issues/1300#issuecomment-565734550</ref>, too: https://gitlab.com/poweroftwo | ||
So, to troubleshoot this further, it'd make sense to exclude the usual suspects one by one: | |||
* disable multi-threading | |||
* disable scenery/terrain | |||
* use [[Draw masks]] | |||
* disable effects | |||
At that point, we should be able to nail down where the culprit is, i.e. what needs changing. | |||
Jules shared the patches so that people more familiar with OSG can hopefully make some progress here.<ref>https://sourceforge.net/p/flightgear/mailman/message/37058676/</ref> | Jules shared the patches so that people more familiar with OSG can hopefully make some progress here.<ref>https://sourceforge.net/p/flightgear/mailman/message/37058676/</ref> | ||