Render Fails after Scene Load

[treddie]

I think a bug maybe...Occasionally, after loading a scene and attempting a render, the render fails. If I temporarily disconnect some geometry to get it to render again, I can then rehook back up the geometry and everything works fine.

[treddie]

Now it's worse. The scene fails to render no matter what I try to do to jog it free, with the big red error message on the right.
The only time it will not fail is when no geometry is connected. The moment I connect a mesh, it fails.
This is a large file with roughly 30 meshes. Connecting even one of them causes failure.

UPDATE: Found a way to get it back...If you have node groups where you have meshes and textures inside each group, you just have to double-click any group to go inside it. That activates a render of the group, I guess (for me, it is a blank render, since the group's camera view is not looking at meshes, only empty space). Then, when you back back out to scene level, you can click the render node again and start rendering the entire scene without issue.

UPDATE 2: Now it's more complicated...I have one of the 30 meshes that never renders even when it is hooked up. It used to be fine. I thought it might be memory related, so I disconnected other meshes to free up space. But not only will the problem mesh still not render, the disconnected meshes still do! So I thought maybe they're still in memory. So I saved the scene with the problem mesh connected, and two others disconnected. I then x-d out of Octane and reopened the scene. When I did the double-click-a-group and then back out to scene level, I clicked the render node only to find that the problem mesh still did not appear, and the two disconnected nodes still did! So maybe it is just corrupted info in the .ocs file.

[FrankPooleFloating]

OCS files are just XML. You could open it in editor like Notepad++ and see if looks screwed. Doubtful, but this is an option.

[treddie]

Great idea! I'll take a look to see if any old info is still hanging out in the file.

[FrankPooleFloating]

And don't forget, OBJ and MTL are just text files too... readable by humans.

[treddie]

Those ones I'm familiar with. But I want to be a Borg, so it takes all of the fun out of it. I don't feel assimilated reading human-centric code!

[treddie]

Case partially solved:

The reason the one mesh would not appear is that I had accidentally overwritten it with one of the other existing meshes. So that meant that two copies of the same mesh, in the same exact position were being rendered, one over the other. That is why it seemed like a corrupted .ocs file, in that respect.

Could this be causing the render failure? No. When the meshes are fixed, the file saved and Octane closed, then Octane relaunched, Octane still has the render failure problem. Once I do the trick above to get rendering to start again, everything is fine. So. apparently, there is still a problem that looks like an Octane bug.

[roeland]

If the render fails, what log messages do you get?

--
Roeland

[treddie]

Hi Roeland,

"0 Textures, 534852 Tris, 27 Meshes, GeForce GTX 560 (failed), 0.0/1968/2048 MB"

Also, If I do a Stop Render, which also deselects the Render Node, the problem returns. Doing the work-around fixes the problem once again.

Originally, I thought maybe it was my GPU not having enough room to create a buffer, but it happens no matter how many meshes I remove out of the 30 that are available to be hooked up, in the .ocs. If I save the same file, but with only a few meshes hooked up, when I reopen the file, the same problem occurs.

Incidentally, the file did not originally have this problem. But somewhere along the way as I added more and more meshes and put things into more groups, something happened.

[roeland]

Can you open the log window from the menu (help » Open log) and copy the messages you see in this window?

--
Roeland