Project information

Discussion thread: http://www.ogre3d.org/forums/viewtopic.php?f=13&t=77133(external link)
Mercurial repository: https://bitbucket.org/sasu_robert/ogre3d-directx11(external link)

List of tasks

This is the first list. As I will arrive to the main features, which has estimated time in days I will split them in more tasks which will consist a work of maximum a day.

IDTitleState(declared, active, done, canceled)Estimated timeActual working timeDependencies
1Correcting the remaining samples active 5 days 14 days -
2 Improving core features for DirectX 11 Render System DONE 4 weeks 4 weeks -
2.1 Immutable state objects DONE 3 days 1 day -
2.2 Read back depth/stencil buffer as texture DONE 3 days 6 days -
2.3 Support new texture codecs BC7/BC6 DONE 3 days 1 day -
2.4 Multithreaded rendering inactive/discontinued 5 days - -
2.5 Texture unit support for tessellation stages - displacement mapping support DONE 7 days 7 days -
3 Terrain tessellation active 7 days 14 days hours 2.5 Displacement mapping support
4 Water tessellation and Island sample active 7 days 7 days 2.5 Displacement mapping support
5 Implementing NVidia's hair sample active 7 days 6 days -
6 Improve Ogre3D on winRT postponed 7 days - -

 

The list of the samples which have visual bugs or which are crashing (I will add this list also to the wiki page):

ID Sample Problem State
1. BSP - DirectX 11 Render System needs at least Shader Model 4.0. open
2. Bump Mapping vertex pixel shader linkage error resolved
3. Compositor - ASCII (there is just a black screen), HDR, Motion Blur(there are problems with the shaders, there are not compatible with D3D11) open
4. Deferred shading - cannot bind render target view. The system is waiting for it, but it is never bound. open
5. Dual quaternion - there is no technique supported by D3D11 - it needs new shaders. open
6. Endless world + Terrain there is a format problem when creating terrain float32 vs R16G16_SINT (this is not recognized by D3D11) ID3D11Device::CreateInputLayout resolved
7. Facial animation - multiple visual bugs when animating - still investigating why open
8. New Instancing Some of the shaders are corrected, there are still some minor issues open
9. SSAO techniques - same problem as deferred shading sample. open
10. RT Shader System - error when trying instanced viewports open
11. Shadows - there is no fixed function pipeline on D3D11, need to rewrite shadows creation for the new render systems. open
12. Volume CSG some visual bugs - some material problems resolved
13. Volume Terrain invalid arguments to ID3D11Device::CreateTexture3D. resolved

Motivation

Tessellation feature is not really used in Ogre3D. There are just 2 simple tessellation samples in Ogre Samples (pushed by myself). This feature can do a lot more, like detailed geometry for terrain and water, adaptive tessellation for models. There is also the compute shader which can used to realistic physical simulations.
I think before braking up the compatibility of Ogre3D we have to release a proper Ogre3D version (1.9) which needs only these things: finishing render systems (D3D11 and OpenGL3+) and adding tessellation, compute shaders samples. In this way there will be a proper Ogre3D version released, and developers who are using Ogre will be able to change their code and use all the new features. After that, we can break up the compatibility and work on Ogre2.0, as it seems a work of around 1 year for me.

Project Proposal

 
There are lot of features from DirectX 11 which are not implemented, there are no samples created for them. Also there is a tendency of making better browser apps, so this is why an emscripten port would be beneficial.

There is one more major feature not implemented yet to DirectX 11 Render System: Multi-Device support.
The major plan of this project would be to finish correcting the samples for the DirectX 11 Render System, correct the samples (I will need some help, advices, answers) until the proper GSoC starts (May 27th), or in the worst case I will need 2 more weeks after the this date. Then I would work on core features of DirectX 11 Render System (immutable states object, read back depth/stencil buffer as texture,support new texture codecs BC7/BC6,multithreading, texture unit support for tessellation stages).As for samples I would go for the Island and Terrain sample from NVidia samples ( it uses tessellation stage to render detailed geometry for both terrain and water), PN-Patches (PN-Triangles and PN-Quads) tessellation - which is almost finished and the Hair sample (tessellation and compute shaders, this sample simulates and renders physically realistic hair in real-time). I will look for more samples, techniques on the NVidia GPU Gem book series.
I think 3 weeks for every sample would be enough. While working on the samples I will discuss with the community how to improve Ogre3D on winRT. So on the last part of the GSoC I would work exclusively on winRT operating system to improve the workflow of Ogre3D.

So here is the list:
1. Correcting the remaining samples.
2. Improving core features for DirectX 11 Render System: immutable states object, read back depth/stencil buffer as texture,support new texture codecs BC7/BC6, multithreading, texture unit support for tessellation stages (hull, domain shaders) - displacement mapping support 0 1
Detailed information about these features are on a later post.
3. More complex PN-Patches tessellation (PN-Triangles and PN-Quads) - this could be finished before GSoC starts. 2
4. Island and Terrain sample from NVidia samples (tessellation to render detailed geometry, terrain and water) 3 4
5. Hair sample - using tessellation to render physically realistic hair in real-time 5
6. Improving Ogre3D on winRT.

Schedule

First period - from now to 17 June:
Actively interact with my mentor and Ogre3D community to discuss final details. Correct those samples which are not working now on the DirectX 11 Render System and finish the current PN-Patches tessellation sample. Also add texture unit support for tessellation stages (hull and domain shaders) and work on displacement support/sample. After 7 June I will be able to work intensively, because it is the last day of the exam session for this year.

Official coding time start - 17 June to 2 Aug
If it is needed I will alloc one more week for correcting correcting the Ogre samples - not easy bugs.

1. Improve core features - 4 week : (7 June - 20 July) - immutable states object, read back depth/stencil buffer as texture,support new texture codecs BC7/BC6, multithreading, texture unit support for tessellation stages. I will allocate around 1 week for each core improvement, one day for adding support for new texture codecs (BC6/BC7)
2. Terrain and Island sample from NVidia - 14 days: (14 July - 2 Aug) - implementing this sample which uses tessellation stage to render complex geometry for water and terrain. Terrain sample uses tessellation stages to generate terrain.

Midterm deadline 2 Aug
At this moment all the Ogre3D samples will work on the DirectX 11 Render System. There will be also some performance gain because of the new features and will support new texture codecs. PN-Patches algorithm will be finalized. The Island sample will be also implemented and ready to test and try. There will be also a working sample of terrain tessellation.

Second coding part 2 Aug - 16 Sept

1. Hair sample - 3 weeks: (2 Aug - 21 Aug) - implementing this sample which uses compute shaders and tessellation stages for rendering physically realistic hair.
2. Ogre3D and winRT - 21 Aug - 16 Sept - I will work exclusively on winRT operating system to improve Ogre3D and gain as much performance as possible.

 
Suggested firm pencil's down (16 Sept)
Ogre3D will benefit of new samples, using the newest technologies - tessellation stages and compute shaders. Moreover the DirectX 11 Render System will be updated and will have more new features, supporting multi-threading and new texture codecs, it will also have a better performance because of multi-threading, the use of immutable state object and by using the possibility to use depth/stencil buffer as textures. It will also have a displacement sample and texture unit support for tessellation stages. Finally, Ogre3D will work better on the winRT operating system, will have a much better performance.

After GSoC
After Google Summer of Code ends I want to help developing the future releases: Ogre2.0, Ogre2.1 and so on. Also I will add multi-device support for DirectX 11 Render System after finishing all the above listed features.

Why You're The Person For This Project

The community probably knows me from the last years Google Summer of Code. But here is my personal description.

My name is Robert Sasu and I study Computer Science at Polytechnic University of Bucharest, Romania. I had participated to GSoC 2011 at GIMP organization on the project Porting Gimp plug-ins to GEGL. Here is a link to my showcase and code: http://sasurobert.github.com/GSoC-2011/(external link)
I have participated to GSoC 2012 at Ogre3D on the project Complete DirectX 11 Render System, the project become to big to be able to finish it in 3 months time (I've committed a changeset of more then 20k lines of code.) After Google Summer of Code 2012 I have actively worked on my repo and resolved DirectX 11 Render System related bugs, also helped community members if they had questions. I have also submitted ideas to SkyX Ogre3D related project. Moreover I worked and I am working as a part-time student on a AeroPlane simulator (urlartmacs.com/url) where I am using Ogre3D 1.7 as graphic engine, using DirectX 9 Render System.
I do have my repository of Ogre3D and have some followers. I am continuously pushing code there, correcting bugs.

I would like to participate to GSoC 2013 and I found the project described above interesting. I have strong background in C/C++,C#, Java, Haskel, CLIPS programming, shader language (cg, hlsl) and algorithms. I really like mathematics:I recently participated to SEEMOUS (seemous.eu) and I earned a silver medal. First year of the faculty I attended a Microsoft course where we learnt how create games, terrains (rendering stuff) using C# with XNA 4.0. It was really fascinating how many things are implemented in this library and how efficient is it working, using the video card to the maximum. Through this course I've also done some basic DirectX 9 and 10 coding, some basic rendering.

Why OGRE?

OGRE is a great 3D graphics library. The main use case for this project is of course completing the DirectX 11 rendering system, which will be really useful for Windows 8 and all the new videocards which are capable of using DirectX 11.

Anything else

Ogre appears to have a very friendly and helpful community. I've already got a lot, learnt a lot by reading all the answers regarding my proposal, and reading all the proposed documentation for me. It is really nice of how fast is the community answering the questions. It would be a great opportunity for me to take part of this community and to work on Ogre3Ds core.

Detailed description of core work:

Multi-threaded rendering - multithreading for DirectX 11

First, improvements in synchronization between the Direct3D device object and the driver enable asynchronous API calls, including resource allocations. Direct3D 11 allows developers more freedom when expressing parallelism by allowing such calls to occur across multiple threads.
Second, the Direct3D device interface now supports multiple rendering contexts. 1) a primary immediate context which dictates the timeline for work submission to the GPU, and 2) optional deferred contexts created by the application developer as needed. Work associated with each deferred context can occur on a separate thread/core. This enables GPU commands to be accumulated in parallel to the main rendering work, and then sent to the GPU later when the main context is ready to submit a new task to the GPU.
Image

Texture Unit support for tessellation stages - hull and domain shaders - and displacement mapping support

http://www.nvidia.com/object/tessellation.html(external link)

Using immutable states object : - can be precomputed and cached,

- subset of command buffer at creation time
The list of immutable state objects used by DirectX 11: Input Layout Object, Rasterizer Object, DepthStencil Object, Blend Object, Sampler Object
http://legalizeadulthood.wordpress.com/2009/07/12/description-helpers-for-direct3d-10-10-1-and-11/(external link)

Read back depth/stencil buffer as texture: Disables writes to the part that is read-only, allows for using texture as input and for depth-culling

Enables features without requiring a separate depth render
• Atmosphere pass
• Soft particles
• DOF
• Forward shadow mapping
• Screen-space ambient occlusion
http://msdn.microsoft.com/en-us/library/windows/desktop/bb205074(v=vs.85).aspx#reading_the_depth-stencil_buffer_as_a_texture(external link)

Support new texture codecs BC7/BC6

BC6H supports high-dynamic range color source data, and BC7 provides better-than-average quality compression with less artifacts for standard RGB source data.
More complex block palette interpolations, smaller amount of artifacts, high dynamic range support.
http://www.nvidia.com/content/nvision2008/tech_presentations/Game_Developer_Track/NVISION08-Direct3D_11_Overview.pdf(external link)

Weekly progress nr.1

  • Create repository by forking the official one, and create this wiki page.
  • Create a list of tasks with columns ID, Title, State (declared, active, done, canceled), Time(estimated, actual work), Dependencies

Contributors to this page: robert_sasu270 points  and spacegaier6073 points  .
Page last modified on Sunday 22 of September, 2013 14:57:56 UTC by robert_sasu270 points .


The content on this page is licensed under the terms of the Creative Commons Attribution-ShareAlike License.
As an exception, any source code contributed within the content is released into the Public Domain.