I'm using Cinema 4D R20 .059, Octane version 4.04 RC4 R2.
I need to use a version earlier than 4.05 due to conflicts with a GSG material pack.
What sort of workarounds are available for this?
~N
Activation Error "This build is not supported anymore..."
Moderators: ChrisHekman, aoktar
4.05-R7 should fix it!
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
-
helloimneil
- Posts: 33
- Joined: Sat Apr 01, 2017 9:44 pm
Thanks aoktar! I'll give it a shot and report back.
Could you explain a bit more?helloimneil wrote:No luck, aoktar.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
-
helloimneil
- Posts: 33
- Joined: Sat Apr 01, 2017 9:44 pm
Certainly.
GSG has created, at this moment in time, two material packs for Octane (and other renderers). In order to use these, their directory location must be linked into the LocalDB filed within Octane Settings > Other > LocalDB.
When I load certain materials (not every material is affected) some aspect of their setup fails to load. One example is a fabric material "D_Bed_Sheet_Gray" (for reference), all maps *except* the normal loads. Where ordinarily the data field would list the image's dimensions, I instead I get 'Error Loading Texture'.
Oddly, though, when I load another fabric material, take '"D_Cloth"Gingham_Blue", for example, all image maps load as expected.
Something I was trying last night was to make duplicates of each of the image textures, moving them to a new location (a 'test' folder, same drive, different directory) and seeing if I could load these duplicated maps into the channels where the Error Loading Texture message is present. However, this also did not work.
As a part of the installation procedure for these material packs, I initially linked the Everyday Material Collection (EMC) within the LocalDB portion of Octane's settings. Once these loaded, I then selected the folder location for MSMC (Modern Surface Material Collection) in LocalDB. Both of these show up in LocalDB, however, it almost seems like the assets that are apart of the EMC are the ones which are affected.
Should I consolidate the directories into a single folder where each are present, as opposed to first linking one asset folder, and then selecting the second?
I hope I've given you enough information to work with, if not, I am more than happy to clarify anything else that may be of benefit to you in assisting me with troubleshooting.
GSG has created, at this moment in time, two material packs for Octane (and other renderers). In order to use these, their directory location must be linked into the LocalDB filed within Octane Settings > Other > LocalDB.
When I load certain materials (not every material is affected) some aspect of their setup fails to load. One example is a fabric material "D_Bed_Sheet_Gray" (for reference), all maps *except* the normal loads. Where ordinarily the data field would list the image's dimensions, I instead I get 'Error Loading Texture'.
Oddly, though, when I load another fabric material, take '"D_Cloth"Gingham_Blue", for example, all image maps load as expected.
Something I was trying last night was to make duplicates of each of the image textures, moving them to a new location (a 'test' folder, same drive, different directory) and seeing if I could load these duplicated maps into the channels where the Error Loading Texture message is present. However, this also did not work.
As a part of the installation procedure for these material packs, I initially linked the Everyday Material Collection (EMC) within the LocalDB portion of Octane's settings. Once these loaded, I then selected the folder location for MSMC (Modern Surface Material Collection) in LocalDB. Both of these show up in LocalDB, however, it almost seems like the assets that are apart of the EMC are the ones which are affected.
Should I consolidate the directories into a single folder where each are present, as opposed to first linking one asset folder, and then selecting the second?
I hope I've given you enough information to work with, if not, I am more than happy to clarify anything else that may be of benefit to you in assisting me with troubleshooting.
I know this is a pretty old thread, but I've been having the same issue and it's driving me crazy. I don't understand why it is happening. I try to open the materials but the textures aren't linked up, and I can't even relink them because the EMC files are all ORBX. Has anyone figured out a solution here?