CINEVERSITY

    Maxon Logo
    • Login
    • Search
    • Recent
    • Popular
    • Users
    • Groups

    Node (Material) Editor Laggy When Using Textures from Asset Browser

    Question & Answers
    asset browser slow laggy
    2
    4
    300
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • GregBollella
      GregBollella last edited by Dr. Sassi

      If I have a texture node with a texture from the asset browser the node editor is laggy. I have to click on a node and wait some seconds before the node is highlighted and then try to move it. Sometimes it doesn't move for a while. If the texture node references a file on my disk then the node editor is snappy.

      I updated the indices on databases that would allow me.

      Any suggestions for speeding up access to asset browser media?

      Thanks,
      Greg

      1 Reply Last reply Reply Quote
      • Dr. Sassi
        Dr. Sassi last edited by

        Hi Greg,

        This is nothing that I can solve. Either it is a tech support question, then:
        https://www.maxon.net/en/support-center
        Or, it is a "Share Your Idea!" case.

        When I need a texture from the Asset Manager, I drag it into the Material Manager, and from there, I copy the texture path into the node. I have no idea if that helps on your side, but perhaps worth a try.

        For me, it is more likely to have all textures in my project tex folder. Things change, and reconnecting in a year or two projects is not fun. So, I'm the last person to ask about any appreciation of cloud or library stuff; I love to have it as an individual package.

        Could your disk be in sleep mode when you try to work on it, which is just a guess? Is it an HD or SDD?(Not a question that I need an answer for, just for you to gain data)

        All the best

        Dr. Sassi Sassmannshausen Ph.D.
        Senior Trainer, Maxon Master Trainer, L&D - Strategist
        Cinema 4D mentor since 2004, Member of VES, DCS.

        GregBollella 1 Reply Last reply Reply Quote
        • GregBollella
          GregBollella @Dr. Sassi last edited by

          @Dr-Sassi Thanks Dr. Sassi!

          Yes, I tend toward keeping all my textures in ../Geometry/tex as it seems to be the most responsive. However, given all the new materials in the Asset Browser and their multiple uses across many projects it does make sense to have only one copy of the texture (especially as we head toward 16K) on disk. I will ask support.

          Cheers,
          Greg

          1 Reply Last reply Reply Quote
          • Dr. Sassi
            Dr. Sassi last edited by

            Hi Greg,

            Yes, 16K will have an impact, especially in 16bit or float. Many years ago, a real problem to load, especially when an HDRI had to work as background as well, then perhaps more than 32-64K to get sufficient data in the camera view. Which sometimes leads to manually resampling the image for what is needed.

            I will run some tests with the current release and then file a report. Fingers crossed, it will help.

            Thanks for your patience.

            All the best

            Dr. Sassi Sassmannshausen Ph.D.
            Senior Trainer, Maxon Master Trainer, L&D - Strategist
            Cinema 4D mentor since 2004, Member of VES, DCS.

            1 Reply Last reply Reply Quote
            • First post
              Last post