So in an earlier question, I had about the file path of saving, I wrote that I managed to get the kick renderer to render the textures that were in the same directory as the .ass file but now for some reason it will not find the textures, even when they are as said, in the same directory as the .ass file. I have no idea why it suddenly stopped finding and even why it found the texture when they were in the same directory.
So my question is now if there is a command that either paths to specific textures meaning I would have to path to every texture used or if there is a command that paths to a directory of the used textures so kick can automatically find them?
What's the filename in the ass file? Is it an absolute path? Or a relative path?
If it's a relative path, then you can use options.texture_search_path
Otherwise, you can use arnold path mapping
the name on the .ass file is DBF0001 and I believe it is a relative path as I exported the .ass file with Preserve references unchecked.
When I tried -set options.texture_search_path to the file path of the folder that holds all the textures, I got this
00:00:00 280MB WARNING | [kick] couldn't find parameter named 'texture_search_path' for -set
Sorry, I mean what is the image.filename in the ass file ?
image
{
name aiImage1
filename "S:\TEST\assets\example.tx"
color_space ""
ignore_missing_textures on
missing_texture_color 1 0 1 1
}
And it's kick -set options.texture_searchpath
kick -info options | findstr search
STRING texture_searchpath
STRING procedural_searchpath
STRING plugin_searchpath
I see, here is one of very many textures file path
image
{
name Motherbase_Airship_With_others:Person_transport_Airship:file1
filename "D:/Dokument/Maya_2/default/sourceimages/Perontransport_standardSurface1_BaseColor.png"
color_space "sRGB"
filter "smart_bicubic"
swrap "periodic"
twrap "periodic"
sscale 1
tscale 1
soffset 0
toffset 0
uvset ""
ignore_missing_textures on
missing_texture_color 0.5 0.5 0.5 0
}
Ok, absolute paths, so you want to use path mapping.
Do you mean something like "-set options.texture_pathmapping" or do you mean something when I am exporting the .ass file? I have no idea how to use path mapping or even where I find it or how I write it if it is inside of kick
@Technics_Man wrote:
Do you mean something like "-set options.texture_pathmapping" or do you mean something when I am exporting the .ass file? I have no idea how to use path mapping or even where I find it or how I write it if it is inside of kick
Nope, I mean using ARNOLD_PATHMAP. There was a link in my first reply that mentioned path mapping.
If re-exporting the ass files is an option, then export relative paths.
To do that, you have to clear the Absolute Texture Paths check box: https://docs.arnoldrenderer.com/display/A5AFMUG/Search+Path
I re-exported the ass files with Absolute Texture Paths unchecked yet it still did not find any of the textures when the ass files and texture files were in the same folder
Here is one of the many file paths that are with the newly exported ass files
image
{
name Freighter_Airship16:file7
filename "Solar_panel_roughness.png"
color_space "sRGB"
filter "smart_bicubic"
swrap "periodic"
twrap "periodic"
sscale 1
tscale 1
soffset 0
toffset 0
uvset ""
ignore_missing_textures on
missing_texture_color 0.5 0.5 0.5 0
}
So I have found the solution and it was that the texture files do not need to be in the same place as the ass files when you have exported with Absolute Texture Paths unchecked, but rather in the same place as the kick.exe.
Once you uncheck absolute texture paths, if you don't want to place them in your working directory (kick's directory in your case) you then need to use the -set options.texture_searchpath that Stephen mentioned to find the textures.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.