I am getting this message when I try to open LiveDB. Is the service down?
Is there a fallback option where we can download all the current materials to our local Octane materials folder and have the plugin access them from there?
Thanks
"Cant access to LiveDB" message
Forum rules
Please post only in English in this subforum. For alternate language discussion please go here http://render.otoy.com/forum/viewforum.php?f=18
Please post only in English in this subforum. For alternate language discussion please go here http://render.otoy.com/forum/viewforum.php?f=18
Any idea why this would be happening or what I can do about it?
The only thing that I recently changed was my textures path. I thought I had set it up for a folder named E:\...\OctaneMaterials
but at some point I found that it was set for E:\...\Octane\ and I had materials in both folders. I consolidated them all back into \OctaneMaterials and changed the textures path in the plugin back to that. I think things were working fine after this until yesterday when I could no longer open the LiveDB.
Thank you.
The only thing that I recently changed was my textures path. I thought I had set it up for a folder named E:\...\OctaneMaterials
but at some point I found that it was set for E:\...\Octane\ and I had materials in both folders. I consolidated them all back into \OctaneMaterials and changed the textures path in the plugin back to that. I think things were working fine after this until yesterday when I could no longer open the LiveDB.
Thank you.
Win 8.1 | 2x GTX780 6GB RAM + 1x GTX 660 | Intel i7 | 16GB RAM | 3DS Max 2011
Does you standalone works properly with LiveDB?buggy wrote:Any idea why this would be happening or what I can do about it?
The only thing that I recently changed was my textures path. I thought I had set it up for a folder named E:\...\OctaneMaterials
but at some point I found that it was set for E:\...\Octane\ and I had materials in both folders. I consolidated them all back into \OctaneMaterials and changed the textures path in the plugin back to that. I think things were working fine after this until yesterday when I could no longer open the LiveDB.
Thank you.