Hello,
I have an issue since many month now and it didn't happen with older versions of Octane (I mean V4).
On all my project, every time I close/re-open them I have "Texture Loading Error", randomly on any texture.
I didn't move the path of those textures (I'm not that stupid) but it keeps randomly showing "Texture Loading Error".
I have a project with quite many frame to render, I noticed at half the time that the HDRI was missing from the render images. When I checked back in the C4D scene, the HDRI was "Texture Loading Error"... Whereas it was working perfectly before I closed and repoened the scene ! Also, the HDRI missing file didnt appear in the Texture Manager, which I carefully checked before triggering the render (because so used to that missing texture issue).
But now I want to understand what is the problem, I can't be the only one, Am I doing something wrong ? Is it a C4D problem or an Octane one ?
It is veeeeery inconvenient in production, espcecially considering that I do not change those texture paths !
Thanks,
J.
C4D R20 / Octane Studio 2020.1.4 / Nvidia Studio Driver 451.48
Octane/C4D "Texture Loading Error"
Moderators: ChrisHekman, aoktar
- jeremyshin
- Posts: 106
- Joined: Thu May 04, 2017 5:59 pm
And it happened again today, randomly, while working, some "Error loading texture".
Relinking them from the Project Asset Inspector doesn't help, Octane doesn't update the path and keep showing "texture loading error". I have to relink all maps from node editor one by one.
It happens suddenly while working, all my path are clean and I didn't move the files.
Relinking them from the Project Asset Inspector doesn't help, Octane doesn't update the path and keep showing "texture loading error". I have to relink all maps from node editor one by one.
It happens suddenly while working, all my path are clean and I didn't move the files.
Check the image files in picture viewer, it can be corrupt
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
- jeremyshin
- Posts: 106
- Joined: Thu May 04, 2017 5:59 pm
I have no image in the picture viewer.
It just happened a second time after a crash for memory.
I update all the links from Asset Manager but Octane can't generate back the textures, I have hundreds of path to relink manually and I don't have a time to care of that bug. It is a non sense.
It just happened a second time after a crash for memory.
I update all the links from Asset Manager but Octane can't generate back the textures, I have hundreds of path to relink manually and I don't have a time to care of that bug. It is a non sense.
- jeremyshin
- Posts: 106
- Joined: Thu May 04, 2017 5:59 pm
For the information Aoktar,
I transferred the C4d file and all assets to another computer, I was able to relink all the maps correctly through the Asset Inspector. Octane was able to load all those maps correctly.
I then saved the C4D file with a new name, re-transferred to the original machine, opened the C4D file, relinked the maps and this time it worked...
I transferred the C4d file and all assets to another computer, I was able to relink all the maps correctly through the Asset Inspector. Octane was able to load all those maps correctly.
I then saved the C4D file with a new name, re-transferred to the original machine, opened the C4D file, relinked the maps and this time it worked...
- Aymeric_FX
- Posts: 20
- Joined: Wed Jan 15, 2020 8:06 am
I've had this problem with Octane for years now. I've emailed numerous times, never getting any solutions. Happens to every project I have. Work on it, save and close. Go to bed, reopen first thing in the morning, random textures all disconnected, project asset inspector only links some. bloody annoying. Especially when you have hundreds of textures. Sometimes when you hit render, one will just disconnect right before you knowing, so when you return, guesssss whattttt.
Before you suggest its something to do with my project files, textures or computer. I've got 4 computers, all having the same issues on different projects with different textures. Worked at over 5 studios, same problem there. So its an Otoy problem for sure.
Before you suggest its something to do with my project files, textures or computer. I've got 4 computers, all having the same issues on different projects with different textures. Worked at over 5 studios, same problem there. So its an Otoy problem for sure.
Feeding your topics with some pictures from issue that will be much appreciated. Otherwise we may be talking about something different, can't know your brain.
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
- jayroth2020
- Posts: 488
- Joined: Mon May 04, 2020 7:30 pm
Use Globalized filenames, as these will be an absolute reference to your texture. You can select the textures via Window > Project Asset Inspector and then choose Asset > Globalize Filenames from the menu. Then, go to Octane Dialog > Materials > Octane Texture Manager and refresh the file list.
Puget Systems / Intel Core Z790 ATX / RTX 4090 / Cinema 4D
- Exactly13_1
- Posts: 3
- Joined: Mon Dec 21, 2020 4:57 pm
- Location: Kent, UK
Im getting the same issue and tried what you say above but still no joy.jayroth2020 wrote:Use Globalized filenames, as these will be an absolute reference to your texture. You can select the textures via Window > Project Asset Inspector and then choose Asset > Globalize Filenames from the menu. Then, go to Octane Dialog > Materials > Octane Texture Manager and refresh the file list.
The Real Path in the octane texture manager is correct but the suggested path still stays with the old reference.
As you can see, there is still an error loading texture. See picture.
Am I missing some step to fix this?
Any help appreciated. Many thanks.
C4D R26.014 | Octane 2021.1.4-R4 | Windows 10 PRO | RTX3090 | AMD TR 3960X 24 Core | 128GB RAM
- jeremyshin
- Posts: 106
- Joined: Thu May 04, 2017 5:59 pm
Try this:
1. Copy all your scene in a new file, save with new name
2. In your new scene directory create a "tex" folder
3. Drag all the textures you use in the scene into that folder (yes I know it creates useless copies on the disk)
4. Go to the Project Asset Inspector and relink all the textures to your "tex" folder.
You should be good to go.
1. Copy all your scene in a new file, save with new name
2. In your new scene directory create a "tex" folder
3. Drag all the textures you use in the scene into that folder (yes I know it creates useless copies on the disk)
4. Go to the Project Asset Inspector and relink all the textures to your "tex" folder.
You should be good to go.