Hi George, sounds like some kind of bug.

Could you please post or e-mail the .3dm model to me at moi@moi3d.com so I can take a look at what might be going wrong in getting the units?

Thanks
- Michael

Here is a Meters file straight from Rhino. I tried the tol settings but didnt affect the mm read in MoI. Thought I'd pass it to the master.

Burr

Hi Burr, thanks - I see the problem now. Actually the same exact thing happens if you read the file into rhino version 3.0 .

It seems that Rhino version 4.0 has a change to the .3dm file format that is not compatible down to the v3 version reader, which is what MoI currently uses.

To get the units across properly in this case you will need to save from Rhino as a v3 3DM file and then that should work.

- Michael

Hi George & Burr - I've fixed this up for the next v2 beta so that units will be read in properly from v4 Rhino files.

For the time being saving as a v3 Rhino file instead should also make them come through.

- Michael

Thanks Michael

Hi Michael,

>>Updated Circle and Arc Tangent commands

It works fine in 2D But not in 3D

That's not your fault because i didn't mention it
Maybe next time

Compliments on this v2 beta update

I Michael, I have a little .3dm v4 file related problem.
I try Rhino 4 for texture and render a moi shape. Rhino ask me to save in v4 because v3 it's obsolete. I can open it again with moi, but if I change something and save it I lose all the material information. It's going to change with the next beta or we have to take care about this and don't save back in moi?

Thanks
Luca

Hi Paolo,

> It works fine in 2D But not in 3D

Yes, it is generally the case that these kinds of tangent constructions only work on objects all in the same plane...

For curves that are all going in different directions in 3D, as far as I can tell there will not likely be any solution to be found for a circle tangent to all 3 3D curves simultaneously.

Maybe I don't understand your situation though, can you please post a model file with some 3D curves in it that you would have expected to work so I can take a look?

> Compliments on this v2 beta update

Thank you!

- Michael

Hi Luca,

> It's going to change with the next beta or we have to take
> care about this and don't save back in moi?

I'm not quite sure yet how much this will change right away, it is possible that I will only be able to handle some of the basic information at first such as object color and not really full materials for a while yet.

But I will try to keep that in mind though.

- Michael

Hi Michael, I don't intend to handle all the material information, but maybe not "broken" the information already in place.

Thanks
Luca

Hi Luca, do you have an example file that you could send to me?

That would help to test with and to see what I could do to preserve it.

Right now I am not sure how difficult that would be.

- Michael

I'll send you this evening, no problem.

Bye
Luca

By the way, has anyone had a chance to test the new FBX format export into 3DS Max to see if it does provide a better quality data transfer as expected?

It should be able to get n-gons and the vertex normal shading information across.

Please let me know if you have run into any problems with it or if it seems to be working well.

- Michael

Michael I just tested it for you on a somewhat complex model.
I exported to FBX (ngon option) and imported into Max 9

For some reason all my materials in Max looks like the gamma has been turned up or self illuminated (is that the vertex normal shading ? )
>>>> edit: (i figured out what this is the ambient color of the environment panel needs to be set to black instead of mid gray which happens during fbx import).

I did get quite a few polygon errors around the boolean cutouts. It seems to have double polygons in this area with one the right way and another flipped.

The mesh generated also seems to have 3 times the amount vertex's it needs which can fixed in max by selecting all verts and weld (after setting your tolerancing factor accordingly).

Also the model comes in faceted so the user would have to apply smoothing groups inside max.

The ngon option makes for a neater mesh and will make uv mapping a lot easier when it comes time to break the model into pieces.

Hi Michael

Just a little question about SketchUp Exporter. If you export only curves, you get nothing (Export don't work). If you include a solid or surface (s), in SketchUp you get the meshes but not the single curves.

Thanks,



George

Hi George, thanks for reporting that - yes the exporter does not handle curves at all, only surface data.

- Michael

Hi Kevin, thanks for testing the FBX!

I believe that Max 9 is older than the current Max version which is Max 2009, is that correct?

I think that for Max 9 you need to update its FBX importer plug-in to the newest version to get rid of some of these problems, you can get the FBX plug-in here:
http://usa.autodesk.com/adsk/servlet/mform?siteID=123112&id=10775855

Sorry I forgot to mention that earlier.

- Michael

>I believe that Max 9 is older than the current Max version which is Max 2009, is that correct?
Yep, since Max 9 there has been Max 2008 and Max 2009. So Max 9 is approx 2 yrs old.

Thanks for the link, I'll give the plugin a try and let you know if that gives a better result.

I'm not having any luck with the .fbx meshes from MoI in 3ds Max Design 2009. It loads in without any problems, and it looks great...no errors, the mesh looks exactly the same as in MoI. However, when I try to render it crashes 3ds Max. I say it crashes, in reality 3ds Max simply disappears from my desktop. This issue only happens when I try to render an imported .fbx file from MoI.

Jeff

Maybe just save the file in MAx format, reload it and render? ;)