search

ChristianLa91 / slimdx

Automatically exported from code.google.com/p/slimdx
MIT License
0 stars 0 forks source link

Compute Shaders 5.0 #723

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
When I render many Compute Shaders the application stop and Windows give me a 
message: "The controller of screen stop answering and recover correctly, Kernel 
driver...".

Why? I use Direct3D 11 with SlimDX June 2010. It is more stable the compiler of 
ComputeShader in Direct3D 10?

Thanks.

Original issue reported on code.google.com by jerez.ra...@gmail.com on 7 Oct 2010 at 1:19

GoogleCodeExporter commented 9 years ago 
More explication:

When I "Dispatch" a compute shader and I use the UAV texture of this as input 
of other compute shader (as SRV), when I concatenate 3 or 4 compute shader, the 
texture UAV generate is black. Why? It is for memory? Order of assignations?? 
Help me please. I need to finish a project that use it.

Thanks.

Original comment by jerez.ra...@gmail.com on 8 Oct 2010 at 8:36

GoogleCodeExporter commented 9 years ago 
Do you have any reason to believe that your problems are related to SlimDX?  
This is an issue tracker for SlimDX.  If you need help with DirectX, you should 
try asking here:
http://www.gamedev.net/community/forums/forum.asp?forum_id=10

Original comment by tom.gran...@gmail.com on 8 Oct 2010 at 2:23

GoogleCodeExporter commented 9 years ago 
And nothing has experimented this issue? I don´t say that this issue is for 
SlimDX but i would to know if you know that exist bugs relatives to it.

There is few documentation over CS5.0 and I don´t know if I'am using well the 
Compute Shaders.

There is a basic rules? 

Thanks.

Original comment by jerez.ra...@gmail.com on 8 Oct 2010 at 2:33

GoogleCodeExporter commented 9 years ago 
All SlimDX does is pass parameters down to the native layer, really. The error 
you are getting sounds like a driver problem, but without more information / 
code there's nothing we can look at here. You should also try to reproduce the 
call stream you're making in native Direct3D and see if you still get the error.

Original comment by josh.petrie on 10 Oct 2010 at 1:11

GoogleCodeExporter commented 9 years ago 
Dieter said as much in the corresponding GDNet thread. We can close this as not 
a SlimDX issue.

Original comment by Mike.Popoloski on 10 Oct 2010 at 1:38