Failure to write when output folder doesn't exist. about cuttlefish HOT 7 CLOSED

Workaround for now is in scripts to call this before calling cuttlefish.

mkdir -p "$(dirname "$output")"

from cuttlefish.

What version of PVRTexToolCLI and on what operating system were you running? When running PVRTexToolCLI 4.23 (from the 2019.R2 install) on Linux, I get the following error message if the parent directory doesn't exist:

Error: Unable to save texture as requested format, please check the format being used is supported.

I did verify that the same command succeeds when the parent directory does exist.

It's been my impression that tools that output a single file by path (as opposed to providing an output directory) error out if the parent directory doesn't exist. To verify this, I tried a few other tools such as gcc and another texture conversion tool I found online, and none of them create the parent directory for you.

While I agree it can be useful, it's also good practice to make as few changes to the filesystem as possible inside the tool. Since the general trend among similar tools is to not create the parent directories, I would be hesitant to do so for cuttlefish.

from cuttlefish.

Yeah, I found most tools don't create directories including PVTexToolCLI. I was working with a script that was failing when I switched to Cuttlefish, but I found out later it needed that directory creation for PVRTexToolCLI as well. There's a workaround, but it means more scripting instead of keeping it all in C++. EtcTool does have some directory creation calls inside it.

Also I'm on macOS, and make sure to updated to 4.24 of PRVTexToolCLI. The 4.23 versions and below don't handle srGB correctly, and neither does EtcTool. I posted some fixes to EtcTool to the Issues list, but it hasn't been updated in 4 years.

from cuttlefish.

I feel it's better to keep consistent with the conventions used with other command-line utilities, since it offers fewer surprises when working with multiple tools. While it can be useful to create the parent directories for you, it can also be useful to be given an error if you passed it the wrong directory name. (e.g. you get an error if you have a typo in the directory name rather than creating the directory)

Rather than calling mkdir -p "$(dirname "$output")" before invoking Cuttlefish for each texture, I would recommend creating your directory structure at the start of the build process. That is pretty common practice, will provide some protections if you accidentally put something in the wrong place, and will also work more gracefully when integrating other tools into your build process.

from cuttlefish.

I this case I want to let the artists to organize their content they way they feel best, so new folders could appear/disappear at any time. Draconian measures to stuff all textures into a flatter hierarchy aren't always best, but certainly easier for the engine to deal with then.

from cuttlefish.

I was thinking along the lines of building an asset package, but in the case of a tool for artists I agree it would ideally follow the directory structure of their source images.

Since I think the default behavior should stay as it is, as a compromise I can add a command-line argument to have Cuttlefish create the parent directory for you.

from cuttlefish.

You can now use the --create-dir command-line argument in version 2.1.0.

from cuttlefish.