Range Profiler stopped working
Hello I was a happy user of the Range Profiler tool in Nsight but it stopped displaying information lately. I have tried it with a GTX 960 and a GTX 1070 GPUs but it Works for neither one. The ranges are displayed on the top with timing information, but the Range Info, Pipeline Overview and Memory are all displaying zeroes and N/A. What can I do, I want to continue profiling my application?
Hello I was a happy user of the Range Profiler tool in Nsight but it stopped displaying information lately. I have tried it with a GTX 960 and a GTX 1070 GPUs but it Works for neither one.
The ranges are displayed on the top with timing information, but the Range Info, Pipeline Overview and Memory are all displaying zeroes and N/A. What can I do, I want to continue profiling my application?

#1
Posted 05/24/2017 10:03 AM   
Hi, I'm sorry for the problem you met, please provide more information for investigating the problem: - Nsight version - OS, driver info - 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
- OS, driver info
- 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:44 AM   
Nsight version: 5.2.0.16321 GPU: Nvidia GTX 1070 Driver: 381.65 OS: Windows 10 Pro 10.0.15063 The range profiler was working for me some time ago. 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 range profiler was working for me some time ago.

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:41 AM   
Hi, We’re working on the release build and I checked the application with the internal build, which didn’t trigger the issue. Please wait for the release build and check it again. Thanks, Letitia
Hi,

We’re working on the release build and I checked the application with the internal build, which didn’t trigger the issue.
Please wait for the release build and check it again.

Thanks,
Letitia

#4
Posted 05/26/2017 07:05 AM   
Thank you I will wait for the update!
Thank you I will wait for the update!

#5
Posted 05/26/2017 08:29 AM   
Hi, The range profiler started working for me again when I started Visual Studio 2015 with administrator rights and Nsight monitor also starts with admin rights when starting it from Studio.
Hi, The range profiler started working for me again when I started Visual Studio 2015 with administrator rights and Nsight monitor also starts with admin rights when starting it from Studio.

#6
Posted 06/14/2017 05:43 PM   
I'm glad to hear the news. Please tell us if you encounter other problems.
I'm glad to hear the news.

Please tell us if you encounter other problems.

#7
Posted 06/15/2017 09:20 AM   
Scroll To Top

Add Reply