20,741
edits
Talk:Hackathon Proposal: CompositeViewer and Canvas: Difference between revisions
Jump to navigation
Jump to search
m
Talk:Hackathon Proposal: CompositeViewer and Canvas (view source)
Revision as of 23:36, 16 November 2020
, 16 November 2020→SceneGraph Cameras vs. Prerender Cams
m (→SceneGraph Cameras vs. Prerender Cams: add links for PRE_RENDER cams for future reference) |
|||
| Line 25: | Line 25: | ||
::::: I honestly have no idea yet. The FSWeekend experience was definitely helpful but we didn't get to try out every combination and every possible limitation of every element involved. I guess we will have to see. | ::::: I honestly have no idea yet. The FSWeekend experience was definitely helpful but we didn't get to try out every combination and every possible limitation of every element involved. I guess we will have to see. | ||
::::: --[[User:Icecode|Icecode]] ([[User talk:Icecode|talk]]) 18:01, 16 November 2020 (EST) | ::::: --[[User:Icecode|Icecode]] ([[User talk:Icecode|talk]]) 18:01, 16 November 2020 (EST) | ||
:: Right, may I then suggest that some time next year, we'll actually explore the idea you outlined at [http://wiki.flightgear.org/Canvas_View_Camera_Element#Create_a_Canvas_Element_subclass_Pending], i.e. providing an "aggregation of a Compositor instance, a View and a pointer to a osg::Group" that could then be instantiated elsewhere ? This could then be used by the CanvasView module (or like you said by code unrelated to the canvas), we could begin adding stubs for property-controlled node masks, LOD and a framerate cap and use this setup to easily tinker with different use-cases and investigate what's possible/missing, as well as the resulting performance impact. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 18:36, 16 November 2020 (EST) | |||
== aircraft-less prototyping == | == aircraft-less prototyping == | ||