Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - GammaNYC

#1
Support / Re: Collision and Unreachable Position Detection
September 11, 2018, 06:31:00 PM
I have interpolation enabled at 1mm resolution (which slows GH wayyyy down), but even then I can't get it to output the correct numbers.
Here's a screenshot of the unreachable path. Even though the simulation shows that one of the axis is unable to reach (hence it turns red) the analysis output does not reflect it.

@singline: cant post the gh file because it uses a lot of custom coded component for which i cant provide the DLLs for.

#2
Support / Collision and Unreachable Position Detection
September 10, 2018, 09:17:52 PM
Hello,

I am attempting to extract the collision/unreachability state of my simulation by looking at the analysis values under the "COLLISION" and "REACHABILITY" outputs, however, there seem to be moments where the path created is unreachable and those outputs still give me a value of 0 on all positions (when they are supposed to give me a value of 1 when a problem is detected).

The simulation still changes the axis to a red color during those moments, but the PRC engine stays gray (meaning everything is fine).

What am I missing?
Is there another output I can monitor to catch these exceptions?

Thanks
#3
Also not too sure how to exclude specific DLLs from a project that loads Grasshopper.Kernel (I assume all DLLs get loaded together). Do you have any suggestions on how to approach that?
#4
Thanks for looking into it. Let me know if you need any debugging output from me to diagnose the problem. I am running VS 2015 and Rhino 5.
#5
After installing KukaPrc I have problems developing C# components in Visual studio. When I compile and grasshopper opens (F5) it gives me a few errors (see attached images). Even though I am not using KukaPRC for the particular component I am developing. It just gets stuck loading that dll.
The funny thing is that when I open rhino outside of VS, I can still run the components I developed, so the errors must not be super critical, (more on the loading side) however they do stop me from launching GH directly from VS, hence my need to fix this.

Any suggestions?