[znouza]

Hi,

I think I've isolated the cause. It has to do with materials being applied by Layer.

Try opening Rhino and unloading Rhinoll. Open a scene. Load new Rhinoll. Change all objects so that materials are applied by Plug-in and not Layer.

negative. I'm not using material assigned by layer but all by plug-in... IMHO it's caused by changed internal structure of plugin 'registry' in scene file, so the new rhinoll tried to read something what never exists.

[Frances]

Were you able to open any of the files with the new plug-in?

There are some I can open and render fine and some I have to unload Rhinoll first and reassign materials.

[znouza]

Were you able to open any of the files with the new plug-in?

There are some I can open and render fine and some I have to unload Rhinoll first and reassign materials.

I guess you can open fine these scene files you never processed in Rhinoll before. As for myself - any scene file, containing something from previous rhinoll causes the 'crash' as described.

[Frances]

Were you able to open any of the files with the new plug-in?

There are some I can open and render fine and some I have to unload Rhinoll first and reassign materials.

I guess you can open fine these scene files you never processed in Rhinoll before. As for myself - any scene file, containing something from previous rhinoll causes the 'crash' as described.

No, I mean there are some scenes I've used Rhinoll 0.5.1 with that have no problem with 0.5.5. So far, they are ones that have a single diffuse material applied to all objects for massing studies, etc. Others do have a problem and take some finessing to get them to open and render.

[znouza]

Sorry i must adviced it in the announcement of the last version.
Like have you seen the new version has many new features, and the materials are almost new, in their internal implementation, so this cause that the actual version is incompatible with the last version.
The message about chunk error is due to that the plugin now stores more information than the previous version, in fact, the new materials causes some inestability with old scenes.
Thanks to Thomas for his advice, use the save as command with the purge plugin information: "-saveAs" --> pluginData=No
So you can reset your plugin info and use the new one.
Sorry for the annoying incompatibility.

isn't one solution to make correct version number to rhinoll (now 0.5.5 identifies itself as 0.5.1) and perform model loading WITHOUT loading or processing plugin-dependant data if version mismatch? with some alert or infomation message...

[Frances]

Call me dense, but I don't see an option for purging plug-in data in the SaveAs dialog.

[znouza]

Call me dense, but I don't see an option for purging plug-in data in the SaveAs dialog.

in the command line type "-saveas" (with the "-")

[Thomas An.]

Seems like this option should be added to the menu command, but I guess that's one for the Rhino NG.

Yeah, it seams it should be included in the GUI dialogue.
The only thing... it is destructive and should be used sparingly. We not only loose Rhinoll data from the file, but also other plugins (Brazil, Rhinoman the whole works).

[hyltom]

Thanks a lot for this update Pablo.


Hyltom

[Thomas An.]

I have made a little change in the rhinoll version, only correct the plugin version in the about window, change the SM with GMT, and allow to use negative GMT values.
The version is the same, it's only to avoid some misunderstandings.
I think that along this day this new version will be uploaded to the web server.

Thank you

[iker]

Pablo ,are you married?