Hi Christiaan, unfortunately not. PW integration is about loading a file into AutoCAD rather than a file format. ie it does not enable DGN in AutoCAD that has to be done by Autodesk. Similarly for Revit, that is an export which publishes a Revit model. We already have a Revit loader, however, we would need an iTwin to RVT which is very different to referencing an iTwin. This would require a "Link iTwin" capability, much as they have an IFC link capability. You have asked, but extending an application handle iTwin is generally done by the applications developers. ie we ingress Revit, so we would expect Autodesk to ingress iTwin. I know there is a subtle difference, but they are fundamentally different. This is up to the Product Managers within Bentley, but wanted to check if you had pushed this with Autodesk
Hi Glen, Will raise this if I can find the right persons. But in general I think it would be faster if Bentley creates this one, Autodesk is pushing there own cloud solutions and I can immagine they won't prioritize this. Bentley already devlivering plug -in's for Autodesk with the PW integrations and what you did in the past with the i-model plugin for Revit. I'm convinced this will drive the adoption of iTwins much quicker if Revit users can refference in iTwin models directly.
Did anyone consider raising this with Autodesk ? To integrate this into AutoCAD and Revit would require access to their source. iTwin libraries are opensource and Autodesk have the ability to do this seamlessly.
Please put this on a higher prio to close the loop between Autodesk and Bentley and give us as Bentley users the posibility to start using iTwins more and more and push it through our organisation. Now a days we have to export IFC from iTwins that doesn't work as it should be.... so please consider to prioritize this! so We can collaborate better with Revit Users if they can have acces to the Coordinated iTwin model and all the issues
Hi Christiaan, unfortunately not. PW integration is about loading a file into AutoCAD rather than a file format. ie it does not enable DGN in AutoCAD that has to be done by Autodesk. Similarly for Revit, that is an export which publishes a Revit model. We already have a Revit loader, however, we would need an iTwin to RVT which is very different to referencing an iTwin. This would require a "Link iTwin" capability, much as they have an IFC link capability. You have asked, but extending an application handle iTwin is generally done by the applications developers. ie we ingress Revit, so we would expect Autodesk to ingress iTwin. I know there is a subtle difference, but they are fundamentally different. This is up to the Product Managers within Bentley, but wanted to check if you had pushed this with Autodesk
Hi Glen, Will raise this if I can find the right persons. But in general I think it would be faster if Bentley creates this one, Autodesk is pushing there own cloud solutions and I can immagine they won't prioritize this. Bentley already devlivering plug -in's for Autodesk with the PW integrations and what you did in the past with the i-model plugin for Revit. I'm convinced this will drive the adoption of iTwins much quicker if Revit users can refference in iTwin models directly.
Did anyone consider raising this with Autodesk ? To integrate this into AutoCAD and Revit would require access to their source. iTwin libraries are opensource and Autodesk have the ability to do this seamlessly.
I agree with Christiaan. This would help adoption from our Revit users.
Please put this on a higher prio to close the loop between Autodesk and Bentley and give us as Bentley users the posibility to start using iTwins more and more and push it through our organisation. Now a days we have to export IFC from iTwins that doesn't work as it should be.... so please consider to prioritize this! so We can collaborate better with Revit Users if they can have acces to the Coordinated iTwin model and all the issues