Announcement

Collapse
No announcement yet.

Spawner not rendering

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

  • #16
    It took about 25gb , with host machine 64gb and nodes 24gb-32gb of memory.
    Quite weird thing is that one of the main servers (which was acting as host for DR nodes) died couple of days ago , not starting at all , with motherboard LED status reporting something related to CPU bridge.
    So it might be a hardware related error , though cannot be sure about that. We changed main server to another machine and for now everything is smooth.
    Also we plan to update to 3.3 this week , once we decide how to be with the different whitepoint (i know about script commands , though need to coordinate that with project manager) , so we will check how that works also.
    Available for remote work.
    My LinkedIn: https://www.linkedin.com/in/olegbudeanu/

    Comment


    • #17
      It could be a hardware issue for sure but since the scene uses 25GB on the workstation and some of the machines has less memory that might be also the reason for dropping spawners.
      You could easily find out if that is the case if you optimize the scene to use about 20GB and run the same test.
      Svetlozar Draganov | Senior Manager 3D Support | contact us
      Chaos & Enscape & Cylindo are now one!

      Comment


      • #18
        Yeah that's the thing i want to try when we will encounter that next time. For now we updated to 3.30, for now it looks fine.
        Available for remote work.
        My LinkedIn: https://www.linkedin.com/in/olegbudeanu/

        Comment


        • #19
          Glad to hear that with 3.30.03 it works fine so far.
          Keep us posted if the issue occurs again.
          Svetlozar Draganov | Senior Manager 3D Support | contact us
          Chaos & Enscape & Cylindo are now one!

          Comment

          Working...
          X