We are 9 months in to developing a web app in Azure that harnesses both Autodesk Forge and Rhino.Compute at the core of what it does. By and large things are good. At its core is this fundamental activity:
- Our app takes a part file from our legacy library of Inventor part files (.ipt) and passes it with new parameter values to the Forge.
- The Forge updates the part’s parameters and exports the resulting shape in a file format that Rhino can open. (very slow)
- This file is sent to Rhino.Compute which opens it and returns its breps as a byte array.
- Our app stores the resulting breps in our database cache for future reuse so in future steps 1 2 and 3 can be bypassed.
We are having problems with the reliability of step 3. When it works it is great and very fast. However we need to decide on the file format to export from the Forge that gives Rhino the greatest success rate in opening the file. We started by exporting STEP format but found that Rhino fails to import STEP files for even quite simple files (see this post). As a workaround we changed strategy and tried exporting DWG but have now discovered that our Rhino6 is also failing to import these files sometimes as well. I attach an example.
SmallCylinderWithTinyCentreHole.dwg (92.8 KB)
Can anyone advise what file format Rhino is most reliable at importing from? Here are the formats that we can choose from (The Forge export options Aug 2020):
I’d like to caveat the question a little further: We are trying to avoid mesh formats such as OBJ as meshes result in faceted geometry and we want precision as our app is an engineering/manufacturing application rather than gaming.
Can anyone suggest a better way of converting (on the fly) Inventor ipt geometry to Rhino geometry?