Announcement

Collapse
No announcement yet.

Vray not saving files out when using phoenix

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

  • Vray not saving files out when using phoenix

    I did a fairly large sim last night and cannot get any of the frames to save out. sometimes they do, but 3/4 of them got to 'rendering image: done' and sit there. no effort to save out a file, process stuck at a steady 12%.

    The machines never get released either - If i delete the job off the server, the frame buffer stays up and it wont take another job. If i close the backburner server and re-open it they still wont take another job - i have to manually kill the process to get it to take another frame.
    30 frames into any animation the entire farm is completely locked up and i have to manually go through killing the process of every max file. No matter how long i wait, it's totally locked up with no files created.

    Was using the max fb - no files whatsoever were getting saved out. now with the vray frame buffer it's 1 in every 4. saving to .exrs, only 4 channels, 1280wide frame.

    sim was 22mil, most frames are 45mb, the occasional bigger one is 170mb Any ideas?
    Last edited by Neilg; 09-04-2014, 11:33 AM.


  • #2
    With the phoenix water/ocean object hidden - but the splash & foam still on, it saves out fine. it's just the water object itself.

    e: I tell a lie - it is still doing it. just less often, made it through 2 frames on each machine before it happened. every one is currently locked up.

    e2: Motion blur was the culprit - switched it off and it saves out fine now. No idea how that would have been affecting a render that was already finished and just needed saving. I did notice that despite having that on & camera motion blur on, both foam and splash had motion blur set to 'force off'. maybe that caused a conflict? idk, it works now.
    Last edited by Neilg; 09-04-2014, 12:29 PM.

    Comment


    • #3
      can you check the consumed memory? i think it could be a memory overload issue.
      the force off option is not in conflict with the general mb, it just will produce no mb.
      and one more question - can it be reproduced with single frame on the local machine?
      ______________________________________________
      VRScans developer

      Comment


      • #4
        It was getting very close to the 16gb limit on the render nodes. To the point where i was worried it'd choke, but it seemed to finish rendering fine. You're probably right.
        The local machine has 64gb ram so idk... Will do some tests later anyway.

        Comment

        Working...
        X