Page 1 of 1

LocalDb can not assign materials to new octane materials

PostPosted: Fri Dec 28, 2018 9:29 pm
by eklein
When the LocalDb is window is open the first time it can download a localdb material to the active octane material. This works the first time. Now select a new object with a new octane material. Make a new download from the localdb and still goes to previous selected material, not the current selected material.

The only way to download localdb materials to new octane material after the first time is to close the localdb window and reopen it for every new octane material.

I have tested with 4.01.1 - 16.3.1 and 2018.1 - 17.0. Under Windows and Nvidia rtx2070 with the latest driver.

Re: LocalDb can not assign materials to new octane materials

PostPosted: Fri Jan 11, 2019 9:34 am
by DrawFun
Hi eklein,

Thanks for your report. Issue reproduced and we are going to provide more flexible livedb workflow soon.

Cheers,
DrawFun

Re: LocalDb can not assign materials to new octane materials

PostPosted: Sat Feb 02, 2019 3:05 pm
by eklein
Hi DrawFun,

Any news when the LocalDb workflow will be updated. As it is now every time I have a new material that I select from a object on the viewport I have to close and reopen the LocalDB windows to download a LocalDB material to this new material I have selected.

Re: LocalDb can not assign materials to new octane materials

PostPosted: Wed Feb 13, 2019 9:33 am
by DrawFun
Change the target node tree when fetching livedb will be available in 17.4.