Messages

I even forgot that that used to be "Expose base" in KUKA|prc, since I had always on since a lot of time ago.

That is a possible solution, however much more convoluted than before.
The same would go for project name (name of .src exported). In some cases I generate it via concatenation of strings and values from my definition, and it is not fixed.
What is the syntax to define that (and other settings) via Override?

Since you ask for feedback, another feature I miss (off-topic) is the ability to play path preview at increased speed, and play from any point into the timeline. Currently, I can only play from the beginning at 1x.
It would also be very useful to play portion of animations from the Analysis tab. That is something I always used to do in KUKA|prc, to better understand problematic passages, to focus them on the analysis and not only see the static position, but a short movement animation in the Rhino viewport from a little before the problem until a little after

Hi all, few months ago I developed a grasshopper component which works on top of KUKA|prc plugin a tool set developed by Robots in Architecture and enables users to remove the collision from a define tool path by rotating the fifth axis about the rotary axis of the tool. The usage of this plug-in is mainly in the area of the robotic machining where a tool is attached to the robot arm and used for milling. I am now publishing the plug-in for a limited period (end of the year) in order to get feed back from end users. Please visit my website for download and use the forum on the same page to give your feedback.

Link to download https://www.parametriczoo.com/index.php/products/kukaprc-tool-path-optimizer/

I am interested in this but unfortunately there are compatibility problems. THe same already posted by a user on "your" (?) site, which looks pretty dead and left to spam bots only.

Code Select Expand

Object: KUKAprc_ToolpathOptimizerComponent (level 2)
{
Method not found: 'Boolean System.IEquatable`1.Equals(KUKAToolPath.IGraphPathSegment)'.
MissingMethodException
}

Hello
I'm trying the new PRC and noticed the different way Bases are managed, which I don't understand.
In KUKA|prc that was straightforward: provide a base, from my own list of bases to the Core component.

in PRC, i don't understand where Bases are actually stored. It seems I have to open the settings, select a base slot and edit manually, which is quite worser than before since it was important to numerically store in my definitions for multiple reuse. When I create a new GH definition, it seems that upon creation of the new "Robot link" for that definition, bases previously created are inherited (copied/pasted) automatically, but then I can change Base 1 in one project while Base 1 in another stays unchanged.

So my questions are:
Is it really no longer possible to input bases from outside the Core component?
Is it the same for project name, so that I have to type it manually for each new use of the component?

This looks to me a major step backward in streamlined usability

Regards