Announcement

Collapse
No announcement yet.

VrayDenoiser node does not work when loaded from network

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • VrayDenoiser node does not work when loaded from network

    Hello, i'm not sure if it's the right forum to ask this question but we are adding the possibility to our artists to denoise image in comp using the amazing vraydenoiser node. But our pipeline is loading nuke gizmos, plugins from a network shared folder. Everything is working well except the vraydenoiser node that is outputting a blank error message when loaded from a shared path. When the path is local everything is working well.

    To resume in the init.py if is local :
    Code:
    import nuke
    
    nuke.pluginAddPath('C:/local_folder/VrayDenoiser')​
    works and we can use the node, but :
    Code:
    import nuke
    
    nuke.pluginAddPath('//network_folder/VrayDenoiser')​
    ​When we create the node we have this error message :
    Click image for larger version

Name:	vraydenoiser_network_issue.jpg
Views:	287
Size:	16.8 KB
ID:	1192367
    We even tried to map the network path to a mapped drive same issue. We can't install locally on every workstation and render farm the node since the pipeline dynamically load eveyrthing for the artist.

    Thanks for your help. We are using nuke 13.0v4

  • #2
    Hello, maybe there is a better place to ask for this ?

    Comment


    • #3
      I'm troubleshooting it. Will write again with more info.
      Aleksandar Hadzhiev | chaos.com
      Chaos Support Representative | contact us

      Comment


      • #4
        After some thorough testing, it does work for both network paths and mapped drives. A few things to note:
        1. Make sure the init.py file is in ASCII encoding.
        2. Make sure the VRayDenoiser version corresponds to the Nuke version (downloads here)
        3. Check permissions.

        Also, are there any errors printed in the console?
        Aleksandar Hadzhiev | chaos.com
        Chaos Support Representative | contact us

        Comment


        • #5
          Thanks for the answer, now it's working. I don't know what changed but everything seems fine.

          Comment

          Working...
          X