LiveDB .orbx file Tweet

[joseburgos]

I exported materials from Daz Studio which created the .orbx file, into a folder in my LiveDB folder.
When I opened them in Lightwave 2018 LiveDB Local, they all say Data I/O and have no thumbnail. I right click to create thumb nail but I have no direct way to know which material it is.
I opened one of the .orbx files and I read this at the top of the file;
<graph id='1' type='1' name='Data I/O'>
<graph id='605' type='1' name='Looking Back Earrings: defaultMat, Earring' position='0 0'>
Here I can see Lightwave is using the graph id=1 name and not the 605 name.

So I opened Octane standalone and looked at these files there and they had same Data I/O name but at least in Octane, if I hover over the thumbnail, it says the name of the material.
In Lightwave 2018 it does not show the name when I hover over it.

Right now my workaround is to load in one of the Data I/O into the LiveDB materials node and then press Edit Octane Material. Then I right click and choose Import and then steer to to where my local db files are located to list all the .orbx by the name I saved them as and load them in.
Very tedious to say the least

So is there something I did wrong?
Is there a way to fix them?
Worse case, once I figure out Data I/O is which, can I change the LiveDB name?

Thank you,

[joseburgos]

Any ideas Juan?

[juanjgon]

Let me try to check the LiveDB feature here. I'm not sure to fully understand your problem, but at least I'll check if it works fine exporting materials from the Standalone.

Thanks,
-Juanjo

[joseburgos]

Here is a video I made showing what I am doing and I just noticed not only are they all called Data I/O but they do not work if I right click on them and choose Import. But if I enter Edit Octane Material, and import the material from the LocalDB list, it works.
https://www.youtube.com/watch?v=-l47lebZ0iQ

[juanjgon]

What happens if you try to import one of these materials in the Standalone. I'm testing the plugin using materials exported from the Standalone and they don't have this problem.

Can you please attach one of these materials to check it here?

Thanks,
-Juanjo

[joseburgos]

Yes in stand alone it works fine

[joseburgos]

Here is one

[joseburgos]

So I did another test of saving out the material node out of Octane Stand Alone into LocalDB. I then restarted Lightwave 2018 and opened the LocalDB. Since it was saved and named in Octane, the name shows up correctly in LocalDB but it does not work just like before. I have to edit the octane material and then import the same material but the file, like before and then it works.

[juanjgon]

Hi,

I've just fixed a bug in the LiveDB/LocalDB feature related to all the imported texture maps paths, that were broken due to a change in the SDK. With this fix I can import your material without problems so far, as you can see in the attached image.

I'll release a new plugin build along this week with this fix.

Thanks for reporting it!
-Juanjo

[joseburgos]

Thank you very much Juan and I'm looking forward to testing it