Internalized data not serialized on next open

Hey everyone,

I had a large number of planes that I internalized (i was recording them as they were created and I wanted to save them all for later). So I internalized them (there were several thousand).

When i opened the file again none of them showed up and I got an error message saying that they could not serialize properly.

Anyone else have this problem?

-Brian

Replies to This Discussion

Permalink Reply by Mateusz Zwierzycki on May 10, 2012 at 1:18pm

From my own experience - only points and num/ints internalize properly...

Permalink Reply by Brian Harms on May 10, 2012 at 1:24pm

Hey Mateusz,

I've done several meshes before and that seems to work well too. But yeah Im not sure about planes. Right when I internalized them it seemed to work properly (they would turn preview-green when clicked).

Permalink Reply by Marios Tsiliakos on May 10, 2012 at 2:45pm

Brian,

Same here. happened to me a long time ago. Did you get the same error ( see discussion)??? I also used meshes, not many of them though..

Permalink Reply by Brian Harms on May 10, 2012 at 2:49pm

Hey Marios,

no it was actually a different error ( I should have saved it but I didnt). It just said the objects could not be read and could not serialize properly.

I actually have had good results with internalizing meshes. I made a set of inverse kinematic tools for Staubli robot arms and all of the 3d models of the robots are internalized meshes (and they all work great).

I dont think ive ever tried to internalize planes before. I'll try to internalize a few and see how it goes when I reopen the file. At first I thought it might have been an issue because of the number of planes i was internalizing, but I'm not sure.

EDIT:

I just tried internalizing 100 xz planes and it worked fine when i closed down rhino/gh and reopened it again.

The planes I made before (when i got the error) all had unique orientations and there were probably 15000 total. Maybe just too much to handle?

Permalink Reply by Marios Tsiliakos on May 10, 2012 at 2:54pm

I only got this error once or twice. never had a problem with any kind of geometry since then. But I couldn't find neither the source of the problem nor a repeating pattern. some things are meant to be unanswered..

Permalink Reply by Brian Harms on May 10, 2012 at 2:58pm

Here is the error I got:

Component Plane {4f8984c4-7c7a-4d69-b0a2-183cbb330d20} failed to deserialize itself: Object reference not set to an instance of an object.

Component Plane {4f8984c4-7c7a-4d69-b0a2-183cbb330d20} failed to deserialize itself: Object reference not set to an instance of an object.

Component Plane {4f8984c4-7c7a-4d69-b0a2-183cbb330d20} failed to deserialize itself: Object reference not set to an instance of an object.

Component Plane {4f8984c4-7c7a-4d69-b0a2-183cbb330d20} failed to deserialize itself: Object reference not set to an instance of an object.

I'd actually really like to get these planes if possible - I can't really recreate them again.

Maybe David will come to my rescue? :)

Permalink Reply by Mateusz Zwierzycki on May 11, 2012 at 4:12am

Light up the grasshopper sign in the sky ! *

*batman style

Permalink Reply by Brian Harms on May 11, 2012 at 4:22am