*save as* and *Bake to Rhino* data issues, 'baked' model not refreshing in Rh PO:: "model's kinda lost"

Hi yeah so as above:
Looks like every time I’ve ‘saved as’ the PO data migrates with the new model rather than duplicating it?
note the file size difference between mainv2 and fork_v3, v3 has way less actual stuff in the RH file:
And it only has a ‘baked’ PO model from GH.
@mostapha I can message you both of these files for TS purposes if needed ofcourse

Also the baked model:
(Cant seem to figure out how to get the PO RH manager to populate?)

This is an interesting one for @mingbo to have a look at. Can you provide more information about how you created V3 from V2? Is it only a simple SaveAs?

V3 was baked from v2 via GH bake PO model; via internalizing in the _from_RH PO model compo insert spaghetti end of spaghetti–>PO model compo: do bake, the files are contained in the ‘vid about issue’ message dropbox link.
#I_break_stuff_good :sweat_smile:

1 Like

@mingbo hello! I just wanted to see where this all landed if you happened to have time to take a look

Hi @tfedyna, sorry for the late reply. I am trying to understand how to recreate this issue on my side:

  1. Are you using GH plugin to read a model from Rhino and bake it back to Rhino?

  2. When I try to use “Save As” the model in Rhino and open it again with a new instance of Rhino. Everything seem working correctly to me.

  3. If I am understanding correctly what you did, then there might be an issue with our GH plugin. @antonellodinunzio might be able to have a better understanding than me. @antonellodinunzio please let me know if you have any insights?

So I baked the model in this file as I needed to do some major simplification to pipe it into WUFI Passive,
The model I baked; while being ID’d as a PO model:
Refresh button etc: it won’t read in all the room names and data on the rhino side nor will the PO Model component read the model into grasshopper again

Hi @tfedyna, until @antonellodinunzio has time to look into it, you could try to use GH to save HBJson file and then import it to Rhino, instead of baking it back to Rhino. This should be able to help you keep working on this model.

1 Like

To add to @mingbo’s comment - do you delete the original rooms before baking back the new ones? Currently, the Grasshopper bake component doesn’t sync the existing objects. It creates new ones every time.

1 Like

I fortunately have numerous copies of the model, so alls well: I found a “Checkpoint” I saved and stashed in a folder so I’m on track.

AHHH That’s good to know about the current Gh bake:
I did not delete the OG rooms fortunately; tho I did internalize and bake to a clean Rhino file