It's a crucial feature, I'm also hoping to see it implemented soon.

Maybe try changing units under scene settings - in the past some users reported that Metric (or None? Can't remember...) don't work, although I've never had any issues with that...

I made a quick test and put a correctly named texture into a folder with some Polish characters, and System Console gave me the same message - I suggest you check all your folder names as well, it's probably best to avoid non-English characters in everything Octane-related...

From your description I can only tell that I haven't ever had such a problem, unfortunately. Let's just see what System (not Python) Console says - go to Window > Toggle System Console when the problem occurs.

Hi,
this kind of behavior might indicate problems with texture paths - either lost or containing non-English characters, but please post the error message (Window > Toggle System Console) so that we know more details.
Cheers
Szymon

Hello,
It happens in 2.25 - 9.9 version on Win 10. I've managed to save the interactive session image a few times - only when I set the output path to desktop, but even then I get random crashes. Paths other than desktop don't work for me.
Saving interactive session images is a super cool feature ...

Yes, I have the same with materials called "Material". In my case, changing material's name fixes the problem.

hello, you can attach the file blender?
Sure thing:) Have a look at "edge emission.blend" attached below.

i only want the "outer" edges of an object
Maybe try starting with something like this:
edge emission (compositor).jpg
... and then composite this with your rendered image. I'm not sure ...

Hello lakris,
maybe the wireframe modifier or fallof texture could do the job? Cheers,
Szymon

OK now I get it - all I need to do to restore the camera response for F12 rendering is set it inside Blender's Color Management. Actually, I like this approach much more than the previous one, thank you JimStar!