Modo Scripts
mm_LWMotionIO
Posted by on Tuesday, September 18, 2007 (GST)
 
17 March 2010: Updated to fix problems running under modo 401. In 401 the script is also automatically attached to the bottom of the right click context menu in the item list - you can just right clcik on the item for which you want to import or export a motion and select 'Lightwave MotionIO' from the menu and the usual form will pop up.

Requirements: For modo versions earlier than 401, these scripts require access to python librarries that are not shipped by default with Modo. In Windows it is advisable to install  a full distribution of Python 2.4.3 such as the one from ActiveState
 
 
Zip contains 4 files:

mm_LWMotionIO.cfg - goes in user configs directory
mm_LWMotionImport.py - goes in user scripts directory
mm_LWMotionExport.py - goes in user scripts directory
mm_ModoUtils.py - goes in user scripts directory
 
 
Setup:
 
Copy the 3 files from the archive into the correct directories. Restart Modo.
 
To add the UI to a pallette or window, create a new window from the layout menu. Click on the arrow at the top, right corner of the new window and select 'Form View' from the menu. Now right click on the title (the dark band at the top of the window that now says 'Form View' and select 'mm_LWMotionIO' from the menu. Your window should now look something like the following:
 
 
 
 
Usage:
 
Importing a lightwave motion: The script will load and apply data from a Lightwave motion (.mot) file to the currently selected item in the item list. Ths cript knows the difference between mesh layers, cameras and lights, so it won't for example, attempt to apply scaling channel information to a camera. If you do import a motion file containing scaling data to a camera, the script will apply the channels that it has in common. As you can see from the screen shot above, you can also manually select which channels you wish to load from the file.
 
Exporting a lightwave motion: The script will export the motion channels for the currently selected item in the item lost to a Lightwave motion (.mot) file. Checking the 'baked export' box will bake and save out the motion as individual frame values.
 
 
Note:
 
There is currently no acceptible (read accurate) way of translating curve control parameters between Lightwave and Modo. If you want your motions to appear exactly the same in both applications it is advisable to bake them in Lightwave prior to exporting or chck the 'baked export' box in Modo if exporting from there.
 
 
Add any comments, questions, suggestions etc as comments to this article. You will need to be registered as a member and logged in to do that.
 
 
 
Comments:

How do I save out camera motion from Lightwave?
By wesball on Thursday, June 12, 2008 (GST)
I've been searching for an hour with no luck.

I've used pftrack to export a LWS. Camera motion is full of keyframes for postion, rotation, zoom... 

but I don't see how to save out the camera motion?


Camera Vue
By Felix on Friday, May 07, 2010 (GST)
Hi there, I have installed this script, when I run it I get a "script execution failed..." error message.

I am assuming this is because my camera position is parented to a locator, which in turn is constrained to a path, the camera  also has a directional constraint to another locator, the rig works great, thank to Andy Brown. So the other option is to bake out the export, which produces a TXT file.

Is there any way to get VUE 8 Infinite to read this data. Vue has syncronization plugins for Lightwave and import data file capability too, though it does not recognise the text file generated for the script.

Any sage advise would be greatly appreciated.
THX

F

BTW, thanks for all the great scripts!