Rhino 8 Feature: Annotations and Hatches in GH1

In that case it is my understanding that that component does only query annotation styles in Rhino or GH created annotation styles that have been baked/cached into Rhino from within GH.

However, you can define annotation styles within GH, never bake them, and connect their output to other components that get baked and this will result in your custom dimension styles or whatever showing up properly in Rhino still and will then actually populate the custom annotation style into the Rhino model and at that point it can be referenced since it has been baked/cached in the flow of logic at the end.

1 Like

I think you’re all running up against the exact problem that we’ll be facing when adding support for these new data types (at least the ones that rely on a document). As mentioned, typically an annotation has a style this is assigned from the document. Since this doesn’t exist in compute, this will be a problem. It’s possible that Michael is correct in that you might be able to generate your own custom style all within GH and assign that and it could work, but I’m not 100% sure. It would need to be tested. @Kike and I have been discussing this topic as well and we may have some ideas on how to get around this issue but it will require some typing. Unfortunately I don’t have a lot of answers currently, but I will report back once I’m able to fully jump into this issue.

1 Like

It depends on if you care about the dependencies. Curves are currently passed to compute, but you don’t know what linetype it was using. The same goes for many of these items where interdependencies exist.

1 Like

@AndyPayne @michaelvollrath @stevebaer Thanks guys! This is exactly what I’m trying to accomplish. Basically I want to use rhino.compute/resthopper and these new components to generate superb 2D drawings server side. The geometric/textual output could then be displayed elsewhere (for example in web based viewers or PDFs)

I’ll continue to investigate from my end as well. Please do keep me in the loop! Really excited about this!

1 Like

This is also something I’m very much interested and working towards. So far I’ve been focusing more on the algorithm side of automating AEC construction documents (A LOT to cover in this area) but deploying results and outputs via web interface is a likely next step and I’ve been researching workflows to that end.

A colleague just introduced me to Rhinoanywhere and just now I realized you worked on that. I’ll definitely be checking that out when I get a chance, thanks for sharing!

2 Likes

@michaelvollrath That’s great - sounds like we have some common goals then. Let’s keep in touch!

And thanks! It was a really fun hack to work on :slight_smile:

1 Like

Will hatches have a background colour? So a diagonal hatch will have a white background for example, rather than the current workaround of having a diagonal hatch on top of a solid hatch coloured white. It’s super fiddly having to work with 2 hatches and being able to merge it together like how Sketchup has done for years would be fantastic.

Hi Marina -

That’d be the Bc input here, no?

image

-wim

1 Like

Hi, I just downloaded the Annotations.gh file to try. Upon opening in GH, the Curve Preview component popped up the following error: ā€œ1. Data conversion failed from Number to Model Linetypeā€. What should I do about this?
FYI, I am new to Rhino 8 and GH in general.
Thanks for the help!


1 Like

I think from the screenshot you posted, you were talking about the ā€œSimple Dimensioned Partā€ example. I searched and couldn’t find that file attached anywhere in this thread, but I did have a copy of it on my machine. All that was needed was to replace the Number Parameter with a Model Linetype component. I’ve swapped out those components and you can download the fixed model here.
SimpleDimensionedPart - Millimeters.3dm (47.5 KB)
SimpleDimensionedPart.gh (31.0 KB)

Sorry @AndyPayne , I should have included the link.
Go to the bottom of the page:

The linetype component you added has worked for displaying the plate in this example (rectangle w/ 3 holes), but perhaps not for creating these shapes? I am not able to bake the whole thing, plate and annotations for exporting to another program. Can you help with that? Much thanks!


To bake things into the document, you can use the new Content Cache component. Simply pass whatever content you want to push to the document into the C-input and then set the P-input to True to bake every time you make a change. Like this.


Annotations_Bake.gh (29.0 KB)

3 Likes

Great, thank you @AndyPayne !

@AndyPayne, it would be helpful to add an output for obtaining hatch geometry in the Model Hatch component. @andheum incorporated this into the CreateHatch component for Human, and it was very useful. Also related to this, the Explode Object component outputs a brep from any hatch pattern, yet when a hatch is exploded in Rhino it creates the object geometry used to define the hatch. Or maybe I am misunderstanding why a brep is the result even if the hatch is composed of lines? Thanks for the new display components tab for Rhino 8.

Hi @John_Leahy , if I recall correctly this is that the Boundary Curve (Bc) output is for. Right click on the Model Hatch component and show all variables/parameters.

Unless of course you mean the actual .pat lines for instance like the dots and triangles that make up a concrete hatch or the curved wavy lines that may make up a wood hatch. Is that what you mean?

Thanks for the suggestion, @michaelvollrath, but I am not referring to the Boundary. I mean the objects of the hatch pattern from the .pat file. If those lines, shapes, etc. could be an output for the Model Hatch component, or if the Explode Object component could release those objects from the hatch.

1 Like

I see, that makes sense, thanks for clarifying @John_Leahy

@John_Leahy Does the explode component not return the lines of the hatch pattern? If not, can you post a simple definition that does not work correctly? In my test, it appears to be working as expected.

1 Like

@AndyPayne My apologies for not posting a screen shot earlier.

When the Hatch Pattern input is set to Grid 60, shouldn’t Explode Object output the lines/curves created by Model Hatch? Model Brep would be accurate if the Hatch Pattern had been defined as Solid, so perhaps there is an error with Model Hatch? Possibly the Background and Fill Style inputs/outputs are not actually empty? If not, then why must a hatch be baked first to Rhino for Explode Object to function properly?

My suggestion was that it might be helpful to include an output parameter for Hatch Geometry between Hatch and Hatch Pattern since many other parameters are passed through the Model Hatch component. This also makes me wonder if Show Boundary is actually useful since the input parameter for Boundary could just be used.

I have tremendous respect for the work you’ve put into creating these very useful components! Thanks!!

@John_Leahy Thanks for reporting this. I found the bug and this will be fixed in the next 8.6 release (next week).

2 Likes