search

gerardorosiles / slimdx

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

[June 2010] Uknown shader reflection and/or dynamic shader linkage usage mechanics #765

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I have problems with managing(or even getting basic stuff working) for shader 
reflection and dynamic shader linkage - SlimDX current state does not accept 
usage specified in DX SDK documentation. How do i use shader reflection? Doing 
stuff like ShaderReflection refl = new ShaderReflection(myShaderBytecode) gives 
me runtime error, also dynamic shader linkage usage is unclear as it does not 
match with native direct3d 11.. Any help or guidelines?

Original issue reported on code.google.com by oskarsla...@gmail.com on 7 Jan 2011 at 2:38

GoogleCodeExporter commented 9 years ago 
When you say "SlimDX current state does not accept usage specified in DX SDK 
documentation," what do you mean exactly? Similarly, what runtime error do you 
get when you try to create a new ShaderReflection object? You're going to have 
to be more specific, I'm afraid.

Original comment by josh.petrie on 7 Jan 2011 at 3:54

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
It means that i cant port C++ samples to SlimDX using C#, because SlimDX does 
not provide interfaces and general usage structure similar to one in native 
version. It could be fine, but as there is only class definition documentation, 
its unclear how should i get similar results. Could you please provide simple 
(meaning few lines of code) example of how i should use shader reflection?

Original comment by oskarsla...@gmail.com on 12 Jan 2011 at 3:55

GoogleCodeExporter commented 9 years ago 
You're going to have to be more specific about what's wrong. The 
ShaderReflection constructor calls D3DReflect internally. After that, all the 
methods and types should match up just fine.

Original comment by Mike.Popoloski on 22 Jan 2011 at 12:00

GoogleCodeExporter commented 9 years ago 
Without some sort of indication about what's wrong, we can't actually fix 
anything. If you come back to this at some point make a new issue and tell us 
more specifically what the problem is.

Original comment by Mike.Popoloski on 27 Feb 2011 at 9:52