Full Version: Pivot Point issue

Show messages: All  1  2-20

HI Yanus3D, yes the LWO pivot point bug (Pivot point for mesh object in LWO export not scaled when "Scale output units to meters" enabled) will be fixed in the next v5 build.

- Michael

---

Thanks!
later will for ask for more features. I would like to have some Quality of Life when exporting procedures...
Just simple question: how much you can change LW Exported library?
What you can do with this library module? (like operate with Layers, smoothing treshold, etc)

---

Hi Yanus3D,

re:
> Just simple question: how much you can change LW Exported library?

It's all my own code so I can change any of it.

But it is not a goal to try and replicate a set of polygon mesh editing tools directly in the exporter.

- Michael

---

Message 11999.5 was deleted

---

...so even better if you use own code!

1. I would like to have one layer after exporting.
MoI produce like tens of them (its coming down from Rhino system probably)
Maybe at first you can create one Layer as option in MoI LWO exporter (I suggest make it fix, because these layers are useless)

2. Also another option:
Is annoying that MoI pass down smoothing surface threshold at 20% for all surfaces (this probably comes somehow as default surface option from Rhino...)
This is of course again next useless parameter and all surfaces should have no smooth threshold at all.

Attachment with both "issues"

---

Hi Yanus3D,

> 1. I would like to have one layer after exporting.
> MoI produce like tens of them (its coming down from Rhino system probably)
> Maybe at first you can create one Layer as option in MoI LWO exporter (I suggest make
> it fix, because these layers are useless)

Do you mean having just one surface in the LWO file so everything will be the same render color?


> 2. Also another option:
> Is annoying that MoI pass down smoothing surface threshold at 20% for all surfaces (this
> probably comes somehow as default surface option from Rhino...)
> This is of course again next useless parameter and all surfaces should have no smooth
> threshold at all.

I can put in an option in moi.ini to not write the smoothing angle chunk.

- Michael

---

HI

"Do you mean having just one surface in the LWO file so everything will be the same render color?"
- no, Just when export we get one layer instead many (attachment) Lightwave has nice layer organizing system which of course we use (like Walls, windows, ceiling, etc, these layers names no surface names) but after MoI we gat like hundreds of them (this comes from Rhino because Rhino/Autocad/other similar has different structure modeling similar to one layer one primitive object)


"I can put in an option in moi.ini to not write the smoothing angle chunk"
Yes!

Image Attachments:
Layers_multi.png  layer_one.png 

---

Hi Yanus3D,

re:
> - no, Just when export we get one layer instead many (attachment)

Do you get what you want here if you set the same object name on all objects in MoI and set Options > Import/Export > "Combine same named objects" ?

To set the same object name on all objects do Ctrl+A to select all, then click on the object name here:


- Michael

Image Attachments:
SetObjectName.jpg 

---

Sorry, I think I made a typo.

So, once again, I will explain with a list of the actual statuses.
After exporting from MoI to the LWO format and opening it in LightWave, we get:

- No UV maps and vertices (beta version of MoI) — GOOD
- Smoothness threshold 20% — BAD (you mentioned a future update)
- Surface names passed from Rhino are good, I have exactly same surface naming—we know how to handle this in Rhino. Originally, you do not receive surface names and have to work with just one surface name, but the guys who model for me know how to manage this (No big deal, just slightly different procedures when modeling.. I will have question about that becaouse propably you can do it in different way, better (now MoI does it in bad way but I believe it can be done corectly) From now we do it it in Rhino.
- Issue with Pivot Point: BAD (you mentioned a future update)
- A massive number of LW layers (if the object is heavy, it can exceed 50 layers) is problematic. I suggest forcing the exporter to include only ONE LAYER (the first in the list in LW).
- Merge points if possible. The exported LWO model from MoI has exploded polygons, which is problematic. (not sure this possible)



Thank you!

---

Hi Yanus3D,

re:
> - A massive number of LW layers (if the object is heavy, it can exceed 50 layers) is problematic.
> I suggest forcing the exporter to include only ONE LAYER (the first in the list in LW).

I'm not sure if I'm understanding this one yet because of the different terminology in each app.

MOI does not have anything called layers.

Rhino has something called Layers, when you open a .3dm file from Rhino into MOI, the layer list in Rhino will become the styles list in MOI.

When you export from MOI into a polygon mesh format for rendering, the styles list in MOI will become the materials list in the rendering program.

In LWO format there is a thing called Layers ("LAYR" chunk) where geometry like vertices and faces is stored.

In Rhino and MOI the thing that contains geometry is called an "Object" which can have an object name.

When you export from MOI to LWO, the object list and object names in MOI will become a list of 'LAYR' chunks in the .lwo file.

There is an option in the MOI export settings that controls how objects in MOI with the same object name are written. That's under Options > Import/Export > "Combine same named objects" checkbox (at the top, it is used by multiple formats).

If "Combine same named objects" is set, then every object in MOI that has the same name (other than a blank name) will combine together into one 'LAYR' chunk in the LWO file.

So if you want only one 'LAYR' chunk in the LWO file, you should be able to do that now by setting the same name on all objects in MOI before doing the export and also have "Combine same named objects" enabled.


re:
> - Merge points if possible. The exported LWO model from MoI has exploded polygons, which is problematic. (not sure this possible)

To get a watertight mesh the edge in the CAD object must be a joined edge shared by 2 faces. Then also the "Weld vertices along edges" controls whether vertices for each face will be separate but stacked on top of each other or whether they will reference the same vertex.

- Michael

---

I upload for you model to show "issue"
After opening it in Lightwave I see multiple layers (this model is light but you can imagine something bigger...)
surfaces are correct (guys from Rhino use one layer with multiple surfaces names - thats why I get correct surfaces in LW, otherwise , in traditional way I get one surface name)
Topology in Rhino with layers/names is different than in Lightwave. This is not issue and we can deal wit it. Issue is multilayer construction after export from Moi.
In attachment object R5 for test and screenshot from LW.

Attachments:
whirlpool 1.3dm

Image Attachments:
Screenshot 2026-05-20 095409.png 

---

Hi Yanus3D, please try the attached .lwo , does it have the LightWave layers how you want?

- Michael

Attachments:
whirlpool 2_lwo.zip

---

Yes!
That`s correct export
One layer only.

Image Attachments:
Screenshot 2026-05-20 114330.png 

---

Hi Yanus3D,

re:
> Yes!
> That`s correct export
> One layer only.

Great! To get that result, make sure "Combine same named objects" is turned on here under Options dialog > Import/Export :



Then set the objects you want combined to have the same object name before exporting.

To do that, use Ctrl+A to select all, then click on the object name here and set to any name other than blank:



If you then generate your .lwo file you should get the same one layer result.

- Michael

Image Attachments:
CombineSameNamedObjects.jpg 

---

Yes, that`s works!
So I was thinking (I hate extra clicks in pipeline) is possible to do automatically?
Simple button in LW Exporter for it.....

---

Hi Yanus3D,

re:
> So I was thinking (I hate extra clicks in pipeline) is possible to do automatically?

Yes, you can set up a shortcut key that will do those steps automatically.

To do that go to Options > Shortcut keys and add a new one. For the Command part of the shortcut key put in this:

script:
moi.geometryDatabase.getObjects().setProperty( 'name', 'Layer' );
moi.geometryDatabase.saveAs( 'filetype=lwo' );

- Michael

---

Thank you!


But I am thinking about a fixed solution, such as adding a checkbox in the export menu. Could you add that?
There are too many procedures involved in exporting and importing, and I want to avoid unnecessary clicks and shortcuts.
I ask this because I understand when someone does it casually, but in our case, we have multiple projects running simultaneously, a huge data exchange between departments, and every extra click counts.

---

Hi Yanus3D,

> I ask this because I understand when someone does it casually, but in our
> case, we have multiple projects running simultaneously, a huge data exchange
> between departments, and every extra click counts.

You only need to set up the shortcut one time, after that using the shortcut is just one key instead of 2 clicks.

Actually the shortcut saves even more clicks than that because it sets the file type to .lwo automatically as well.

- Michael

---

O yes...now works perfect :)
So I wait for next update with fixed Pivot.
Thanks again!

Can you make a list what I can put in script for Lightwave format?

---

Show messages: All  1  2-20