Cannot display geometry with deinterleaved vertex buffers?
Hello I am a big fan of Nsight. Some time ago I've rewritten a graphics engine to use deinterleaved vertex buffers, so that positions, normals, texcoords, etc. are in their own buffers but multiple ones are bound with IASetVertexBuffers in DX11. My problem is, that Nsight graphics debugger's Geometry window inside Visual Studio stopped displaying my meshes. There are no error messages just an empty viewport window. There are some floating point specials though in my vertex data but that was never a problem for me.
Hello I am a big fan of Nsight. Some time ago I've rewritten a graphics engine to use deinterleaved vertex buffers, so that positions, normals, texcoords, etc. are in their own buffers but multiple ones are bound with IASetVertexBuffers in DX11. My problem is, that Nsight graphics debugger's Geometry window inside Visual Studio stopped displaying my meshes.
There are no error messages just an empty viewport window. There are some floating point specials though in my vertex data but that was never a problem for me.

#1
Posted 05/24/2017 09:52 AM   
Hi, I'm sorry for the problem you met, please provide more information for investigating the problem: - Nsight version - GPU, OS, driver info - did the Geometry window display the meshes before? - Can we have your sample to do some local repro, then we can identify the crash quickly? Thanks, Letitia
Hi,

I'm sorry for the problem you met, please provide more information for investigating the problem:
- Nsight version
- GPU, OS, driver info
- did the Geometry window display the meshes before?
- Can we have your sample to do some local repro, then we can identify the crash quickly?

Thanks,
Letitia

#2
Posted 05/25/2017 02:54 AM   
Nsight version: 5.2.0.16321 GPU: Nvidia GTX 1070 Driver: 381.65 OS: Windows 10 Pro 10.0.15063 The geometry window displayed meshes before. My project is on GitHub: https://github.com/turanszkij/WickedEngine Usage is simple: 1.) Click on LoadModel button in the top right corner 2.) Browse to WickedEngine/models/Sample/scene.wimf and open the file 3.) Capture using Nsight graphics debugger Thanks for getting back to me!
Nsight version: 5.2.0.16321
GPU: Nvidia GTX 1070
Driver: 381.65
OS: Windows 10 Pro 10.0.15063

The geometry window displayed meshes before.

My project is on GitHub: https://github.com/turanszkij/WickedEngine

Usage is simple:
1.) Click on LoadModel button in the top right corner
2.) Browse to WickedEngine/models/Sample/scene.wimf and open the file
3.) Capture using Nsight graphics debugger

Thanks for getting back to me!

#3
Posted 05/25/2017 08:40 AM   
Hi, I checked the sample locally,there're some issues of memory data shown in the geometry view: - some data are nan which cannot be displayed. - in a draw call, the primitive polygon is triangle, but the memory data is shown as the picture, the data cannot compose a triangle. [url]http://imgur.com/a/6F364[/url] Can you please tell me in which draw calls the geometry view showed nothing but it was displayed before? then we can identify the crash quickly. Thanks, Letitia
Hi,

I checked the sample locally,there're some issues of memory data shown in the geometry view:
- some data are nan which cannot be displayed.
- in a draw call, the primitive polygon is triangle, but the memory data is shown as the picture, the data cannot compose a triangle.
http://imgur.com/a/6F364

Can you please tell me in which draw calls the geometry view showed nothing but it was displayed before? then we can identify the crash quickly.

Thanks,
Letitia

#4
Posted 05/26/2017 07:52 AM   
Thank you for checking this issue so fast. I could see every mesh rendered in the geometry window which I rendered from input assembler data previously, but now nothing shows up. The strange thing about the nans in the VB is that in the application side I don't see strange data at all in the vertex arrays. And rendering without the debugger is also correct. I assumed the floating point specials are detected because of a bug in Nsight and overlooked it so far.
Thank you for checking this issue so fast.

I could see every mesh rendered in the geometry window which I rendered from input assembler data previously, but now nothing shows up. The strange thing about the nans in the VB is that in the application side I don't see strange data at all in the vertex arrays. And rendering without the debugger is also correct. I assumed the floating point specials are detected because of a bug in Nsight and overlooked it so far.

#5
Posted 05/26/2017 08:42 AM   
I've just checked with Visual Studio graphics debugger and my mesh data definetly doesn't contain so much faulty data that Nsight tells me.
I've just checked with Visual Studio graphics debugger and my mesh data definetly doesn't contain so much faulty data that Nsight tells me.

#6
Posted 05/26/2017 08:58 AM   
Hi, An internal bug is created for the problem, we'll do more research. Regards, Letitia
Hi,

An internal bug is created for the problem, we'll do more research.

Regards,
Letitia

#7
Posted 06/06/2017 08:05 AM   
Hi, any news on this? It still doesn't work for me in Nsight 5.5. The data appears to be correct when inspecting the buffer contents in the resource viewer window, however the geometry window shows nans and completely messed up data. The geometry window also doesn't display the mesh at all. I have a sample app which can reproduce the issue: http://www.mediafire.com/file/jhd82aibxiag57d/WickedEngineLDSSkinningTest.zip The issue is visible in the very first draw call. Kind Regards, Janos
Hi, any news on this? It still doesn't work for me in Nsight 5.5. The data appears to be correct when inspecting the buffer contents in the resource viewer window, however the geometry window shows nans and completely messed up data. The geometry window also doesn't display the mesh at all.
I have a sample app which can reproduce the issue: http://www.mediafire.com/file/jhd82aibxiag57d/WickedEngineLDSSkinningTest.zip

The issue is visible in the very first draw call.

Kind Regards,
Janos

#8
Posted 02/07/2018 10:05 AM   
Hi turanszkij, I'm sorry the bug is still unresolved. I'll tell you if there're some update. Thanks, Letitia
Hi turanszkij,

I'm sorry the bug is still unresolved.
I'll tell you if there're some update.

Thanks,
Letitia

#9
Posted 02/08/2018 09:11 AM   
Hi turanszkij, I believe Nsight should fixed this bug and will be available in the coming release. I just check your issue with internal latest Nsight, the Geometry view's graphical and memory tab looks as expected, I can see the points and tex coord from different vertex buffers and the model looks good. Thanks An
Hi turanszkij,

I believe Nsight should fixed this bug and will be available in the coming release. I just check your issue with internal latest Nsight, the Geometry view's graphical and memory tab looks as expected, I can see the points and tex coord from different vertex buffers and the model looks good.

Thanks
An

#10
Posted 03/26/2018 11:00 AM   
Thank you, that's good to hear. I will check this when the new release is available. :)
Thank you, that's good to hear. I will check this when the new release is available. :)

#11
Posted 03/26/2018 11:06 AM   
Scroll To Top

Add Reply