Announcement

Collapse
No announcement yet.

VrayCamera to USD and Nuke

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

  • VrayCamera to USD and Nuke

    Hello,
    I recently activly use Nuke for compositnig and need the same camera from 3ds max in Nuke, but currently when I load camera (exported from 3ds max via USDa) into Nuke it's not read Focal Length, Tils and Shifths of lens, and horizontal apperture/verticalAperture as well zoom in camera not taken into account. There is way to export camera from 3ds max taking into account all settings of the camera and seamlessly bring to Nuke?

  • #2
    Thing is that the VRayCamera parameters are correctly exported (you can check it yourself by exporting the .usd as ASCII and opening it in Notepad), but are probably not read. There is a similar limitation in 3ds Max, where, currently, only the Transforms, FOV, and Animation are read through a USDStage. I presume the case with Foundry is similar.
    Aleksandar Hadzhiev | chaos.com
    Chaos Support Representative | contact us

    Comment


    • #3
      Originally posted by hermit.crab View Post
      Thing is that the VRayCamera parameters are correctly exported (you can check it yourself by exporting the .usd as ASCII and opening it in Notepad), but are probably not read. There is a similar limitation in 3ds Max, where, currently, only the Transforms, FOV, and Animation are read through a USDStage. I presume the case with Foundry is similar.
      I guess that solution for this would be use Vray for Nuke, but it's not updated already for 2 years

      Comment


      • #4
        Originally posted by hermit.crab View Post
        Thing is that the VRayCamera parameters are correctly exported (you can check it yourself by exporting the .usd as ASCII and opening it in Notepad), but are probably not read. There is a similar limitation in 3ds Max, where, currently, only the Transforms, FOV, and Animation are read through a USDStage. I presume the case with Foundry is similar.
        and actually Houdini don't read it, as format of the custom attribute, that just simply not recognizable by other DCCs that have no vray, maybe parameters of the camera need to be written down using common primvars?

        Comment

        Working...
        X