DIVA components disappear from canvas upon re-open...

Replies to This Discussion

Permalink Reply by Andy Payne on February 6, 2012 at 6:28pm

I'm not completely sure... but it looks like one (or more) of the DIVA components isn't properly deserializing itself.  Thus, when the definition is re-opened, some of the chunks are missing (upon reserialization).  Unfortunately (if this is the case), there's not much that can be done except to go into the code and re-work this portion so that everything is properly deserialized upon saving.  Perhaps the developers could issue a quick patch to solve the problem.  Or maybe David has a better solution.

Permalink Reply by Jeff Niemasz on February 7, 2012 at 9:42am

Hi Marc,

This is a known issue with only the legend component and will be fixed for the DIVA 2.0 release. I got all the errors you describe when I try to open your definition, but I am not able to repeat the error if I add the definitions and save them again. If I put all the DIVA components into your definition, then save and open it again they all open (except the legend component- whose function can be created on its own from some native grasshopper components). I am running 0.8.0066 with Rhino 4.0 SR 9. Please confirm you are using these versions and try opening the attached definition.

Jeff

Attachments:

• DivaAnalysis4_JN.gh, 90 KB

Permalink Reply by Marc Syp on February 7, 2012 at 10:03am

Hm.  Thanks for testing.  I opened your file in both Rhino 5 (64-bit) and Rhino 4 (SR9) and I get some strange new errors (see below).  All of the components are missing except for the solar tools.  I am starting to wonder if I have some sort of mismatch between my GHA file and my Diva version, though I'm not sure that would cause these kinds of problems.

Incidentally, I tried creating a brand new file and I get the same results.  I cannot save anything with DIVA components in them, they disappear every time.  :(

Speaking of 2.0, do you happen to know when that will be released?

Thanks,

Marc

info: Plugin version: 0.8.0066
info: Plugin version: 0.8.0066
info: Object list read
info: Plugin version: 0.8.0066
info: Object list read
info: Plugin version: 0.8.0066
info: Object list read
info: Plugin version: 0.8.0066
info: Object list read
info: Plugin version: 0.8.0066
info: Object list read
info: Plugin version: 0.8.0066
info: Object list read
info: Plugin version: 0.8.0066
info: Object list read
error: Component DIVA Daylight Analysis for GH {4ec4ef63-a2e3-4501-891c-dc1107bdd94d} failed to deserialize itself: Method not found: 'Boolean Grasshopper.Kernel.GH_ComponentParamServer.ReadParameterTypeData(GH_IO.Serialization.GH_IReader)'.

error: Component Material {842f969a-3d16-4b32-9aaf-d996bd25181a} failed to deserialize itself: Method not found: 'Boolean Grasshopper.Kernel.GH_ComponentParamServer.ReadParameterTypeData(GH_IO.Serialization.GH_IReader)'.

error: Component Construction Assembly {2f4beddf-fda7-4852-9820-c36101cd316d} failed to deserialize itself: Method not found: 'Boolean Grasshopper.Kernel.GH_ComponentParamServer.ReadParameterTypeData(GH_IO.Serialization.GH_IReader)'.

error: Component Fixed Shade {cc5c1712-3cb4-4e91-b322-ebc050a75c3f} failed to deserialize itself: Method not found: 'Boolean Grasshopper.Kernel.GH_ComponentParamServer.ReadParameterTypeData(GH_IO.Serialization.GH_IReader)'.

error: Component Read Saved Thermal Results {b71b827f-7e12-42a8-a44a-a9ebb1da1596} failed to deserialize itself: Method not found: 'Boolean Grasshopper.Kernel.GH_ComponentParamServer.ReadParameterTypeData(GH_IO.Serialization.GH_IReader)'.

error: Component Viper: Thermal Analysis for GH {8a8fd0f2-dcd8-4c3c-83dd-d74baf8dcaba} failed

Permalink Reply by David Rutten on February 7, 2012 at 10:13am

ReadParameterTypeData() method has been removed. Apologies, I didn't realise anyone was actually using it.

Jeff, you get compiler errors regarding these when you try to compile DIVA against the latest Grasshopper versions right? Why exactly were you calling ReadParameterTypeData()? Or am I totally confused?

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Jeff Niemasz on February 9, 2012 at 10:47am

Hi Marc, We haven't been able to replicate this error with the current version of DIVA and the latest release of grasshopper, so I am having trouble tracking down the problem. I can generate a similar error if I open a file saved from an earlier version of DIVA, before David changed the serialization methods (I think this was something like 0.8.005x). Did you update the latest DIVA assembly to both your rhino 5.0 and 4.0 grasshopper components folder? Maybe you are flipping between two different versions? We will try making keeping track of the versions in the future releases. Let me know if this works.

Jeff

Permalink Reply by Marc Syp on February 9, 2012 at 12:44pm

Hmm... I'm not sure.  I can say that I get the error in both Rhino 4 and Rhino 5.  I thought that I only had GHA files in one location feeding both Rhino/Grasshoppers.   My DIVA component is dated 10/24/2011 3:57pm.  Can't find another one.  (It's not in my Rhino 4 Plug-ins/Grasshopper/Components folder...)

Any ideas?

Thanks,
Marc

 

Permalink Reply by Marc Syp on February 9, 2012 at 1:06pm

Ok, problem solved.

I downloaded the latest version (1.901), installed over top of the existing installation, and replaced with the newer GHA (dated december 2011).  Had to rebuild my file but I'm not getting deserialization errors anymore.

Thanks for the help... 

Marc