วีดีโอ

Very nice. Had to watch twice to understand. Keep it going.

I learned something! Thanks, like these short videos.

Thanks a lot for sharing, Hyvää uutta vuotta!

Thank you, well explained. I will reference this video in the future.

Thanks for this! I still don't undertand the entire point of the frustrum (the cage) of the view. The X and Y extents inputs define the size of the rectangle closest to the location. The Z domain does nothing. Neither does target. I think maybe the developers rushed the publishing of this component or have things planned that are not implemented. The old Make2D Parallel and Perspective views work just fine with less inputs.

Can you explain how the "Model View" component works?... I am so lost.

Thank you for the explanation, what I was looking for.

"This was a really helpful video! As someone just starting out in computational design, I'd love to see a series focused on beginners to cover the basics step-by-step. Also, I have a few specific questions I'd love to clear up-how can I reach out to you personally for some guidance? Thanks for the great content!"

mean get 4 views

The video is great, you need to keep promoting your channel. Is not hard.

Go go!

Great tutorial! Thanks for sharing!

cooooooooooooooooooooool

Where I have stumbled in figuring these out is the Content Cache settings. I would connect everything to the nodes of the Model Layer and zero effect. Thanks for showing this in the example. Action 1.

wow, so clear. Thank you!

u sound very handsome. I bet ur face is handsome too

Thanks SO MUCH!!!

Can Query Model Layers find the current layer?

@1:39 That is because the Move component takes Grasshopper Geometry as an input, and you are providing it with Model Content. The Move component will reinterpret the Model Content as Grasshopper Geometery, i.e. take the geometry of the Model Content, and work with that. To rebuild Model Content that is to be pushed or baked into Rhino, you would have to run it first through the Model Object Component. Generally, you do your geometric manipulations before preparing them for output to the Model Object and User Text components.

Query Model Objects next please!

Will you eventually be showing an example of how the Rhino components work in concert?

These new playlists are very helpful, Thanks

Thank you very much for taking the time to do this for me! I, in the meantime, had researched the two components in order to understand them better, and yes, it would seem that the geometry cache is the predecessor of the content cache, thrown together in about a day by David Rutten some 13 years ago. It now languishes in the geometry panel as a broken legacy component. The promise of what the content cache can do is large, but intimidating and convoluted. I sincerely feel as though the developers need to rethink how they plan to address the interopability and means by which geometry travels between Rhino and Grasshopper.

I like your accent. It sounds Finnish? or at the very least Scandinavian. Could you do a video on the Geometry Cache component? Cache is pronounce like "cash". Have a nice day!