Is DenoiseRaytraced supposed to work?

If I follow the link in the Package Manager it leads to a GitHub page where it says: “The command DenoiseRaytracedCheck will walk you through the setup of the tool.” Sounds promising!
But if I do so in Rhino, a Windows Explorer opens and a zip file downloads. Not what I would call a “walk through” but I understand that I have to copy the content of the zip archive in this opened folder.
After doing so, the command DenoiseRaytraced asks for a file name and location, a width and an height, the number of passes and the it aborts saying it wasn’t able to start the Raytrace mode.

Ok, I found the problem; the viewport must not be in Raytraced mode before entering the command… it may be worth it to check for this?

I would say that Denoise at it’s current state is a hidden “techdemo” for the nerdiest :slight_smile:

The command-line has the instructions after running the check command.

The command works with the target viewport in any mode, including Raytraced.

On thing I noticed is that the tool doesn’t like spaces in paths. I’ll fix that tomorrow.

1 Like

I don’t know if this problem is still relevant? I just checked it a little and it works fine. I put downloaded files in the:

\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\Denoise Raytraced (faede54a-4082-46f4-80b0-0bc9cc5069c3)\settings\

Then just run the command DenoiseRaytraced
Spaces in the paths are still not working :stuck_out_tongue:

Nice stuff indeed.
A lot is going on in the rendering area, but I feel like many things are deeply in the WIP state or hidden somewhere. Since some time ago I decided to move out from V-ray, I would really like to see all that stuff that @nathanletwory is working on, a little more available to users.
Well, maybe not everything at once, but every couple of months another more or less “ready to work” tool.

very simple test, 200 passes:


1 Like