Octane Render's Character Different than whats in Lightwave Tweet

[jmilton]

Hi,

I've exported a few guard character from iClone to Lightwave. It's the same mesh but they have different FBX motions assigned to them. One guard is sitting the other is standing with a idol motion. I have each character set up individually in a different Lightwave scene and I did a Load Items From Scene and imported each character into this existing scene.

The motions work fine in Lightwave when I'm setting them up and scrubbing through the timeline. When I do an Octane render or Open IPR it has the guard with the idol motion sitting doing the same sitting motion.

Lightwave 2019.0.3
Octane version 4.02.1.0 (Feb 12)

What I see in Lightwave

What I see in Lightwave

What I see in Lightwave

[juanjgon]

Hi,

Can you please try to render your scene with the "Instance LW clones" option disabled? You can find this option in the render target root node options panel.

Thanks,
-Juanjo

[jmilton]

Hi Juanjo,

Yes that did that trick. Thanks for the help!

--Jeff

[Lewis]

Juan, that "Instance LW clones" option is very cool feature and helps with VRAM optimization but i wonder is there a way to "de instance "only some meshes 'coz i often in scene have maybe clones which i still like to be treated as instances but maybe one or two id' like to not be treated as instances. Would be maybe good to add that feature to object properties so we could de-instance only some if we want and not all always.

[juanjgon]

Juan, that "Instance LW clones" option is very cool feature and helps with VRAM optimization but i wonder is there a way to "de instance "only some meshes 'coz i often in scene have maybe clones which i still like to be treated as instances but maybe one or two id' like to not be treated as instances. Would be maybe good to add that feature to object properties so we could de-instance only some if we want and not all always.

Yes, perhaps I could add an option in the Octane object properties panel to avoid the instancing, but I need to check how easy is going to be support this with the current plugin architecture. I'll take a look at it after the next 2018.1 plugin build release.

Thanks,
-Juanjo

[Lewis]

Great, thanks.

Basically i'd leave check mark in render target AS IS now but add override in object properties so that those who have applied "de-instance" option would behave as separate clones and not instances.

[jmilton]

Not sure if this is related but I’m having an issue when I’m using Lightwave flocking. I have a character that I’ve set up with MDD motions. I’ve replicated the mesh 4 times and then did an offset on the start frame for each of the characters.

I then used these characters with Lightwave flocking to make 9 guards run down the hill. That works great but the original MDD objects still show in the Octane render. You can see them floating in air all clumped together in the right of the screen shot. If I set them to ‘Hidden from Camera’ all of the characters disappear.

They don’t show in the native LW render since I have the objects set to hidden. They only show in the Octane render. I have Instance LW clones disabled in the Octane Render Target.

Thanks,
Jeff

[juanjgon]

You are going to need to "hide" the master objects moving them out of the camera or scaling them near 0.0. Currently it is not possible to disable the objects to be instanced.

Thanks,
-Juanjo