Issue: When trying to access the file path of a linked block from a file that has been downloaded from an external source, the file path will be a location on the machine of the person who created that file. This can be fixed by opening the Rhino file and saving it. But it's an extra step that's unintuitive.
Solution: If the file path can't be found locally, comb through sub-directories to locate the linked block file. When found, adjust the 'source_archive' variable accordingly. This is a simplified implementation of how Rhino handles the finding of linked files. https://wiki.mcneel.com/rhino/rhinov5status_filefinding
Issue: When trying to access the file path of a linked block from a file that has been downloaded from an external source, the file path will be a location on the machine of the person who created that file. This can be fixed by opening the Rhino file and saving it. But it's an extra step that's unintuitive.
Solution: If the file path can't be found locally, comb through sub-directories to locate the linked block file. When found, adjust the 'source_archive' variable accordingly. This is a simplified implementation of how Rhino handles the finding of linked files. https://wiki.mcneel.com/rhino/rhinov5status_filefinding