Kangaroo 2.0 effects Rhino viewport target orientation

I have been having trouble with Kangaroo 2.0 effecting the Perspective viewport camera target in Rhino. Once the Kangaroo Solver is placed in the Grasshopper canvas the rhino camera target position jumps around to different targets while I am attempting to navigate the model in Rhino.

I have had this happen on a few computers and am unable to pin point what exactly causes this, as it seems to happen sporadically as I build up Goals and input them in into the Kangaroo Solver. All I know is that it only happens with Kangaroo 2.0 and no other plugins.

I have attached a gh file with the simplest version of this occurring. Once I zoom select the points and move the Rhino perspective viewport around a bit, it suddenly jumps to different focus points in space.

Any advice/help or other discussion to point to?

Attachments:

Jumping camera target position.gh, 15 KB

Replies to This Discussion

Permalink Reply by Daniel Piker on December 18, 2015 at 12:16pm

Hi Jason,

I can't reproduce this, and haven't heard of such behaviour before.

The file you posted is just has some lines preserving their start length and some anchors, with no other inputs? - so nothing moves at all in the Kangaroo simulation.

You're saying that when you select these points (by using zoom on preview on the solver component?) the Rhino viewport starts behaving oddly?

Permalink Reply by Jason Hare on December 18, 2015 at 1:33pm

Hi Daniel,

Sorry I uploaded an example of the simplest case I have had with this problem.

Here is a more robust file.

I should clarify, the gh file I have uploaded has the information internalized so that I can upload the file onto this forum (due to size). Though all the internalized information (points and curves) are drawn geometry in Rhino. So when I select some of this geometry (ex. a few points) then run the zoom selected 'ZS' command in rhino and begin to orbit around the geometry, the perspective viewport (which I am looking through) jumps to different target positions, almost as if it is referencing multiple orbiting axis.

Again this has only happens while I have been working with Kangaroo 2.0.

...might be a stumper!

Attachments: