RyanSpaulding

Hey guys,

I've decided to give it a run...lets see how MicroStation XM plays with Modo, shall we? This will be sort of a WIP project...may not go too fast as I dont have much time...but this Modo forum doesn't go fast either. I must note, I'm a huge Modo novice at this point.

So, 1st thing's first. What doesn't work on import...

The XM > DXF > Modo workflow is not spot on. Seems Modo likes solids or mesh objects...so you cant drop your mesh to individual triangles. Wont work. So use 'Deep Exploration' to accomplish the import. Export from XM to U3D and then open the U3D in Deep Exploration, save as an LWO file. Modo seems to play well with this format. Credit on this specific topic goes to Peter Fotadis.

I do not have the CAD edition to see if the DGN importer works well or not...saving us a step. No biggie as my 43mb DGN came to 1.5mb in U3D format.

I noticed each object comes in seperate...so each post can be selected, each wall that's not merged, ect. The tree is Layer > Object. It does not differentiate between colors on your level. If you want to seperate objects of selectability, use different levels...not one level with X number of colors.

The camera from XM comes through, but I'm not sure if it works yet. Directional light (aka the solar light in XM) also comes over.

Modo is a bit resource heavy...I've noticed significant slowdown in workflow. It'd be best to make only necessary levels visible. Import can also be a bit slow. I've had 1 crash due to moving geometry around.

Another note, on 1st glance, I dont see any Import function. It may just be the OPEN command when it's not an LXO (luxology) file...but at this point, I tried to have my scene open and import a simple 3ds file...and it's hanging. So I'm not sure how to add items to the scene such as XFrog trees, 3D People, or 3d autos.

UPDATE: The 'Open' function while in my design file crashed Modo.

Seems stable. One crash for moving my geometry, one for opening a file.

wda

To copy...you need to open the new file. It will show along with the files already there.

Try to dragging and droping a mesh from one file to another in the item list view. Make suer the import dialog box has everything checked. You materials from the imported mesh appear in the group called imported shader of the shadertree view. Usally very few problems with the materials until you copy only polys and paste into a mesh. Then you need to restructure the group and base shader in the render>shader tree.


WDA

__________________
From the calm seas.... Into the CG Fire...... Into the Heart of Texas

RyanSpaulding

Thanks man. I'll try some more today!

EDIT: Some potentially bad news. When I import my original LWO scene, all my levels are in tact...so I can select glass with one click, select siding with another, ect. If I save the file as an LXO file, close, and reopen, my levels are gone and I'm left with 10,000 'Geometry: ###' items...hardly usable.

CHE

Ryan,

Have you tried AccuTrans? I use it all the time to convert files to LWO for Modo and vice versa. Here is a link to a post that explains how to use it for Modo.

http://forums.luxology.com/discussio...show=accutrans

I hope it helps,

Ernesto

RyanSpaulding

I wonder if it's even an issue with DE's translation though...because it comes in fine. It's when I save and reopen it in Modo...that leads me to believe DE's work was done fine, it's modo's issue. I'll try AccuTrans to see...

CHE

Modo does not support 3ds files. It has a DXF importer/exporter but it is very slow and it doesn't always work well. You can also try exporting to OBJ but I have had better results with LWO files. AccuTrans will translate your layering and in some cases cameras and UVs. I do have not experience any "merging" of layers after closing and opening th LXO before. Do you loose all your mesh items when that happens?

RyanSpaulding

No, I dont lose them...I lose the item tree.

Here's a link to my issue.

Attached Images

modo_issue.jpeg (88.8 KB, 50 views)

RyanSpaulding

No new news. The Luxology forum users think it may just be an incompatability between the CAD way and the way Modo 'optimizes' files.

RyanSpaulding

So, the workaround to this is:

Within the 'Levels' item tree, go into each layer name and see if there are any further objects that have child objects attached to them. If there are, select those light grey items, right-click and hit 'delete' but DO NOT delete children when it asks. Then, once you have the layer as the only grey item and all children beneath is are in black, right click on the layer name and select 'Change Item Type' to 'Group Locator'.

Group Locater seems to be the equivalent to layers.

This is, however, a pain in the ass for any arch viz workflow as it adds a step to do and sometimes, the way you build your CAD model will be affected.

I'll research a different method into Modo to see if this step can be eliminated.

CHE

Yeah. Unfortunately, there is not direct translation for CAD files into Modo. As you know, there is a DXF importer/exporter but it doesn't work with complex models very well. Right now, your best bet is to use AccuTrans but even then you will be left with a lot of cleaning up to do in Modo. You could also use Cinema 4D to import your Model and then export it as a LWO. Some guys have had great results this way. Personally, I would do all my modeling in Modo. I only use AccuTrans to translate CAD floor plans and elevations. I moved into Modo because I was looking for an alternative to 3dsmax and I truly believe that I couldn't have made a better choice. You will be missing a lot of what makes Modo unique if you only plan to use as a render engine.

Ernesto