Hi Steve, you're running into some slightly different bugs or oversights in those other applications in each of those cases.
For SketchUp you can find someone else mentioning the same problem here:
http://forums.sketchucation.com/viewtopic.php?f=180&t=27946
The issue with SketchUp is that SketchUp does not actually have any kind of real curves in it, it only works with polylines. So when you import that DXF file, the SketchUp importer breaks the smooth spline curve up into line segments. Unfortunately it uses a very low number of lines which produces the result you see there. There does not seem to be any way to adjust it.
Instead of doing the DXF conversion to go into SketchUp, use the new direct SKP format save function in MoI version 2.0, it will let you control the density of how many lines are created for those curves.
Vectric Cut2D seems to have a different problem - the spline entity that gets created for a circle has a particular NURBS attribute set on it called "weights", and the result that you show there from Cut2D is what it would look like if the weights were ignored and only the x,y,z control points read in from the spline. If you send Vectric that DXF file as a test case and tell them that they are not reading in weight values, that may help them to fix that problem.
You could do a similar workaround in this case as with SketchUp - if you reconstruct the curve in MoI so that it is not what is called a "rational" curve that uses weight values, then it would probably go into Cut2D ok since it wouldn't make any difference if the weights were ignored. For that try running the Rebuild command, as described here:
http://moi3d.com/2.0/docs/moi_command_reference10.htm#rebuild
Then convert the rebuilt curve over to a DXF file and see if that goes in ok.
Just to test the DXF file itself, here is what your original DXF file looks like imported into Rhino:
Here imported into Alibre:
Here imported into ViaCAD:
- Michael