Announcement

Collapse
No announcement yet.

Constant high CPU usage when show mesh

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

  • Constant high CPU usage when show mesh

    Almost unusable. Max19 up3. 27th december phx
    I just can't seem to trust myself
    So what chance does that leave, for anyone else?
    ---------------------------------------------------------
    CG Artist

  • #2
    Does not reproduce here with a simple scene. Can you send your scene over?
    Svetlin Nikolov, Ex Phoenix team lead

    Comment


    • #3
      yeah, tried to repro - and it is very scene specific. i hate 3dsmax....

      sent

      edit

      you wouldn't believe - import to new scene, then save (no hi cpu usage), then delete that new scene with old one - and now that old scene doesn't use cpu all the time. What the hell autodesk is happening.....

      edit

      reproduced again:
      mesh preview on
      goto frame 12
      goto frame 1

      hi cpu and no mesh seen at all.

      edit

      even simplier

      mesh preview on
      frame1
      profit
      Last edited by Paul Oblomov; 28-12-2018, 10:04 AM.
      I just can't seem to trust myself
      So what chance does that leave, for anyone else?
      ---------------------------------------------------------
      CG Artist

      Comment


      • #4
        Got the scene, simulating now... first impressions: the grid is 100M voxels. Note that the mesh preview does not have reduction, so that would be a very solid polygon amount in the viewport.
        Svetlin Nikolov, Ex Phoenix team lead

        Comment


        • #5
          No. It works perfectly fine, when using merged scene. I can send .aur frame too. Just forgot, it is -100 frames

          I had same shite in maya on different machine. Well, almost...
          I just can't seem to trust myself
          So what chance does that leave, for anyone else?
          ---------------------------------------------------------
          CG Artist

          Comment


          • #6
            Yes, got it! For now you can work around the problem if you go to Time Configuration, set Time Display to FRAME:TICKS, and make sure Start Time is an exact frame - it should say 1:8 right now, and changing it to 1:0 should work around the problem until the fix goes into the nightlies.

            Cheers!
            Svetlin Nikolov, Ex Phoenix team lead

            Comment

            Working...
            X