Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
It makes me very sad to see how far down the vote list I had to scroll to find this.
This is so vitally important and would make fusion as a whole a VERY powerful package.
Personally, I am more concerned with being able to call any tool path function and define its parameters. BUT I would settle for being able to call a saved tool path template at the minimum...maybe that's easier to implement?
If the CAM team is too busy, can anyone give us some information as to how we might go about building some of this functionality ourselves?
Maybe I'm being overly hopeful, but this is so critical that I, for one, would be willing to help in whatever limited capacity I could.
The CAM API desperately needs extension. The documentation (which is now 2 years old) says that phase 2 is coming 'later in 2016' and yet, here we are, still without the ability to even get basic information through it- I cannot request the tool list and tool information, let alone manipulate it. I can't get the setup information (like offsets, relate the selected setup model to the CAD side, etc.), I can't get the toolpaths themselves (except in a convoluted way through invoking a custom post, which is a ludicrous methodology) And all that is just basic information request, not even asking to set those things!
Agree on this. Although the limited number of post about the CAM api and posts asking for this functionality make me ask: Is there little interest in the API? Or does the API in its current form generate little interest.
I think a good API would be great to let machine vendors build Addins for their machines, but maybe most users just want to use Fusion just as it is.
