WIP - setting User Text on Attributed Block Prior to baking and preview?

Continuing the discussion from WIP - Setting User Text On Model Objects Prior To Baking?:

To expand on the above discussion, in the latest wip, the User Text now works prior to baking as expected. But I tested to assign the User Text on transformed block definitions or existing block instances, and the user text fixed to block attribute could not be modified by bake/update, and also it could not be previewed with a new-assigned attribute.

@AndyPayne @michaelvollrath Have you had any concentration on this?

Please see the screenshots below:

[block with attribute “testKEY” and default value “1”]

[test step - 1, 2, 3]

[test step - 4]

Thank you all for your time!

Would it be possible to include a simple Rhino and Grasshopper file so I can replicate what you’re seeing? Thanks.

@AndyPayne Sorry for the late reply, I have tested the latest beta version, and it seems not updated for this, and I also found another issue. Please see below:

#1 it seems to get wrong when display in gh that will always display the last created block attritbutes.

#2 blockinstance in gh will not display the modified attributes
#3 Attributes of baked blockinstance will unexpectedly reset to default value.
#4 baked block instance will out of tracking by the bake component, can be repeated with the second cllick and it turned yellow for warning.


Here are the testing files if needed:
test for blocks.gh (13.7 KB)
TEST.3dm (2.0 MB)

Hi
@kike @Gijs Are these possible to be fixed in the next update? :grin:

@weekenlwk,

#3 and #4 will be on next RC, the other two are more tricky.

Thanks for the quick reply. :coffee:This could be very cool when finished.

Hi @kike
#1 ~ #3 seem not fixed in the latest Beta, will there be any updates on the upcoming Beta? :grin:

@weekenlwk,

The issue with the current wiring is that you are baking a new transformed block instance that do not have any User Text. Plain geometry do not have User Text, only Objects do have, so if you want to chain several changes on an object you have to do something like this.

  1. Applies user-text
  2. Applies new transformed geometry
  3. Baker make your changes persistent on the document.

Does it work as you expect if you connect the Object to the baker like this?

1 Like

@kike No exactly in the latest Beta. Even though I just modified the referenced instance without any transformation, it will always reset to the default. :sweat_smile:

hi @kike ,

In 8.4 RC, I still get the reset default value when baking.

Are the issues still on track, or is there any news?

This is a very important procedure in AEC parametric design that dynamically changes the attributes relevantly.

Thanks!