# DX11 DX11 Assimp - Mesh got messed up!

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

## Recommended Posts

All right guys,

I've been using Assimp for a while now and in most of the cases it works fine! But then this happened:

View from the Assimp viewer:

Post processing:

const aiScene* scene = importer.ReadFile( pFile,
aiProcess_GenNormals			 |
aiProcess_CalcTangentSpace       |
aiProcess_GenUVCoords            |
aiProcess_Triangulate            |
aiProcess_FlipUVs				 |
aiProcess_TransformUVCoords      |
aiProcess_SortByPType);


Now I don't think there's anything wrong with my other code as many previous examples worked perfectly!

Now this may be a bit vein, but does anybody know what could be the problem? (BTW. In Assimp, that model is the huge cube in my program)

##### Share on other sites

Which version of Assimp are you using? You should compile the library from the latest code from the svn, as they don't release all that often. They've also done work on the obj importer recently.

If it still doesn't work, it would be worth asking them directly on the sourceforge project's help forum, and provide the file that's causing you trouble.

##### Share on other sites

There are 2 possibilities of what happens in Assimp Viewer:

2. Assimp auto-generated normals using some smoothing angle which was too high and it ended up horrible

I'm not sure what I'm seeing in your program though. Are you sure model isn't simply upside down? It seems to contain more than 1 mesh, do you join vertex and index buffers correctly? (assuming you do that)

##### Share on other sites

Okay,

first of all I'm using v3.0.

So i tried to inverse the normals, but no luck.

And no, the model isn't inverse...

Sorry guys, that's the best i can give you, and I know my multiple mesh renderer works as I've usen it before.

##### Share on other sites

Oh well,

last night I was messing around with some code and then somehow I fixed the bug, I believe that the bug was part of my engine, sorry to bother you guys!

But thanks!

• 10
• 11
• 9
• 16
• 18
• ### Similar Content

• I wanted to see how others are currently handling descriptor heap updates and management.
I've read a few articles and there tends to be three major strategies :
1 ) You split up descriptor heaps per shader stage ( i.e one for vertex shader , pixel , hull, etc)
2) You have one descriptor heap for an entire pipeline
3) You split up descriptor heaps for update each update frequency (i.e EResourceSet_PerInstance , EResourceSet_PerPass , EResourceSet_PerMaterial, etc)
The benefits of the first two approaches is that it makes it easier to port current code, and descriptor / resource descriptor management and updating tends to be easier to manage, but it seems to be not as efficient.
The benefits of the third approach seems to be that it's the most efficient because you only manage and update objects when they change.

• hi,
until now i use typical vertexshader approach for skinning with a Constantbuffer containing the transform matrix for the bones and an the vertexbuffer containing bone index and bone weight.
Now i have implemented realtime environment  probe cubemaping so i have to render my scene from many point of views and the time for skinning takes too long because it is recalculated for every side of the cubemap.
For Info i am working on Win7 an therefore use one Shadermodel 5.0 not 5.x that have more options, or is there a way to use 5.x in Win 7
My Graphic Card is Directx 12 compatible NVidia GTX 960
the member turanszkij has posted a good for me understandable compute shader. ( for Info: in his engine he uses an optimized version of it )
Now my questions
is it possible to feed the compute shader with my orignial vertexbuffer or do i have to copy it in several ByteAdressBuffers as implemented in the following code ?
the same question is about the constant buffer of the matrixes
my more urgent question is how do i feed my normal pipeline with the result of the compute Shader which are 2 RWByteAddressBuffers that contain position an normal
for example i could use 2 vertexbuffer bindings
1 containing only the uv coordinates
2.containing position and normal
How do i copy from the RWByteAddressBuffers to the vertexbuffer ?

(Code from turanszkij )
Here is my shader implementation for skinning a mesh in a compute shader:

• Hi, can someone please explain why this is giving an assertion EyePosition!=0 exception?

It looks like DirectX doesnt want the 2nd parameter to be a zero vector in the assertion, but I passed in a zero vector with this exact same code in another program and it ran just fine. (Here is the version of the code that worked - note XMLoadFloat3(&m_lookAt) parameter value is (0,0,0) at runtime - I debugged it - but it throws no exceptions.
and here is the repo with the alternative version of the code that is working with a value of (0,0,0) for the second parameter.

• 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