ts of spheres, that are behind the camera, appear. This normally happens with weird lens length settings. The camera needs a 45° viewing angle and therefore might fall into this category. Maybe there is a good solution to get rid of this issue?
Issue #2: I have no clue how to run the screenshot calculation at the end of the solution. Normally I wanted to color the spheres in the video with the "Custom Preview" component, but they would not show up in the saved picture, since custom preview was calculated later than the screenshot component "Cubemap"
Issue #3: The calculation of an equirectangular image takes quite a while. ~4 seconds. Thats still good compared to the 9 seconds i had in the beginning. Multithreading through parallelizing could improve it even more, but it wouldn't work for me.
Especially ISSUE #2 is annoying and does not allow me to create a nice video. I would be glad if someone could assist me in this.
I actually tried already ExpirePreview or Solution, but maybe I used it the wrong way...
Best,
Martin…
one another by 1 value (255,0,0) and (255,0,1) so thats practically the same color.
Maybe input a minimal variation of 30 units?
Btw shouldnt hue go form 0 to 360? The component seems to just go to 255.…
trying to do.
i have a spiral that i divided in grasshopper into 360 points, that bit i managed to do, what i want is to connect point 1 to point 2 with a line, then connect point 1 to point 3 with a line and so on till point 1 is connected to all the other 359 points in that order, once i have done that i want to then connect point 2 to point 3 and so on, i want to repeat this till i have a connection all the way down the spiral, i'm pretty sure that once the first set of points are dealt with then it should be fairly easy to replicate the procedure to do the other point connections.
Michael…
ine will require a points and normal vectors. Give ArrPolar the same parameters used to position the diamonds, but use a point instead of a gem object. This will give you your points. The normals are just a vectors from origin to the points.
4. I added components to the attached file that includes a VB fillet routine. (I don't recall where I found it.) You have to play with the 2 Boolean values depending on the 2 surfaces you feed the routine. Also, be aware that Rhino does not handle filleted surfaces well when they come from Grasshopper. To fix this you have to invoke the Rhino command _DivideALongCreases - otherwise your filleted surfaces will have corners in them.
…