Posting again after some silence ...
After recent Unity (2018.2.12f1 + some other previous ones) and Octane (126.96.36.1991) updates, we have noticed some unexpected behavior. Simple rendering of a single frame works in a simple project but when trying to record a sequence using Octane's PBR Recorder it produces the following behavior:
1) Octane PBR Recorder fails to use the <0000> suffix tag indicating the frame number. It basically overrides the same file again and again without using any frame number at all (even the first one '0000') ...
2) Unity crashes with a window error saying there is no fix found for such bug/error ...
2.b) Sometimes some messages appearing in the Unity log (please, read at the bottom of this post):
Do you think you can handle this bug soon? We believe it is critical, as this used to work in previous versions. We have tried to go back to previous Octane versions but the problem persisted (maybe a combination of Unity and Octane, we are using latest 2018's Unity).
Please, let us know if you want us to try something for you.
>>> Unity log, repeated 'n' times:
NullReferenceException: Object reference not set to an instance of an object
OctaneUnity.RecorderORBXFileNameGenerator.BuildFileName (OctaneUnity.RecorderComponent recorder, System.String pattern)