Very cool stuff in this thread, well done guys.

Cheers

Thanks for the new functionality Michael, and thanks to Paq for testing, (and I suspect suggesting).

I did some experimenting with this and found that if you have a solid object the whole object will be
outlined, as in the background object. If you want all parts outlined as in the foreground object then
you just need to use Edit - Separate in Moi before exporting to LWO.

Hi danperk - actually you're supposed to be able to keep it together as a solid when you export.

Do you notice any difference if you export with welding turned on or off?

Are you doing this in Modo or LightWave?

Also do you have the contour mode set to "segment boundaries" and not the other "surfaces" option for it?

- Michael

Hi Michael,

I tried with welding on & off.(normally on)

This is done in Modo.

I'm using segment boundaries.

The 3DM file is attached.

Hi danperk, hmmm well the part labels seem to be generated ok when your object is exported as a solid - it generates 49 different part labels and there are 49 different surfaces in your model...

Do the part assignments seem to be correct when exported as a solid? I mean if you go into the Statistics pane in Modo you should see a "Part" category with 49 different entries under it. If you select some of those does a small portion of the mesh corresponding to one of the original surfaces get selected?

- Michael

Remember you have to convert the modo mesh to static mesh before this will work.

I tried your file and it worked perfectly exported as a welded mesh and converted to static mesh in Modo.

Very strange.

>>Do the part assignments seem to be correct when exported as a solid? I mean if you go into the Statistics pane in Modo you should see a "Part" category with 49 different entries under it. If you select some of those does a small portion of the mesh corresponding to one of the original surfaces get selected?<<

I see 1 object in Modo, unless I use separate in Moi. Attached image of my export settings.





SteveMacc said: >>Remember you have to convert the modo mesh to static mesh before this will work.<<

Yes, it's a static mesh, not in the image capture, but I do that step.

Here's my LWO I/O settings in Modo:

Hi danperk,

Parts should be visible in the statistic, under POLYGON > PART

If parts are visible, then every should work fine :

Turn the mesh into static mesh (seems that's what you have allready done)
Turn the contours on, using the Segment Boundaries method (and not Surfaces Boundaries).

If it still dont work, could you post the .lxo scene ?

Hi PaQ,

Nothing in statistics. Even though the mesh is converted to a static mesh it still
shows as an ordinary mesh. (maybe 501 bug!?)




Attached Zip file contains the exported LWO file and a LXO file.


The only thing I have done with my Moi set-up that my be non-standard is that I'm running my Moi.ini file from previous Moi beta 2 versions.

Hi danperk,

Well there is something wrong with the MoI export, the .lwo you provide do not contain the part slicing.

So either the patch didn't work, or the moi.ini dont contain the :

[LWO]
WritePartTags=y

We have to wait Michael advice on this one.

FYI here a .lwo export from the .3dm you provided.

You should be able to render contour from this file in 501.

Thanks for checking the file PaQ!
Your file works fine for me, I can see the parts list and it looks fine
and the file you exported renders correctly.

Well the entry is in the Moi.ini file:



When I ran the update.cmd file I didn't see any error messages.

Michael, does the update.cmd create a log file?

Hi danperk,

> When I ran the update.cmd file I didn't see any error messages.
>
> Michael, does the update.cmd create a log file?

No, it doesn't make a log file but if it didn't work properly it should have printed out an error message on the command line. You may not see that if you're running it by double-clicking on it from Windows Explorer - maybe try running it from a command prompt to see any error messages that will then be printed out in the command line as well.

Also if it worked properly there should be a backup file of the original moi_lib.dll created in that same folder named moi_lib_orig.dll

Hmmm, maybe you're running into some kind of UAC issue on Vista or Windows7, maybe if you can run it as Administrator that might make it work.


Maybe the other possibility is that you have edited the wrong moi.ini file? Did you say something about using one from a previous beta? Are you using it by having the moi.ini file copied into the same folder as the moi.exe program? If so then that's the one that you would need to edit.

You can see which moi.ini file it actually being used by going to Options > General and pushing the "Edit .ini file" button - it will pop up a dialog box that will show where the moi.ini file that is currently being used is located at.

- Michael

Hi Michael,

I checked the MoI directory and there was no file
named moi_lib_orig.dll.

Here's a capture of the Com window after running update.cmd:



Tried to run as Admin. as well and no change. I'm on Win.7 64bit.

Michael Gibson wrote: >>Maybe the other possibility is that you have edited the wrong moi.ini file? Did you say something about using one from a previous beta? Are you using it by having the moi.ini file copied into the same folder as the moi.exe program? If so then that's the one that you would need to edit.<<

I always edit MoI.ini from within MoI.

What I was referring to about the Beta 2 ini file was that I copied my setting from the last Beta 2 Release. (shortcut Keys).

You need to run CMD as Administrator. Here is how to do it:

http://www.howtogeek.com/howto/windows-vista/run-a-command-as-administrator-from-the-windows-vista-run-box/

You can't do this by using "Run as Administrator" directly on the cmd file. You have to open the command window as Administrator first.

Hi danperk - yeah that's the new-ish UAC system in Windows that kind of locks down the machine in certain ways.

One of the things that it does is prevent modifications to stuff inside the \Program Files folder.

If you can get a Admin command window up as Steve describes above, that will probably enable it to work.

Another way is if you temporarily disable the UAC system - to find the setting for that type in "User Account Control" into the search box, that should get you to the control for it.

- Michael

That did it, Thanks Steve! Thanks Michael and PaQ!

Man it's been a long time since I used a DOS prompt!!

With UAC, PowerShell and 2008 Core, old, often quoted Bill's sales pitch that Windows is better Unix than Unix is slowly coming true. Some fifteen years after - it was NT 4 that he was praising at that time!

Thanks Guys. I had the same problem and had been scratching my head that I must be doing something wrong. After following the instructions of firing up the command line in Admin mode I'm good to go :)

Cheers
Nigel

That's a nice addition (in both modo and MoI) !
Works really great.

You can even define a line width smaller than 1 pixel (here I've chosen 0.5)

Thanks Michael for the update (I had to deactivate the UAC to make it work)
Thanks to PaQ for requesting the feature. Also, nice images in the 501 preview tour !!! Congrats