OTOY Forums

This is the first time I have witnessed this, but earlier today I was changing the materials on a model from standard to Octane.
I just noticed that a series of folders have been created off the root of my hard drive, one for each of the materials used and named after the materials.
Most of them were empty but a few had material files in them.
I'm not sure what I did that produced this effect, but it creates clutter and I don't see the benefit in it.
Thank you.

buggy wrote:This is the first time I have witnessed this, but earlier today I was changing the materials on a model from standard to Octane.
I just noticed that a series of folders have been created off the root of my hard drive, one for each of the materials used and named after the materials.
Most of them were empty but a few had material files in them.
I'm not sure what I did that produced this effect, but it creates clutter and I don't see the benefit in it.
Thank you.

Did you use LiveDB materials?
If so, what texture path do you use for it?

Yes, they were liveDB materials. I have never used the textures path and had always assumed that the plugin was reading the liveDB materials from the cloud and have not noticed it creating local folders before. At what point does this happen?
I can see why one might want them local so that any bitmaps can be stored and edited.
I just went through the manuals to see if I can understand how it works but I didn't find the information.

In most cases the folders were empty because there are no bitmaps associated with them. Unless there are bitmaps I don't see the point in it creating a folder for the material.
In some cases I made copies of the livedDB plastic materials to other slots in the Material editor and changed their color settings. Does it create new folders for each of these too?

My textures path is currently blank. Do I need to set it for each scene I create or can I set it once to create one local repository that all my scenes refer to?
All my assets are on my E: drive, but I just checked and in addition to creating material folders in the root of E:, there are also some in C:

Forgive my ignorance of all this! I'm sure it's all clear to the power users but I'm still grasping some of the features.

buggy wrote:Yes, they were liveDB materials. I have never used the textures path and had always assumed that the plugin was reading the liveDB materials from the cloud and have not noticed it creating local folders before. At what point does this happen?
I can see why one might want them local so that any bitmaps can be stored and edited.
I just went through the manuals to see if I can understand how it works but I didn't find the information.

In most cases the folders were empty because there are no bitmaps associated with them. Unless there are bitmaps I don't see the point in it creating a folder for the material.
In some cases I made copies of the livedDB plastic materials to other slots in the Material editor and changed their color settings. Does it create new folders for each of these too?

My textures path is currently blank. Do I need to set it for each scene I create or can I set it once to create one local repository that all my scenes refer to?
All my assets are on my E: drive, but I just checked and in addition to creating material folders in the root of E:, there are also some in C:

Forgive my ignorance of all this! I'm sure it's all clear to the power users but I'm still grasping some of the features.

Standalone stores all downloaded textures in ocs file. For 3ds max it is bad approach.
You can use one place for all your projects.
If you make a material copy, you don't need to create a new folder. material copy will refer to the same place as original.

Thank you. I set the materials path in the field so there should be no surprises now