Octane doesn't save EXR(Octane) files

[Aleksei]

Hi,
For me it looks like a bug, but maybe I'm doing something wrong?
After an image finished rendering in EXR(Octane) format the file is not written to folder.
If I change format to any other including regular EXR everything works as expected. The passes which I render are not stored only for the EXR(Octane). At the same time, the correspondent folders (for different passes) are created successfully.

I tried it with Octane versions 2021.1 and 2021.1-(R2). The same behaviour in both cases.
PC's tech specs a listed in my signature.
I would like to use Cryptomatte, so there is no option for me to switch to another format. Please, help.

Here are my render settings:

[aoktar]

Have you tried simple paths without $take/etc..?

[Aleksei]

Ok, I've just came back here to write that I know what causes the issue. Occasionally I noticed this post from another topic:

I found out why
exr (octane) files are not displayed in Chinese paths
Can this be fixed quickly?

...and realized that I have a space symbol in one of the folder names (in that part of path which is blurred in the screenshot).
So it looks like a bug, because it never happened with any previous versions of Octane (using spaces in folder names for years, as well as Octane).

[aoktar]

Could you please show your path? I've tested it nothing seems wrong on my tests. Also there's not any revisions on my side to cause this. I cannot know the changes out of plugin side.

[elsksa]

...and realized that I have a space symbol in one of the folder names (in that part of path which is blurred in the screenshot).
So it looks like a bug, because it never happened with any previous versions of Octane (using spaces in folder names for years, as well as Octane).

Hello,

While I do not know with exactitude how does Octane for Cinema 4D behaves in that regard, it is an "industry standard"/"protocol" to not have both spaces and special-characters (including cyrillic, arabic, farsi, hanzi/kanji, etc... alphabets).

Therefore, CamelCase and underscore are often used and recommended, if not exclusively, in file naming convention with English as the universal language.

[Aleksei]

Could you please show your path? I've tested it nothing seems wrong on my tests. Also there's not any revisions on my side to cause this. I cannot know the changes out of plugin side.

Here is the first problematic part of the path: F:\projects\ССС0004 JP Morgan\
(F is an external SSD, if it matters).

it is an "industry standard"/"protocol" to not have both spaces and special-characters

I know about that and I was following this standard whole my life. It was espcially important while working on old versions of Windows. But a lot of years passed and I noticed that neither Windows nor other apps have these problems any more and I skipped this practice with time. Now, I guess, I'm going to return back to it.

[aoktar]

What happens if you don't use "ССС" characters in file path? It seems the issue. Are they russian or so?

[Aleksei]

OMG! It's in Russian indeed!
And I didn't know about it until now.
The matter is that it's very easy to type the letter "C" in Russian instead of English accidentally (if this is the only one letter which you have to type).
And here is why:

[abstrax]

Thank you for the report. It will be fixed in the next release (2021.1.1).

[InTao]

Cinema 4d R25
Octane render version: 2021.1-R2
I also encountered the same problem when exporting EXR (Octane). When there is a Chinese path or the file name has Chinese, the file cannot be rendered, or the rendered file name is garbled. There will be no problems when I switch to EXR. I hope to fix this problem as soon as possible.