Announcement

Collapse
No announcement yet.

Embree error when network rendering

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

  • Embree error when network rendering

    Hi

    I've recently upgraded to V-Ray 6.1006 for max 2023 and now I'm getting this error when network rendering using Backburner:
    Job 'xxxx' ERR Error message: 3dsmax adapter error : Autodesk (Autodesk 3ds Max 2023 (64-bit)) failed for Renderslave 25.3 reported error: [V-Ray] Error building Embree static ray caster, error message: [CommitEmbreeThread::threadProc] 1: Setting progress monitor function failed

    The frames/AOV's are fully rendered - and saved - but the error makes max shut down after completing each frame and then restart for the next frame, which is not ideal.
    My workstation and slave report the same error (Intel and AMD CPU's respectively) and they both have plenty of memory to spare when rendering this scene.
    I don't recall getting this error in earlier versions of V-Ray 6.
    http://henrikbclausen.com

  • #2
    Hello,

    It would be best if you could send a scene to our support for this one

    Best regards,
    Yavor
    Yavor Rubenov
    V-Ray for 3ds Max developer

    Comment


    • #3
      Hi, please use the support contact form to send us the scene. Please include a link to this thread in your e-mail.
      Vladimir Krastev | chaos.com
      Chaos Support Representative | contact us

      Comment


      • #4
        Submitted it now - along with a link to the archived scene file.
        http://henrikbclausen.com

        Comment


        • #5
          Following for similar issue when I use DR. I can render fine on each machine individually, but as soon as I turn on DR I get the " [13:56:54.368] Error : Error building Embree static ray caster, error message: [CommitEmbreeThread::threadProc] 1: Committing scene failed"
          Everything was working fine earlier in the week.

          Comment


          • #6
            Hi, thanks for the scene, we are looking into it.

            Everything was working fine earlier in the week.
            Do you recall what has been changed since then? Are you getting the error in each scene or only in one scene? If you have only one/few scenes with the error please send it to support.
            Vladimir Krastev | chaos.com
            Chaos Support Representative | contact us

            Comment


            • #7
              Hi, the issue is reported under VMAX-13315 in our bug tracking system.
              Vladimir Krastev | chaos.com
              Chaos Support Representative | contact us

              Comment

              Working...
              X