#Error Finder | How To Find, Debug And Fix Your uVS Red Nodes (Errors)

1 messages · Page 1 of 1 (latest)

karmic shore
#

Have you ever had an error and you don't know what is causing it?

Sometimes clicking the console log error... it doens't take you to the responsible gameObject or to the asset in Project files tab?

Then you'll need to add this.

image.png
karmic shore
#

Credit to @drifting grail and the team behind the community addons. This is an extract from that, and I believe it's the ESSENTIAL for any uVS programmer.

karmic shore
#

Want to find every red node (errors) in your Unity Visual Script?

Download this file and import it in your Unity project.

  1. Add this file to your Unity Project
  2. Let it compile
  3. Click on Unity Editor top tab >> Window >> uVS Error Finder

Then you'll get a list of all red nodes. Click on each to find where is the possible cause. It'll warp you to the responsible Graph and select the right gameObject.

Please be aware that one red node may not be the CAUSE (root) but a consequence or part of the flow. Being organized helps to find that cause.

karmic shore
#

Latest update 29 08 2025

We made some modifications so now it displays at once in the search results:

gameObject | Node Type | Error Details | Path of script (shows one folder)

So you can see quickly what gameObject is responsible for the error, you click the result and goes to that in the hierarchy.
It also shows you what node is red, and takes you to that graph and center it in the screen.

Then the details of the error so you may know why it is happening.. and for further debugging, it shows the filepath of the script.

image.png
#

Any idea to make it better? Leave your request below:

wet otter
#

Hi, the code works great, but my custom nodes cann't be seen in the context menu if I want to add new node. If i comment your code, custom nodes will come back. Regenerate Nodes doesn't work either.