Image Texture Node missing C4D's "Copy Assets to Project"
Posted: Wed May 04, 2022 10:39 am
I posted this in the Facebook group and was made aware that I should use this forum as FB is not an official feedback channel.
When I create a material and add an image texture node, it immediately opens a search file window and prompts me to select a texture. So far so good.
When I select a texture, it creates an ABSOLUTE path to said texture. In older octane version this automatic search file window wasn't a thing and you had to press the "..." first.
My problem is, that this behavior prevents C4D from asking if I want to copy my assets to the project structure. Standard C4D behavior is a prompt that asks me if I want to copy the texture to the "tex" folder -> if I deny this, it creates and absolute path.
Absolut paths might make sense for global resources that are used in many projects, e.g HDRI files, surface imperfections, etc.
But there are dozens of cases where one would need customized, specific texture maps for a project and it would be beneficial to copy them to the projects TEX folder. But even if I copy the texture to the TEX folder manually and select it in that automatic dialogue, it creates an absolute path to that texture.
I know this was implemented to save some time, but I talked to some users, many just click on the "..." option again, select the same texture to get the normal C4D prompt that asks to copy the assets. Others just don't use that feature at all and copy everything to the TEX folder manually... or they drag and drop the files from an explorer window that they have always open on a secondary screen. This could all be prevented if octane wouldn't just override / suppress the C4D prompt that asks to copy the files.
TL;DR, a video:
Also, for those who only use absolute paths and wonder why I want an relative path:
If I copy that project to a new drive, change the name or location of the project I have to go through every material or use the octane texture manager to fix all the path names.... it's very crucial to use relative paths.
When I create a material and add an image texture node, it immediately opens a search file window and prompts me to select a texture. So far so good.
When I select a texture, it creates an ABSOLUTE path to said texture. In older octane version this automatic search file window wasn't a thing and you had to press the "..." first.
My problem is, that this behavior prevents C4D from asking if I want to copy my assets to the project structure. Standard C4D behavior is a prompt that asks me if I want to copy the texture to the "tex" folder -> if I deny this, it creates and absolute path.
Absolut paths might make sense for global resources that are used in many projects, e.g HDRI files, surface imperfections, etc.
But there are dozens of cases where one would need customized, specific texture maps for a project and it would be beneficial to copy them to the projects TEX folder. But even if I copy the texture to the TEX folder manually and select it in that automatic dialogue, it creates an absolute path to that texture.
I know this was implemented to save some time, but I talked to some users, many just click on the "..." option again, select the same texture to get the normal C4D prompt that asks to copy the assets. Others just don't use that feature at all and copy everything to the TEX folder manually... or they drag and drop the files from an explorer window that they have always open on a secondary screen. This could all be prevented if octane wouldn't just override / suppress the C4D prompt that asks to copy the files.
TL;DR, a video:
Also, for those who only use absolute paths and wonder why I want an relative path:
If I copy that project to a new drive, change the name or location of the project I have to go through every material or use the octane texture manager to fix all the path names.... it's very crucial to use relative paths.
