CompositeViewer support: Difference between revisions

Jump to navigation Jump to search
m
m (→‎Status: add background about disappearing scenery tiles)
Line 78: Line 78:


For now, it seems we 'Cant Use' CompositeViewer because of $reasons in the Effects code<ref>https://sourceforge.net/p/flightgear/mailman/message/26189393/</ref>. Maybe the reason is simply that it needs some work to move away from the single CameraGroup, however.<ref>https://sourceforge.net/p/flightgear/mailman/message/37059939/</ref>
For now, it seems we 'Cant Use' CompositeViewer because of $reasons in the Effects code<ref>https://sourceforge.net/p/flightgear/mailman/message/26189393/</ref>. Maybe the reason is simply that it needs some work to move away from the single CameraGroup, however.<ref>https://sourceforge.net/p/flightgear/mailman/message/37059939/</ref>
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 


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>

Navigation menu