Jump to content

  • Log In with Google      Sign In   
  • Create Account


Member Since 17 Mar 2013
Offline Last Active Jun 26 2016 07:02 AM

#5298083 .Net DX12

Posted by on 26 June 2016 - 02:49 AM

The biggest Pro for SlimDX by my opinion is, that it works fine with VB.NET. SharpDX does not support VB.NET because they messsed up some case sensitive exports. Another big point are projects which are already done in SlimDX. So @promit, pleeeeaasse continue your great work! :rolleyes:

#5237873 CS write to Texture

Posted by on 01 July 2015 - 09:14 AM

Oh fu** ... sorry guys. I was calling the dispatch(8, 8, 0) instead of (8, 8, 1)

DirectX gives me millions of warnings for each pice of shit, why not in this case.. this took me the whole day..

#5236683 Best technique for lighting

Posted by on 25 June 2015 - 01:05 AM

At first thank you for your answers. Lets split it into two different problems:


Shadow Mapping:

I think the problem with the Tiled approach would be that I also have a Projection Texture AND Shadowmap. Finally I'm not sure about the maximum Texture Array size. Next question would be, is it possible to render the shadowmap directly into the array on a specific slice or to I have to copy the single shadowmaps into the array?


Shading/Texture Projection

As I mentioned before, the current approach to render the projection (by drawing a frustum mesh) isn't really an optimal solution, because it waste a lot of GPU power. Please have a look on the attached Images. The first one shows a current approach and the second would be perfect, but I don't know how.




I also thought about an another approach for texture projection, please let me know what you think:
In a computeshader just use the shadowmap to reconstruct a worldPos, Project it back to Screenspace to figure out GBuffer coords and finally do the shading. But I think the problem here will be the undersamping/interpolation, because of fixed size of the shadowmap.