Fabrication API 2017 and up, issue changing connectors, seams, etc

Anonymous · ‎08-15-2017

I have tested the Fabrication API sample project provided by Autodesk on 3 versions of CADmep and CAMduct. In 2016, I would open the FabricationSample interface and change an item's connector with it. No problem.

If I use CAMduct or CADmep 2017 and above and repeat the above steps (with the addin for that version), the moment the connector is changed, the IsNone property gets switched to true as well. This results in a connector that is set to None instead of a connector that is simply changed. I have debugged it. This property takes place during the item.ChangeConnector() method. Not at the necessary lock thereafter.

This affects seams too, and I assume could be a problem elsewhere within the API.

I've also tested the older .COD scripts in the affected versions. The scripts can still change a connector just fine.

I have a Revit AddIn that needs to be able to communicate with CADmep and CAMduct both. The AddIn that I am developing with this API is bar none going to be the best route to take. However, this problem has grounded it, full stop. We have projects in process that can use fallback methods, but they are problematic at best.

Anonymous · ‎09-12-2017

Autodesk confirmed the defect. I'd imagine a fix should be in the next round of service packs which they seem to only be releasing now to subscription customers.

dkessler · ‎04-25-2018

I appears that this has still not been fixed. Is there any time frame on this?

@Anonymouswrote:
I have tested the Fabrication API sample project provided by Autodesk on 3 versions of CADmep and CAMduct. In 2016, I would open the FabricationSample interface and change an item's connector with it. No problem.

If I use CAMduct or CADmep 2017 and above and repeat the above steps (with the addin for that version), the moment the connector is changed, the IsNone property gets switched to true as well. This results in a connector that is set to None instead of a connector that is simply changed. I have debugged it. This property takes place during the item.ChangeConnector() method. Not at the necessary lock thereafter.

This affects seams too, and I assume could be a problem elsewhere within the API.

I've also tested the older .COD scripts in the affected versions. The scripts can still change a connector just fine.

I have a Revit AddIn that needs to be able to communicate with CADmep and CAMduct both. The AddIn that I am developing with this API is bar none going to be the best route to take. However, this problem has grounded it, full stop. We have projects in process that can use fallback methods, but they are problematic at best.

Micaletti · ‎07-25-2018

Any news on this?

Anonymous · ‎09-03-2018

I just did a test with the 2019 Fabrication API in CAMduct. It appears to be working like it did in 2016 again.