Announcement

Collapse
No announcement yet.

Copy and paste geometry causes HUGE delays. Please help!

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

  • Copy and paste geometry causes HUGE delays. Please help!

    If I copy and paste ANY geometry -- even a single line -- I get a 10 second delay. The file is under 25 MB, so it's not a memory issue

    I suspect it is a V-Ray bug because I see this info on my command line:
    _CopyToClipboard
    _Paste

    V-Ray data version of "C:\Users\David\AppData\Local\Temp\rh$6C14.tmp ": -1


    ​Again, there is no material on the single line that I did my copy and paste test.

    For larger geometry with materials, the system lock-up delays can be 20 seconds or more. This makes the system almost unusable.

    BTW / In the past, I had a delay issue involving new material copies being created when I copied geometry. it was fixed with the command RenderPasteConflictOption > DiscardIncoming​. This new issue is different. No extra materials are created.

    SYSTEM
    [latest] Windows 11 pro with 32 GB of RAM
    [latest] V-Ray for Rhino 8 6.20.06
    [latest] Rhino 8.13
    EDIT / just updated
    Chaos License Server 6.20.0, no change
    Last edited by schultzeworks; 04-11-2024, 11:17 AM.

  • #2
    Hi, the warning is removed in V-Ray 7, as other people noticed its redundancy. The delay however is interesting. Recently I had similar issue with a page layout geometry that was a V-Ray proxy in the 3d model. It turned out that when Rhino is producing the page layout graphics ot explodes the proxy geometry, generated by V-Ray into individual curves, each tagged as being the V-Ray proxy it come from. That caused reading the same proxy file many times over. That as well is fixed in V-Ray 7. Are you by chance, falling under this case ?

    Comment


    • #3
      Thanks for the reply.

      No, I am not using any layout pages.
      No, I am not using any proxies.

      Comment


      • #4
        ok, any chance you share a file in private ?

        Comment


        • #5
          Yes. Here is a link to a g-drive downnload. I have zipped the Rhino file and all texture maps into a single folder.
          https://drive.google.com/file/d/1yga...ew?usp=sharing
          Thank you!

          NOTE : If you have a preferred method for sending files, I didn't see it anywhere.
          Last edited by schultzeworks; 07-11-2024, 09:45 AM.

          Comment


          • #6
            I've checked your file. Indeed there is a delay when copying (not pasting though).
            If you disable V-Ray and perform the same action - you will observe the delay as well. Thus it is not V-Ray itself, at least not the V-Ray run-time for sure.
            I used the debugger to check up the call stack at the time of the delay, and it is mostly Rhino's OpenImageIO implementation. That is there is some image processing going on on a background.
            Furthermore when you copy, but not paste, and close Rhino, you will see this message:
            Click image for larger version

Name:	image.png
Views:	35
Size:	11.2 KB
ID:	1219902
            This is very odd, for having copied a single line geometry.
            I inspected the clipboard - and indeed Rhino puts ~1MB and geometry and 5 MB of imagery on the clipboard:
            Click image for larger version

Name:	image.png
Views:	31
Size:	6.9 KB
ID:	1219903
            The image you see (CF_DIB) is the snapshot of the viewport.
            The bigger viewport the larger the image - thus you can reduce the size of what Rhino puts on the clipboard by having smaller viewports.
            This is not very practical, but an useful knowledge.

            When you copy something via Ctrl+C, what Rhino does it to make a new document that contains only the copied stuff. However that also includes among other things the full RDK table (materials, textures and environments)
            Usually that is OK, since the RDK is just XML "file". And indeed those 1MB is mostly comprised of the RDK table. However, the shape you copied doesn't have any materials assigned !?
            And yet Rhino does copy the entire RDK alongside it. And it does that several times. The reason for that is that it is not known in advance where you're gonna paste it. That's why Rhino puts the same data in several different formats on the clipboard.
            it even writes out a .dwg file for AutoCAD (on the disk!).

            No onto the real problem.
            Putting all that on the clipboard is not really a problem - after all the clipboard is just RAM and that is fast.
            The problem is that Rhino does some image processing. I don't know what and why, but it does, and that takes time.
            That's why CAD software usually have in-built copy command. That does not inflict putting any data to the clipboard, transforming it into several formats.
            This is true for AutoCAD, Solidworks, Catia, you name it, so does Rhino.

            Just use the in-build Copy command, instead of CopyToClipboard
            You will save a lot of time

            Comment


            • #7
              Ok,this sounds like an excellent discovery! I will share this with the Rhino tech staff, since this seems VERY important. I've never seen this before until recently.

              My first step will be to make an alias for CTRL+C to be Copy instead of CopyToClipboard.

              I'll report back with an update.

              EDIT 1 : Things are improved, but the command Edit > Copy invokes an extra step; it asks you for starting and ending position.
              I'm going to ask the Rhino tech staff for suggestions.

              EDIT 2 : The tech support at McNeel suggested a keyboard shortcut that does the copy AND paste with a single command with no delay. Specifically, it avoids the CopyToClipBoard command that is the culprit.
              CTRL + C should be defined as follows: _Copy _Pause _InPlace
              There is a space before the second and third underscore, but not the first.
              Last edited by schultzeworks; 09-11-2024, 01:20 PM.

              Comment

              Working...
              X