Announcement

Collapse
No announcement yet.

Auto exposure issue

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

  • Auto exposure issue

    Hey guys,

    I keep getting this error even when I am rendering with all cameras on and auto exposure on. Also light cache is on. Any ideas?

    Maya 2018. Vray Next update 2.1 (4.30.01)
    Website
    https://mangobeard.com/
    Behance
    https://www.behance.net/seandunderdale

  • #2
    The shot is correctly exposed by the auto exposure during the render, but throws that error up when I try to copy settings to the camera.
    Website
    https://mangobeard.com/
    Behance
    https://www.behance.net/seandunderdale

    Comment


    • #3
      It seems to be working fine with the said versions. Do your cameras have a 'physical camera' V-Ray attribute? Does this happen on a specific scene? Could you attach it here?
      Aleksandar Hadzhiev | chaos.com
      Chaos Support Representative | contact us

      Comment


      • #4
        Ive got physical camera on. It worked when I first installed Next ages ago, but in recent months its never copied over. Ill see what happens on a fresh scene and if it is still an issue Ill send it over. Probably just need to delete maya prefs as usual...
        Website
        https://mangobeard.com/
        Behance
        https://www.behance.net/seandunderdale

        Comment


        • #5
          Ok Ive worked out whats happening, and how to fix it. If I open a new scene, make a plane, a sphere, a dome / hdri and a camera. Enable physical cam. CUDA mode with Light cache and auto exp on.

          If I render and try to transfer cam settings it errors. If I switch to CPU, re-render and try, it works. Then if I switch back to cuda AFTER it working in CPU mode, it also continues to work. So it seems I have to render in CPU mode before CUDA mode will work.
          Website
          https://mangobeard.com/
          Behance
          https://www.behance.net/seandunderdale

          Comment


          • #6
            Yes, you are right. The issue is already logged (internal bug-tracker id: VMAYA-8052) for developer analysis. I'll give it a priority bump. For now, the mentioned workaround should suffice.
            Aleksandar Hadzhiev | chaos.com
            Chaos Support Representative | contact us

            Comment

            Working...
            X