|
|
Line 175: |
Line 175: |
|
| |
|
| So we've always got the basic scenario to fall back on where there is just a single view and things are essentially identical to a standard non-CompositeViewer setup.<ref>https://sourceforge.net/p/flightgear/mailman/message/37076818/</ref> | | So we've always got the basic scenario to fall back on where there is just a single view and things are essentially identical to a standard non-CompositeViewer setup.<ref>https://sourceforge.net/p/flightgear/mailman/message/37076818/</ref> |
|
| |
| === Potential Issues ===
| |
| So far, it seemed 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
| |
|
| |
| So, to troubleshoot this further, it'd make sense to exclude the usual suspects one by one:
| |
| * disable multi-threading (see Torsten's comments about known issues about multi-screen/multi-GPU setups at [[Howto:Activate multi core and multi GPU support]])
| |
| * 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 (topic branch, see above) so that more people can get involved in testing and making progress.<ref>https://sourceforge.net/p/flightgear/mailman/message/37058676/</ref>
| |
|
| |
|
| === OSG stuff === | | === OSG stuff === |