OTOY Forums

When trying to start a Recording, we are getting this error. It's happening so often that it gets frustrating. We then reload the scene, change nothing, and it works. But it'll often get the error 9 times out of 10 tries, it's very frustrating. Once the capture starts it works great. We are recording based on Frames, starting from example frame 50. We get the error no matter how many frames we render, frame 50 to 50 or frame 50 to 600.



Unity 2018.2.17, Octane 1.2.0.1362, Windows 10.

I cannot recreate this issue on my end.

Is this for every scene or for a specific scene you are using?
If it only happens for a specific scene, could you PM me your project?

We had it happen in two scenes (which unfortunately I don't think we can send, as our Unity app and those scenes are confidential). Of our two scenes, it happened much more often on the more memory-intensive scene (that required using system memory in addition to 8GB GPU RAM). Our theory is it may be because we used multiple Unity cameras one-at-a-time, assigning them to the PBR Renderer camera field and then starting the render, but internally the render losing track of that camera before the rendering started. Because sometimes we would get the null exception, then re-drag the camera into the PBR Renderer camera field (on top of the old one), do the render again, and the render would work that time.

If the rendering actually started happening, the problem wouldn't happen at all.

Ill check if it can recreate the issue by reassigning cameras.

I have not been able to recreate this issue, even with larger scenes that use out of core.

Would it be possible for you to create an example scene that has the issue that isnt confidential?

I'm having this same problem.
What kind of file would be helpful to post? I'd be happy to.

bwatanabe wrote:I'm having this same problem.
What kind of file would be helpful to post? I'd be happy to.

The easiest is sharing the project with us. (You can pm it to me)
If that is not possible because of NDA/Sensitive material, a test case project that performs the the same error can help us solve the issue.

Just an update: I updated to the latest version of Unity and the problem was resolved. Have been running a newer version of Unity for at least a week with no issues.