• Advertisement
Sign in to follow this  

DX11 Beginning Radiosity

This topic is 2331 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi I'm currently a games development student about to go into my third and final year and for my project I'm writing a global illumination renderer in DirectX10 using HLSL, the past couple weeks I've been stuck deciding what to use for indirect illumination, I've read countless articles on the radiosity method as well as the different techniques (PRT, instant radiosity, radiosity normal mapping, irradiance volumes etc...). I've read every single forum post on here that mentions radiosity and also MJP's DX11 radiosity method.

I have no idea which technique would be best to use, and when i decide on one I get very confused about where to start, would anybody care to offer help and suggestions ? Cheers

My renderer needs to be able to run at interactive speeds (for games)

Share this post


Link to post
Share on other sites
Advertisement
Well the first thing you'll need to decide whether you're looking to use precomputed global illumination, or something that works in real time. Also if you want to do the latter there are techniques that work with static geometry but dynamic lighting, as well as techniques that allow for both to be fully dynamic. Deciding on this will narrow down the field considerably.

Share this post


Link to post
Share on other sites
I'm hoping to do static geometry with dynamic lights and then if I get that done maybe check out dynamic geometry. I've been leaning more towards the instant radiosity method with the VPL's.

Share this post


Link to post
Share on other sites
If you happen to go with instant radiosity with VPLs, I've got an example of that with Nvidia's ray-tracing library Optix and DirectX: http://graphicsrunner.blogspot.com/2011/03/instant-radiosity-using-optix-and.html

Share this post


Link to post
Share on other sites
Cheers, obviously this technique works well with deferred shading, but I'm not looking to build a deferred renderer so does anyone recommend a better technique to use with forward rendering ?

Share this post


Link to post
Share on other sites
You could do some research into what Geomerics does for Enlighten. As far as I know they precompute form factors for static geometry at regularly-sampled points on a mesh surface (basically light a lightmap), then at runtime they compute the lighting at those points and solve the system of equations using Gauss-Seidel (or something similar). They do that on the CPU, but it's possible to do it on the GPU as well.

Another interesting approach is appoximating surfaces as discs, which was pioneered by Michael Bunnel. There's an older GPU Gems article about it, and there's some descriptions of his updated algorithm from his SIGGRAPH talk last year. It's intended for use with dynamic geometry, but I did some experiments with precomputing visibility for static geometry and the results were promising.

There's also the paper from SIGGRAPH this year about cone-tracing through a voxelized scene. That definitely looked pretty neat, and with static geo you could pre-compute the voxelization.

Share this post


Link to post
Share on other sites
My personal favorite is the dynamic lightmap generation from Lionhead (a cancelled game called Milo) and Battlefield 3. Lionhead's used spherical harmonics and there presentation was at GDC earlier this year. "Geomerics" and DICE use a not too dissimilar approach (at least in some respects) for Battlefield 3. It gets you dynamic objects lit by "partially" dynamic geometry (you can remove or add the light bouncing geometry, but a bunch of extra stuff has to be calculated if you do).

Battlefield 3 has presentations... everywhere. Just go to DICE's site and you'll find stuff.

Share this post


Link to post
Share on other sites
[quote name='MJP' timestamp='1314040725' post='4852460']
You could do some research into what Geomerics does for Enlighten. As far as I know they precompute form factors for static geometry at regularly-sampled points on a mesh surface (basically light a lightmap), then at runtime they compute the lighting at those points and solve the system of equations using Gauss-Seidel (or something similar). They do that on the CPU, but it's possible to do it on the GPU as well.

Another interesting approach is appoximating surfaces as discs, which was pioneered by Michael Bunnel. There's an older GPU Gems article about it, and there's some descriptions of his updated algorithm from his SIGGRAPH talk last year. It's intended for use with dynamic geometry, but I did some experiments with precomputing visibility for static geometry and the results were promising.

There's also the paper from SIGGRAPH this year about cone-tracing through a voxelized scene. That definitely looked pretty neat, and with static geo you could pre-compute the voxelization.
[/quote]

I took quite a detailed look into the voxel cone tracing method, was extremely impressed and interested by it but im afraid its much too complicated for me, I dont quite understand the Geomerics approach, the only info i could find on it was their talk with Crytek and its quite brief, also I don't know what the system of equations is or Gauss-Seidel. Took a look at the Bunnel approach an understood it, couldn't find much documentation on it past the GPU Gems article though.

Would probably help if I had a really good book on GI, I have one small book but its pretty rubbish, do you know of any really good books ?

Cheers

Share this post


Link to post
Share on other sites
Well if you haven't already, you definitely want to download the [url="http://people.cs.kuleuven.be/%7Ephilip.dutre/GI/TotalCompendium.pdf"]GI total compendium[/url]. The basic idea behind using a system of equations is that for each sample point, you can compute the lighting of that point as the sum of the lighting at all other points multiplied with the form factor. Together these form a large system of equations that looks like this:

A = B * FFab + C * FFac + D * FFad ...
B = A * FFba + C * FFbc + D * FFbd ...
C = A * FFca + B * FFcb + D * FFcd ...
etc.

That forms a matrix, which you can use to solve that system of equations to get the lighting at each sample point (you probably learned about how to do that in algebra class). Gauss-Seidel is just a method for solving such a system of equations. Altogether that matrix might be very large for a complex scene, and Geomerics deals with that by breaking up the scene into different "zones" where a sample point in one zone is only assumed to be affected by a sample point from within the same zone. They can also compress the matrices because they end up being sparse (lots of zeros due to one sample point not affecting another sample point due to no visibility).

Bunnel gave a talk about his GI tech last year at siggraph, and you get the PDF here: [url="http://cgg.mff.cuni.cz/%7Ejaroslav/gicourse2010/index.htm"]http://cgg.mff.cuni.cz/~jaroslav/gicourse2010/index.htm[/url]

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Now

  • Advertisement
  • Similar Content

    • By mister345
      Hi, can somebody please tell me in clear simple steps how to debug and step through an hlsl shader file?
      I already did Debug > Start Graphics Debugging > then captured some frames from Visual Studio and
      double clicked on the frame to open it, but no idea where to go from there.
       
      I've been searching for hours and there's no information on this, not even on the Microsoft Website!
      They say "open the  Graphics Pixel History window" but there is no such window!
      Then they say, in the "Pipeline Stages choose Start Debugging"  but the Start Debugging option is nowhere to be found in the whole interface.
      Also, how do I even open the hlsl file that I want to set a break point in from inside the Graphics Debugger?
       
      All I want to do is set a break point in a specific hlsl file, step thru it, and see the data, but this is so unbelievably complicated
      and Microsoft's instructions are horrible! Somebody please, please help.
       
       
       

    • By mister345
      I finally ported Rastertek's tutorial # 42 on soft shadows and blur shading. This tutorial has a ton of really useful effects and there's no working version anywhere online.
      Unfortunately it just draws a black screen. Not sure what's causing it. I'm guessing the camera or ortho matrix transforms are wrong, light directions, or maybe texture resources not being properly initialized.  I didnt change any of the variables though, only upgraded all types and functions DirectX3DVector3 to XMFLOAT3, and used DirectXTK for texture loading. If anyone is willing to take a look at what might be causing the black screen, maybe something pops out to you, let me know, thanks.
      https://github.com/mister51213/DX11Port_SoftShadows
       
      Also, for reference, here's tutorial #40 which has normal shadows but no blur, which I also ported, and it works perfectly.
      https://github.com/mister51213/DX11Port_ShadowMapping
       
    • By xhcao
      Is Direct3D 11 an api function like glMemoryBarrier in OpenGL? For example, if binds a texture to compute shader, compute shader writes some values to texture, then dispatchCompute, after that, read texture content to CPU side. I know, In OpenGL, we could call glMemoryBarrier before reading to assure that texture all content has been updated by compute shader.
      How to handle incoherent memory access in Direct3D 11? Thank you.
    • By _Engine_
      Atum engine is a newcomer in a row of game engines. Most game engines focus on render
      techniques in features list. The main task of Atum is to deliver the best toolset; that’s why,
      as I hope, Atum will be a good light weighted alternative to Unity for indie games. Atum already
      has fully workable editor that has an ability to play test edited scene. All system code has
      simple ideas behind them and focuses on easy to use functionality. That’s why code is minimized
      as much as possible.
      Currently the engine consists from:
      - Scene Editor with ability to play test edited scene;
      - Powerful system for binding properties into the editor;
      - Render system based on DX11 but created as multi API; so, adding support of another GAPI
        is planned;
      - Controls system based on aliases;
      - Font system based on stb_truetype.h;
      - Support of PhysX 3.0, there are samples in repo that use physics;
      - Network code which allows to create server/clinet; there is some code in repo which allows
        to create a simple network game
      I plan to use this engine in multiplayer game - so, I definitely will evolve the engine. Also
      I plan to add support for mobile devices. And of course, the main focus is to create a toolset
      that will ease games creation.
      Link to repo on source code is - https://github.com/ENgineE777/Atum
      Video of work process in track based editor can be at follow link: 
       
       

    • By mister345
      I made a spotlight that
      1. Projects 3d models onto a render target from each light POV to simulate shadows
      2. Cuts a circle out of the square of light that has been projected onto the render target
      as a result of the light frustum, then only lights up the pixels inside that circle 
      (except the shadowed parts of course), so you dont see the square edges of the projected frustum.
       
      After doing an if check to see if the dot product of light direction and light to vertex vector is greater than .95
      to get my initial cutoff, I then multiply the light intensity value inside the resulting circle by the same dot product value,
      which should range between .95 and 1.0.
       
      This should give the light inside that circle a falloff from 100% lit to 0% lit toward the edge of the circle. However,
      there is no falloff. It's just all equally lit inside the circle. Why on earth, I have no idea. If someone could take a gander
      and let me know, please help, thank you so much.
      float CalculateSpotLightIntensity(     float3 LightPos_VertexSpace,      float3 LightDirection_WS,      float3 SurfaceNormal_WS) {     //float3 lightToVertex = normalize(SurfacePosition - LightPos_VertexSpace);     float3 lightToVertex_WS = -LightPos_VertexSpace;          float dotProduct = saturate(dot(normalize(lightToVertex_WS), normalize(LightDirection_WS)));     // METALLIC EFFECT (deactivate for now)     float metalEffect = saturate(dot(SurfaceNormal_WS, normalize(LightPos_VertexSpace)));     if(dotProduct > .95 /*&& metalEffect > .55*/)     {         return saturate(dot(SurfaceNormal_WS, normalize(LightPos_VertexSpace)));         //return saturate(dot(SurfaceNormal_WS, normalize(LightPos_VertexSpace))) * dotProduct;         //return dotProduct;     }     else     {         return 0;     } } float4 LightPixelShader(PixelInputType input) : SV_TARGET {     float2 projectTexCoord;     float depthValue;     float lightDepthValue;     float4 textureColor;     // Set the bias value for fixing the floating point precision issues.     float bias = 0.001f;     // Set the default output color to the ambient light value for all pixels.     float4 lightColor = cb_ambientColor;     /////////////////// NORMAL MAPPING //////////////////     float4 bumpMap = shaderTextures[4].Sample(SampleType, input.tex);     // Expand the range of the normal value from (0, +1) to (-1, +1).     bumpMap = (bumpMap * 2.0f) - 1.0f;     // Change the COORDINATE BASIS of the normal into the space represented by basis vectors tangent, binormal, and normal!     float3 bumpNormal = normalize((bumpMap.x * input.tangent) + (bumpMap.y * input.binormal) + (bumpMap.z * input.normal));     //////////////// LIGHT LOOP ////////////////     for(int i = 0; i < NUM_LIGHTS; ++i)     {     // Calculate the projected texture coordinates.     projectTexCoord.x =  input.vertex_ProjLightSpace[i].x / input.vertex_ProjLightSpace[i].w / 2.0f + 0.5f;     projectTexCoord.y = -input.vertex_ProjLightSpace[i].y / input.vertex_ProjLightSpace[i].w / 2.0f + 0.5f;     if((saturate(projectTexCoord.x) == projectTexCoord.x) && (saturate(projectTexCoord.y) == projectTexCoord.y))     {         // Sample the shadow map depth value from the depth texture using the sampler at the projected texture coordinate location.         depthValue = shaderTextures[6 + i].Sample(SampleTypeClamp, projectTexCoord).r;         // Calculate the depth of the light.         lightDepthValue = input.vertex_ProjLightSpace[i].z / input.vertex_ProjLightSpace[i].w;         // Subtract the bias from the lightDepthValue.         lightDepthValue = lightDepthValue - bias;         float lightVisibility = shaderTextures[6 + i].SampleCmp(SampleTypeComp, projectTexCoord, lightDepthValue );         // Compare the depth of the shadow map value and the depth of the light to determine whether to shadow or to light this pixel.         // If the light is in front of the object then light the pixel, if not then shadow this pixel since an object (occluder) is casting a shadow on it.             if(lightDepthValue < depthValue)             {                 // Calculate the amount of light on this pixel.                 float lightIntensity = saturate(dot(bumpNormal, normalize(input.lightPos_LS[i])));                 if(lightIntensity > 0.0f)                 {                     // Determine the final diffuse color based on the diffuse color and the amount of light intensity.                     float spotLightIntensity = CalculateSpotLightIntensity(                         input.lightPos_LS[i], // NOTE - this is NOT NORMALIZED!!!                         cb_lights[i].lightDirection,                          bumpNormal/*input.normal*/);                     lightColor += cb_lights[i].diffuseColor*spotLightIntensity* .18f; // spotlight                     //lightColor += cb_lights[i].diffuseColor*lightIntensity* .2f; // square light                 }             }         }     }     // Saturate the final light color.     lightColor = saturate(lightColor);    // lightColor = saturate( CalculateNormalMapIntensity(input, lightColor, cb_lights[0].lightDirection));     // TEXTURE ANIMATION -  Sample pixel color from texture at this texture coordinate location.     input.tex.x += textureTranslation;     // BLENDING     float4 color1 = shaderTextures[0].Sample(SampleTypeWrap, input.tex);     float4 color2 = shaderTextures[1].Sample(SampleTypeWrap, input.tex);     float4 alphaValue = shaderTextures[3].Sample(SampleTypeWrap, input.tex);     textureColor = saturate((alphaValue * color1) + ((1.0f - alphaValue) * color2));     // Combine the light and texture color.     float4 finalColor = lightColor * textureColor;     /////// TRANSPARENCY /////////     //finalColor.a = 0.2f;     return finalColor; }  
      Light_vs.hlsl
      Light_ps.hlsl
  • Advertisement