Announcement

Collapse
No announcement yet.

Rendering problem with 3dsMax 2015/Vray2.51/PhoenixFD2.2

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

  • Rendering problem with 3dsMax 2015/Vray2.51/PhoenixFD2.2

    Hi Ivaylo,
    I just installed 3dsMax 2015, Vray 2.51 and PhoenixFD 2.2 and did a test render. Everytime when I try to render even a very simple simulation, it renders forever all my cpus are on 100%, nothing shows up in the render window and I canĀ“t even cancel the rendering process. I then have to end the process in the task-manager. The same behaviour with the scanline renderer. I tried it with some different scenes, always the same behaviour. When I tested exact the same scene on 3ds max 2014/Vray 2.4/PhoenixFD 2.2 it rendered as usual with no problem in a few seconds.

    Thanks in advance,

    Jan

  • #2
    we have no official builds for max 2015, so this is a nightly build, can you tell me the revision? you can find it in the about box, see the simulator buttons
    ______________________________________________
    VRScans developer

    Comment


    • #3
      Ok, I understand. Sorry, I forgot to mention that is was a nightly build, the revision is 24810.

      Comment


      • #4
        Hello, can you please try a nightly build form the previous day - we have this same issue here as well today, but and older build will be fine
        Svetlin Nikolov, Ex Phoenix team lead

        Comment


        • #5
          Ok, I see, I will try that. Thanks for your help!

          Jan

          Comment


          • #6
            hi again, is this happening with a brand new scene, or only old scenes?
            ______________________________________________
            VRScans developer

            Comment


            • #7
              Yeah, I tried it with a brand new scene. After that I also tried an old scene but it was the same behaviour.
              I just did a test with an older nightly build (rev: 24803), like Svetlin said, and it works fine now.

              Thanks again,

              Jan

              Comment


              • #8
                it's fixed already, the issue exists only in the today's builds
                ______________________________________________
                VRScans developer

                Comment

                Working...
                X