algorithmic modeling for Rhino
The thing is: I don't need camera big thing :D
I guess there is some way out there of doing this, because I once messed around with the viewport command in rhino and so on ... what I get is always the same geometry view, when I open the grasshopper definition. It's really always the same! ... But it's not the view, that I wish to have ...
Is there really no way of doing this without having to install a new plugin especially for this?!
You could script it yourself in a VB or C# component.
The Named View in Rhino is probably what you were talking about. But all that does is save the Camera Location and its target for use later. If you have the camera and target location as a Point and input these to the set camera you will always get the same view.
So I will need these new components ... what's the best and easiest of these two components? ... what plug-in do you prefer? ... Thank you! ...
I haven't used Chameleon, but it is designed to help rhino/gh integrate with revit, so if you use revit, it may be worth checking it out. Horster has the added advantage here of setting your camera lens length as well, which can be useful. Horster also has some other components that help you extract information about referenced geometry...so you can know what layer it is on, its name if it has one, what type of object it is, etc.
I've used both Horster does give you Get Camera as well which Chameleon doesn't but then Chameleon as an Animate Camera component which Horster doesn't.
Chameleon has GH/Revit functions which I've never used and Horster has Reference components which I've only sporadically.
If you wanted to make your own it would could look something like this:
Private Sub RunScript(ByVal L As Point3d, ByVal T As Point3d, ByVal A As Boolean)
If A = True Then
doc.Views.ActiveView.ActiveViewport.SetCameraLocations(T, L)
End IfEnd Sub
file attached
That's what the Up is for on the Horster Version.
Here is the new one:
Thank you Danny ...
Could you please help me with this one:
How does this component (SetCam) work?! The Target location has to be always a point, right? This is where the camera should "look at", right? The Camera location Input is also a point and that's where the camera should be placed, right?
What is the Up vector? How should the Up vector be understood?!
Thank you man!!
but it needs a bit clockwise rotation ...
The Up vector sorts out where the top of the viewport is located
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by