algorithmic modeling for Rhino
I am just struggle to bake Ladybug (visualize weather data components) text output, as most of the components text baked as mesh in rhino. the only component that bake text as text is the "3D chart" one.
I just want to bake all charts text as text.
Replies are closed for this discussion.
How do you bake the results? If you use bakeIt it should bake them as text. Otherwise if you're baking it by right-click select bake you need to connect text outputs (not the meshed ones) to a collector component and bake them as text.
I am trying to bake the "PsychChart" but no (BakeIt) input and if I try by right-click is always end as mesh. the output (chartCurvesAndTxt) are curves and meshes.
This is something that is currently under development and should be complete by the next stable release:
The BakeIt options will be fully functional (with no meshes and only text, curves, and hatches) and will support a workflow that exports the graphics to vector-based formats like PDFs and Illustrator.
We have to use meshes for text now because of some limitations in the Rhinocommon SDK and, had we not needed to do so many work-arounds to get dynamically interactive text, this all probably would have been done a lot sooner.
I will post here once I put in the fully functional BakeIt option on the psych chart.
I'd like to throw my 50 cents in the jar of proper text for baked objects. I'd also like to ask a tiny winy question about visualization and -ViewCapturetoFile command in Rhino. I didn't want to create a new discussion for this problem because I felt like it have been answered somewhere on the forum but I couldn't get the right words to find it.
Anyway, my question is about how rhino exports .png files with the transparent background and messes up the colors and how to fix it. I don't bake the results, I like to ViewCapture them, is it the wrong way to go?
First image was loaded directly here and the one below was opened with native windows app, snipped and loaded here (app couldn't recognize the transparency, not a problem here), In both ways blues were lost and this happens every time and I'd like to know how to get around it and why does this happen in the first place (why blues, other colors seem fine).
Thanks for the 50 cents and I am admittedly not that familiar with the rhino -ViewCapturetoFile command. When I capture images, I typically use the "Ladybug_Capture View" component:
It enables me to have a lot of control over the captured view and to create png animations by automating the taking of pictures when I animate a slider in GH. With this, I am usually using a white Rhino background and not capturing transparency. If the transparency is particularly important, I might suggest baking the geometry and using Rhino render.
Let me know if any of this is helpful and if it addresses the issue.
If I'm right, then you bake real text with the bake button and the previews are just meshes, right?
I'm looking for a way to, on purpose, mesh a lot of text inputs for a faster and more responsive preview (when all the meshes are joined). Is there a line in Ladybug one can copy in order to "Text2Mesh" ?
Here is the function in Ladybug_Ladybug that converts a list of text and corresponding list of points to text meshes:
You can call this function in a python component with the following code:
import scriptcontext as sc
lb_visualization = sc.sticky["ladybug_ResultVisualization"]()
textMesh = 
for meshList in lb_visualization.text2srf(text, textPt, 'Arial', textHeight):
See attached file.
Sorry for late reply.
It is a less laggy preview on several text objects than normal text previews. however the mesh generation is too slow for it to actually be a benefit.