Bug in Lunchbox 'Object Save'

When I have multiple Objects plugged into "Object Save" and save as an .obj everything works as expected. But when I also plug in objColour with a different value for each object, then the component will actually save as many times as there are objects. I had to force quit Rhino to get it to stop. I then tried with a smaller number and it was clear it was somehow getting confused and actually saving once for every number of objects.

When I use the ‘Object Bake’ component with multiple objects and multiple colours it works as expected and bakes once.

I am attaching a small patch to illustrate the problem. I am using Rhino 5 on Windows 7, GH is version 0.9.0076, Lunchbox is version LunchBox v.2015.7.20

Also I would love to be able to somehow change the settings it is using when saving. I am using it to export geometry animations from grasshopper, exporting each frame as an .obj file, but would like to change some of the settings for .obj saving it is using, like whether or not to group things together and saving materials. It’s a great workflow I have been testing and works really well for animating things in GH and then being able to have the complete geometry animation in something like Cinema4D for camera and rendering. I will make a tutorial about that soon, but first need the objColor to work as expected.

Attachments:

lunchbox_bug.gh, 8 KB

Replies to This Discussion

Permalink Reply by Nathan Miller on March 21, 2016 at 9:57pm

Hello Armin,

In all honesty, the Save tool needs to be rethought and I am sorry to hear it is giving you so much trouble. It was originally built to bake one object at a time and I haven't touched it in years. I am planning on creating a new 3DM authoring toolkit so automating Rhino 3DM files will be much easier as opposed to this command-line hack.

-Nate

Permalink Reply by Armin Seltz on April 5, 2016 at 10:09am

Hey Nathan,

Thanks for your reply. I was away for a while and finally got back to GH. And what do you know the Save component is giving me troubles again. So now it just kind of refuses to work, giving me a "Solution exception: Object reference not set to an instance of an object" error all the time. Not sure what I did different before, but will investigate.

Also we have a different computer, which has Rhino installed in German on it. So of course there it doesn't work at all, because for some inexplicable reason a german Rhino doesn't understand any of the english commands in the command line.

If you know of any alternatives before a rewrite, please let me know.

Permalink Reply by ng5 Alex on April 5, 2016 at 10:32am

Hello Armin,

not quite sure why, but one workaround that works for me (not all the times) is to put an appropriate container component just before the bake or save Lunchbox components.

best

alex

RSS