Page MenuHome

Import: LightWave object file (.lwo)
Closed, ArchivedPublic


Project: Blender Extensions
Tracker: Py Scripts Release
Blender: 2.64
Script name: Import LightWave Object (.lwo)
Wiki page:
Author(s): Ken Nign
Category: Import Export
SVN Download:
Status: Open

Allows you to import a LightWave object, both the newer LWO2 and original LWOB/LWLO formats. For layered objects, each layer is created as its own object.

Will import and apply UV, Morph, Color and Weight map data. Can also construct an Armature from an embedded Skelegon rig.

Maintains correct vertex order/count so that .mdd files can be exchanged between 3D programs.

Just place the script into Blender's scripts/addons folder. Like any other Add-on, it will need to be enabled in Blender's Add-Ons panel.

With the script enabled, you can use it via the File>Import menu as LightWave Object (.lwo). Selecting that menu entry will open Blender's file browser where you can select a .lwo file and adjust the script's options. The script provides a few options for how to import the object, currently they are:

Load Hidden Layers: Object layers in an LWO2 file can be marked as hidden. In LW, a hidden layer shows up when modeling but not animating. If the model being imported is destined for further modeling, this option should be enabled. Default=Off

Create Armature: Will convert an LWO2 file's embedded Skelegon rig into a Blender Armature. This Armature object will have the same name as the object layer but with the prefix "ARM_" Default=On

Apply SubD Modifier: If any of the polygons in an object layer are set to be subpatched, then Blender's Subdivision Surface modifier will be applied to the imported object. Default=On

The attached 3Cubes.lwo file shows the importers ability to load and apply UV and Vertex Color data. The cow.lwo in the .zip shows loading skelegons, UVs, Shape Keys (from endomorphs) and Vertex Groups (from weight maps).

Event Timeline

Ken Nign (ken9) edited a custom field.Sep 2 2010, 7:08 AM

Hi Ken
- looks good, think this is acceptable for trunk addons
- manual text can be moved to a wiki page like other addons.
- further development can continue there. (would suggest some small changes in api use but these can wait).

moved page to match script status
added current svn script

Since your script is now in bf-extensions\' svn (contrib|trunk) we have deleted the current attachments to avoid that end-users could reach this page and get the wrong version of your script.
Note that your script may have api changes or small maintenence changes applied in SVN.
Please retrieve your script from SVN before updating SVN to avoid mis-versioned scripts.

Hey, I've got a problem with the script in 2.61. I've imported an LWO file from Doom 3 and it treats two objects as one and destroys the UV coordinates. I can supply the file.
This is on Windows 64.

please do link the file. its needed for testing.

I just tested the file. The mesh itself seems to be loading ok. It looks the same in Blender and in LW Modeler 10.1, a low-res weapon and a bounding box around it (they're both on the same layer so that's why they are one object in Blender, otherwise point orders get lost).

But yes, the UVs didn't load correctly. I'll look at possible causes.

For some reason I couldn't commit my fixes this time, so I attached it here in the meantime.

Here's the change details:
Vertex related data, like UV Maps, would fail to load when the map's name was too long. The map would be added to the mesh, but the returned object wouldn't pass an 'if not' test.

Now when adding the new map to the mesh object, only the last 31 characters of the name are used.

Wow, that is fast! Thank you very much for fixing this!


Due to changes to the api including the merging of bmesh, several addons are outdated.
Please, if you are the author of an addon check your script with blender revision 44256 or newer.
That is builds made After blender 2.62 official release.
I would ask that updates be made to your addon before the Blender 2.63 release.
6-8 weeks away.
This allows time for the api to become more exposed & bmesh to stablize furthur.
If you need help, drop into irc freenode #blenderpython or #blendercoders & feel welcome to ask questions.
At the time of 2.63 release, scripts that are not repaired or in active developement will have their tracker page marked "Closed"
this will not affect your links to the tracker, similar to closing scripts in 2.49b, the page will be still availible & can be re-opened.

Thanks for your understanding & patience during these Exciting Times.

I updated this addon to 2.63 api myself at request of oscurart.
please check your script in svn to make sure all is well.
tested on 5.3 meg import, multiple objects/materials
confirmed by oscurart, different file.

Uv maps are not imported in 2.63 windows x64
file :
and many others.
Hope you can fix it and thanks for that script :)

i got this error when I tried importing some old lightwave version 5 lwo's.

This task was automatically closed as archived as part of migration, because it was determined to be no longer active.

The authoritative list of addons is on the wiki, we no longer have a report for each addon to track bugs and updates. Bugs can be reported individually and assigned to the addon developers. See the Add-ons (Community) project page for more information on the workflow.

Nobody (None) changed the task status from Unknown Status to Unknown Status.Sep 2 2010, 7:08 AM

I'm trying to import this official NASA file, but the imported model only contains vertices. No edges or faces.

I'm using Blender 2.81a... I tried installing this addon, but there is a message that says Upgrade to 2.8x required. But I'm on 2.81a? Perhaps I didn't install it correctly?

I clicked on the SVN Download:

It gave me a script. I saved it using notepad. Is this the correct way? I saved it as a .py and tried to install it in Blender under my addons.

Am I doing something wrong?

I'm using Blender 2.81a... I tried installing this addon, but there is a message that says Upgrade to 2.8x required. But I'm on 2.81a? Perhaps I didn't install it correctly?

I have the same issue in Blender 2.83. I assume this means the plugin needs to be updated for Blender 2.8x, is that correct? If yes, when can we expect this plugin to be updated?

I have a number of old lwo files made in the 1998 Mac version of Lightwave that I'd like to import into blender. Is there any other route to achieve that? I'm merely looking for a way to re-use the models, I don't care about any other features of the Lightwave files.