Tracy Profiler mismatch version

Omniverse Archive Omniverse Technical Support
1

Tried to run the Tracy Profiler based on these instructions.

I added this line to my .kit file in the dependencies section:

"omni.kit.profiler.tracy" = {}

I see the menu option and am able to launch Tracy this way, but I get the error:

The client you are trying to connect uses incompatible protocol version. Make sure you are using the same tracy version on both client and server.

I launched my kit app using an elevated powershell and:

.\composer.bat --/app/profilerBackend=‘tracy’ --/app/profileFromStart=true --/profiler/gpu/tracyInject/enabled=true

2

Understood. Can you tell me what version of Tracy and what version of kit, exactly please? Where did you download Tracy? Did you try updating to the latest version from Github ?
GitHub - wolfpld/tracy: Frame profiler

3

Hi,

I’m using kit 106.5 (the new 107 kit app template cannot load my stage) and I didn’t manually download or install tracy, I simply added the dependency to my kit file and that is where the tracy installation came from.

Tracy version is 0.11.1 (latest version)
omni.kit.profiler.trac is 1.2.0

This is what the carb logs say:
2025-03-31 23:43:40 [Info] [omni.kit.profiler.tracy.tracy] launch_process_async : [‘e:/kit-app-template/_build/windows-x86_64/release/extscache/omni.kit.profiler.tracy-1.2.0+wx64\bin\Tracy.exe’, ‘-a’, ‘127.0.0.1’]
2025-03-31 23:43:40 [Info] [carb] Registered plugin: carb.profiler-tracy.plugin (interfaces: [carb::profiler::IProfiler v1.5],[carb::tasking::IFiberEvents v1.0]) (impl: carb.profiler-tracy.plugin)
2025-03-31 23:43:40 [Info] [carb] Initializing plugin: carb.profiler-tracy.plugin (interfaces: [carb::profiler::IProfiler v1.5],[carb::tasking::IFiberEvents v1.0]) (impl: carb.profiler-tracy.plugin)
2025-03-31 23:43:41 [Info] [carb] Plugin carb.tasking.plugin is already a dependency of carb.memorytracking; not changing unload order

4

Hmm, well why I go ask more about this Tracy extension, 3 questions:

  1. What are you trying to use Tracy for?
  2. Have you tried our own standalone Tracy which is more powerful?
  3. And you say that “107 kit app template cannot load my stage”. Let’s explore that. You have a particular usd file that will not load with 107? That is strange. It will not load at all, or just your specific file? Please give details.
5
  1. I need to to analyze my stage / behavior scripts / action graph to find what parts are slowing down my simulation (I have a lot going on)
  2. I didn’t realize there was a different way to use Tracy. I’m happy to do that, can you point me to the docs on how?
  3. I can start a new thread for the issue with 107, I don’t want to conflate these
6

I am going to ask for specific help on using Tracy correctly. Please stand by.

7

Hey @brainstencil

Can you try deleting the folder e:/kit-app-template/_build/windows-x86_64/release/extscache/omni.kit.profiler.tracy-1.2.0+wx64 and reinstall the Tracy profiler extension?

8

Is this correct?

  1. Comment out the line in my kit file:
# "omni.kit.profiler.tracy" = {}

  1. Delete the folder: e:/kit-app-template/_build/windows-x86_64/release/extscache/omni.kit.profiler.tracy-1.2.0+wx64

  2. Rebuild

.\repo.bat build -x
  1. Uncomment
 "omni.kit.profiler.tracy" = {}
  1. Rebuild
.\repo.bat build

Let me know if I missed anything?

9

Yes, give that a try and let me know :)

10

it’s working now. The behavior is the same but I changed the IP. I guess it was simply the wrong IP address… I had assumed the default loopback address was correct, but it works when I use one of my IPs

11

Interesting! Thanks for the update! Glad it works now