Hi Igor - It's pretty much impossible for me to do anything about that without having some examples of problems...

All the previous examples that you sent went into the new Revit 2010 fine, if you remember there was a discussion thread about that back here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=2634.1

So far I have not received any other examples of problem files.


The last problems that you sent in that thread above that did not come into Revit 2009 but did go into Revit 2010 also were properly formed SAT files that loaded into other SAT-based modelers without any problems. So as far as I could tell, Revit seems to have a pretty fragile importer that is still being worked on quite a bit, since there were definite improvements in version 2010.

It seems that Rhino will alter the geometry when you save to SAT to split closed surfaces into 2 joined halves, maybe there is something in Revit that does not handle closed surfaces well or something like that.

But I can only speculate when I only hear rumors of problems rather than having actual files that I can test with.

- Michael

>>As for tests - try importing one of your own more or less complex models into revit (trial if you still have it) and see the result.


Hi Igor,

I have not as yet seen any problems with sat export from MOI. Those exported sat files are imported into various other applications, such as Viacad Pro(Acis), solid_works and solid_edge, I have seen/hear no problem. Inventor 2010 does import sat files from MOI ok (certainly on the models made), but step files still cause it issue (even though I know the step files are OK and import into every other application checked).

Please do post an example file so a check can be made on its import into various other applications.


Regards,

- Steve

Hi Steve ! Welcome back :)

> Inventor 2010 does import sat files from MOI ok
> (certainly on the models made), but step files still
> cause it issue (even though I know the step
> files are OK and import into every other application checked).

That's surprising, I find *.step to be the most robust translator when importing into Industrial 3d CAD programs, I find it the next best translator to parasolid *.x_t


-

Hi Igor, for the next MoI v2 release I've updated the SAT export so that it will split closed surfaces (for example cylinders) into 2 halves rather than having a single closed surface that has a "seam edge" in it.

That appears to be one of the major problems with Revit, that it gets confused pretty easily when trying to read in surfaces like that.


I don't know yet if it will solve the particular problems you ran into because I did not receive any files from you to test with... But it appears to make a big difference with getting stuff over better.

It will be possible to turn off closed surface splitting by a setting in the moi.ini file.

- Michael

Hi Danny,

>>That's surprising, I find *.step to be the most robust translator when importing into Industrial 3d CAD programs, I find it the next best translator to parasolid *.x_t

Inventor will not import an exported Step file from MOI, even a cube gives error. Step AP203 from SW imports (on quick tests) OK.


I have been looking at importing a Sat file from Viacad(Acis) into Revit(demo), anything above sat V7 gives error, below V7 does import, but not an expected result, as example, a cube is imported as a rounded cube.

Looking at Inventor, that will import sat from MOI and sat V7 (and below) from Viacad(sat above V7 from Viacad is reported as "not supported")


- Steve

Hi Michael!

That's a huge step forward with sat export!!!
I tested it on 2009 ver and it went in perfectly!!! Just like rhino now!))

I now can't wait till you release next beta cause next week i start a new project and might already start using MoI heavily..

btw you mentioned that it will be an option in moi and now you say that it will be switched on by default.. Will such spliting affect performance of a MoI model? when it will be preferrable not to have it switched on?

Thanks
Igor

Hi Igor,

> Will such spliting affect performance of a MoI model? when it
> will be preferrable not to have it switched on?

Well, the main thing is it alters topology - things like edges that cross the split line will be split into 2 edges rather than staying as one long edge.

It can be nice to keep edges longer when possible, it makes some kinds of operations that work by selecting edges such as fillets to be handled easier since there are less pieces to pick.

I don't think that you will have much choice but to leave it enabled for going into Revit though, since Revit just does not seem to handle closed surfaces.

- Michael