Hey everyone. Looking around it doesn't seem like this a common issue, so perhaps it is just me. I list my specs down at that bottom just in case.
After a more recent update, and since then, I don't remember the build number but it started at least 2 stable release versions before the current at the time of writing this, 2022.1.1 - 27.16. Basically, on certain scenes, usually scenes that have higher geometry counts, the exporter hangs at export time and then octane server crashes. Usually, but not always, I can sorta "fix" this by restarting server and then clearing the cache, but this is on an every time basis, and only lets the render continue about 60% of the time. The other 40% it just crashes again and I need to rinse/repeat.
It crashes very suddenly and there are no error logs. The scene I am having the issue with right now is only about 9gb of VRAM usage. I am not even close to maxing out my VRAM on my 3090. Temps look good. Event viewer only shows that Octane Server Studio has stopped but no driver issues. Drivers are up to date. I went as far as re-installing windows, updating it, and then doing a fresh install of NVidia drivers so there should be no need for driver-cleaner or scrubbing old drivers at all.
Initially I had thought this might be a result of the Add node, because removing them seemed to fix the issue but then in certain scenes the issue came back.
This issue does not exist for me with the same scene in octane stand-alone or the maya plugin. This seems to me to be isolated to Blender / server studio, and the exporter.
I unfortunately cannot post the scene file because I have an NDA for the work and it takes a degree of scene complexity for me to re-create the issue, but maybe someone does know about this and can help anyway...
System specs:
Blender Octane Edition (The OTOY build, not the add-on version yet);
Windows 11 (10.0.22621);
Ryzen 5950x;
NVidia 3090 (Studio Driver 535.98);
64gb ram, 3800mhz, suggested XMP profile clock;
I didn't used to have this issue. Even after the first update I did the issue didn't happen until I threw a particularly complex render scene at it, although, the scene had worked just fine with 0 issues in previous builds. I had hoped maybe this was just a problem with that version of Octane for Blender and Server Studio but it seems to have persisted. These days I am using stand-alone more anyway, but there are certain things blender excels at as a DCC that sometimes I want to take advantage of, that can sometimes be done in stand-alone but not anywhere near as streamlined.
I appreciate any light that can be shed on this issue, maybe how I can troubleshoot it better or if there is another log being secretly written somewhere I can post that I just don't know about that might help. I appreciate it.