LiveDB materials randomly losing sync with images

[vs_matt]

Hi all,

Just wondered if anyone else has had LiveDB materials that they've imported randomly lose sync with images they are linked to? I've had this happen on a couple of projects now. I'm also getting some inconsistency about where images are saved when imported from LiveDB (which may go some way to explaining it) - sometimes they'll appear in the /Images folder, sometimes within a subfolder that it creates (eg. /Images/textures), sometimes in the /Renders folder etc. I haven't noticed a consistent pattern as yet and haven't had a chance to test further.

It's not a massive issue as you just have to drill down into the Octane nodes and reconnect all the images but it is annoying. Anyone else?

Cheers,
Matt

[juanjgon]

The LiveDB textures are unpacked in the current project content images folder. The final texture paths are stored relative to the this content directory, so if you at some point change the content folder, it is easy break the images path.

So lets say that you have your content folder set to "X:\myProject". The default images directory for this content folder should be "X:\myProject\Images". All the LiveDB texture will be unpacked to this directory, sometimes inside other additional folders, but always relative to content.

If you change the images content folder along the projects, or you try to import the material to a project with different content, the plugin is not going to be able to find the textures.

Hope this helps.

Thanks,
-Juanjo

[vs_matt]

Thanks Juanjo. The thing is, this is happening 'on the fly', without changing the content directory. So yesterday for example I did a render, added another camera to render from a different angle and boom one of the LiveDB textures had lost sync with all its images. But only on one texture so very random.

[juanjgon]

Thanks Juanjo. The thing is, this is happening 'on the fly', without changing the content directory. So yesterday for example I did a render, added another camera to render from a different angle and boom one of the LiveDB textures had lost sync with all its images. But only on one texture so very random.

Hmm, weird. I'll try to reproduce this problem here. If you find something reproducible (for example the same problem always with one of the LiveDB material), please let me know.

Thanks,
-Juanjo

[vs_matt]

Will do.

I'm wondering if it's maybe something to do with subfolders in the image folder and octane changing paths.

So for example, if you have a big scene with lots of textures, so you organise them into subfolders eg:
/Images
--> fruit textures
--> vegetable textures
--> other textures

And you setup a texture using images from one of the subfolders, octane then seems to use that path for LiveDB. But then if you setup another texture using an image from another subfolder it then changes the LiveDB path to that subfolder when you import another LiveDB material. I think. But then I don't know why some then lose sync.

Will test more here as well when I get a chance.

[BorderLine]

Yes, same problem here time to time.

[BorderLine]

Pfff !
It's really a problem that loss of link. You work on your textures, you exported nodes by security and suddenly, it's over, the texture is not read. Even if you import the saved nodes, nothing happens, repeat textures.
It's really really annoying. I lose a lot of time
Thanks

[juanjgon]

Can you send to me one of these materials with the texture links broken? Or a scene where you can always reproduce this problem?

I've trying to reproduce this problem here, but without luck so far.

Thanks,
-Juanjo

[vs_matt]

I should be able to spend a little time tomorrow on it, I'll see if I can reproduce in a consistent way.

Thanks,
Matt

[BorderLine]

I'm in production on two projects and i've this problem with the two. I can't reproduct this problem when i want. At this time, just now, two textures disappears. Don't understand !