Qt-contributors-summit-2013-Scene-Graph: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
* What has been happening for 5.1 | |||
** Render loop for windows | |||
** New threaded renderloop | |||
* What is going to happen for 5.2? | |||
** Renderer | |||
** Animations on a thread? | |||
* Scene-graph integration with other rendering; ‘master mode’ with beginNativeRendering / endNativeRendering calls to ensure SG state is restored. | |||
* ‘slave’ mode; disable the render thread, have a well defined entry point to make SG perform rendering on an existing context. All GL state setup and init needs to happen inside this entry point. (This is for integration with OpenSceneGraph, <span class="caps">OGRE</span> etc where both context creation and timing/threading of rendering are out of our control) | |||
* Real support for AA – render to multisample texture formats to avoid a RenderBuffer -> texture copy | |||
* Core profile support, especially for Mac; ES3 support; add <span class="caps">VAO</span>s, potentially other tweaks | |||
* Stand alone module? |
Revision as of 14:09, 25 February 2015
- What has been happening for 5.1
- Render loop for windows
- New threaded renderloop
- What is going to happen for 5.2?
- Renderer
- Animations on a thread?
- Scene-graph integration with other rendering; ‘master mode’ with beginNativeRendering / endNativeRendering calls to ensure SG state is restored.
- ‘slave’ mode; disable the render thread, have a well defined entry point to make SG perform rendering on an existing context. All GL state setup and init needs to happen inside this entry point. (This is for integration with OpenSceneGraph, OGRE etc where both context creation and timing/threading of rendering are out of our control)
- Real support for AA – render to multisample texture formats to avoid a RenderBuffer -> texture copy
- Core profile support, especially for Mac; ES3 support; add VAOs, potentially other tweaks
- Stand alone module?