[bjorn.syse]

Hi,

Lately, I've experienced very slow read times of my rhino files. Also something simple as a copy paste of a single curve can take minutes. I'm trying to troubleshoot this and was curious about an error message I got in the command prompt when pasting an object:

Maxwell: warning: document-read unsuccessful (caller=ReadDocument).

I wonder if it could be related to what I'm experiencing.

I'm not using Maxwell for this project, and Rhino render is set as the Renderer - so It surprised me It wanted something to do with my files. There are no maxwell materials in the file.

Best regards

- Björn

[kami]

Hi Björn
I've had this experience too. And it still happens from time to time, when I would paste something, that rhino gets stuck for some minutes.
But I wasn't able to see under which conditions it happens.
Cheers, Christoph

[JDHill]

I can't comment on the slowdown issue without knowing more, but I can tell you three things related to your questions:

1. Using copy/paste is similar to saving selected objects to a file, then Importing that file.
2. The warning means that some data is corrupt in some file that's being read.
3. If a file has ever been saved with a plugin loaded, that plugin asked to read that document thereafter.

It does not matter if you have no materials in the document you're importing; it contains other data (even if just a file version marker) that has been written by the plugin, which Rhino does not know how to read, but which it knows the plugin can read. So, if the plugin is installed, Rhino will ask the plugin to do so, and will even attempt to load the plugin, if previously unloaded, for the purpose of doing so. And regardless if the plugin is current renderer, it will be asked to save its data whenever you save a document.

Since this is the way things work, the plugin provides two commands specifically designed to help you manage it: Maxwell_SaveWithoutMaxwellData and Maxwell_SaveAsWithoutMaxwellData. What happens during these commands is: a temporary flag is set, instructing the plugin to refuse to save data, the corresponding Rhino save commands are executed, then the flag is cleared. This is the only way, short of 1) uninstalling the plugin, b) load-protecting the plugin, or c) using -SaveAs SavePlugInData=No (this will do similar, but applying to all plugins), to save a Rhino file that will not contain data written by the plugin.

As to why the document-read error occurs, I cannot speculate; if you can reproduce it by saving to a file the selection you otherwise would have copy/pasted, and then Importing that file, I would like to see the file.