Octane stops rendering after 13 or 17 samples per pixel...

[ROUBAL]

For my own, I submitted some time ago a different problem with opacity textures, even if not set to Zero : once an opacity texture is applied, when changing the opacity texture, Octane Freezes and has to be killed.

Because of that I left aside a project using many opacity textures and requiring many changes for testing (a forest with many different billboard trees).

@ Kubo :

actually it does, it could have something to do with filepaths, hence when you "dumped" all in a single folder (where octane checks anyway when it can't find a resource anyway) it solved. It's worth checking it out.

As I zipped and unzipped the files in a subfolder of my usual project folder, I doubt that it is a path syntax error, because the subfolder would have inherited of the bad path syntax. And before the bug appeared, I always worked with Octane with this same paths structure.

[kubo]

well I thought I had it fixed, but it started crashing again, so I gave it a thought to what abstrax said and took all my alpha maps and changed the black background from 0,0,0 RGB to 3,3,3 and I've been able to render 3 shots with no crash so far, and no other change in the file besides that.
So I'm seending over a beer pack for you Abstrax, I'm not certain if it'll get there just with "Abstrax, Waitakere, New Zealand", but I have faith in the postal service, also you may need to put them in the fridge for a few hours before drinking them. . Thanks, really, I have this contest due thursday and I didn't know what to do.
Also, is looking beautiful, thanks to Octane, and I didn't want / had time to go back to other slower unbiased renderer.
@ Roubal, sorry mate, I got it wrong, I thought that when you unpacked it you did it with out folders, all the images in the root folder where the ocs was. Yet if that was the only change it could be it had trouble locating one file.