20,741
edits
CompositeViewer support: Difference between revisions
Jump to navigation
Jump to search
m
→Open Questions
m (→Status) |
m (→Open Questions) |
||
| Line 110: | Line 110: | ||
What we need is a bit more analysis of what it might impact, in terms of multi-camera support, performance across different platforms and so on. Especially, knowing how it will impact switching to VSG in the future, if VSG isn’t going to have an equivalent, then we should be be quite reluctant to start using it.<ref>https://sourceforge.net/p/flightgear/mailman/message/37075174/</ref> | What we need is a bit more analysis of what it might impact, in terms of multi-camera support, performance across different platforms and so on. Especially, knowing how it will impact switching to VSG in the future, if VSG isn’t going to have an equivalent, then we should be be quite reluctant to start using it.<ref>https://sourceforge.net/p/flightgear/mailman/message/37075174/</ref> | ||
About this specific feature, there’s one concern: from memory (which may be incorrect), the CompositeViewer changes the OSG multi-threading model significantly, because there are multiple contexts. And since most of our long-standing crashing bugs are around OSG multi-threading, usually in combination with some other feature (eg, particles, or reset), James is not in agreement about the ‘risk free’ nature, if it touches threading at all. But, hopes, if it’s off by default, we can find out. | |||
James added, he would also be happier if we could get Fernando to do a code review, to make sure we’re not touching anything which might affect the CompositOR<ref>https://sourceforge.net/p/flightgear/mailman/message/37077081/</ref>. | |||
* [https://github.com/vsg-dev/VulkanSceneGraph/blob/master/ROADMAP.md VSG Roadmap] | * [https://github.com/vsg-dev/VulkanSceneGraph/blob/master/ROADMAP.md VSG Roadmap] | ||