Crashing Non-Octane scenes

[shawnfrueh]

Hey Aoktar,

Is there any way to keep octane from running in the background of a non octane scene? I am working with a V-Ray scene and I get crashes when the little ('Scene plugin version is older than 2.16...') shows up and I select before the scene is fully loaded. This popup should not even show up if a scene has never used the plugin. Why does octane have to be 'Always present' Can you add a "Remove Octane From Scene" feature? I have tried digging into the scene files to see what I can find but only you know where this data is stored.

This isn't necessarily a bug but this is a critical issue when your plugin causes crashes outside of its intended use. (Rendering)

Also why does Octane Render show up in the project attributes? I never understood that, Maybe that's the issue? No other plugins use that space.

-Shawn

[shawnfrueh]

If it helps here is a crash report.

_BugReport.zip

(23.56 KiB) Downloaded 236 times

[aoktar]

Plugin checks the octane setting in you scene and if it's older than 2.16 try to fix it. If your startup scene file( new.c4d or default.c4d) is saved with new file, this message will not popup again. Clear? It has been noted also in related topics.

Btw, what's the crashing issue? Cannot understood well.

[shawnfrueh]

My startup scene has never been edited. This comes from other users using different versions of octane depending on the projects requirements. The problem is that no mater what I do octane attaches itself to your scene even if you aren't using octane. The crash I mentioned happened after opening a V-Ray scene and the Octane window popped up and I selected no. The only time octane should be doing anything in my scenes is if my render settings are set to octane. If my render settings are set to V-Ray, Standard etc. Octane has no business being anywhere in my scene. This then comes into play when I want to render something on a farm using standard. I will get the error "plugin is not found" and the render will cancel itself.

[aoktar]

Live viewer not requires to select Octane as renderer. So it should work without select Octane. That's the our way. Just remove Octane from plugins if you have problems. I'm having also vray, and does not gives any crash.

[zegolem]

Almost the same thing here, standard or other renderers scenes should not ask for octane when no octane tag or property is used. The result is that render farms or net renders just stop with errors because of that.

The problem seems to occure when removing an octane render setting (after some renderers tests for a scene for example), the scene still ask for octane plugin, it should not. Copying a whole scene with settings into a fresh file to avoid that is just painful and a waste of time.

And removing/reinstalling the plugin when not using octane is NOT a solution...

[shawnfrueh]

Copying a whole scene with settings into a fresh file to avoid that is just painful and a waste of time.

And removing/reinstalling the plugin when not using octane is NOT a solution...

This is exactly what I am talking about. I have made a custom plugin just to swap in/out/upgrade the octane plugin to speed up this "workflow."

[aoktar]

You want a very hard change from me. In which point, should i check the old/new scene comparison and update the parameters? I think you don't understand the differences of workflow from other renderers. I have some background processes to capture scene changes to detect. If we don't have a window as Live Viewer, we couldn't had to do this. So we couldn't had immediate updates on scene data. Anyway i'll think about scene backward checking process. But you can save a "new.c4d" and get rid of this alert window.

About renderfarm or network render errors without Octane; there should not be any garbage to generate this, else a null object.

[shawnfrueh]

I wouldn't worry about the old/new scenes but rather just document what the actual value changes are so if it is a problem they can be manually changed by the user. No pop-up, It gets annoying.

I get what you are saying about the background processes. Is it possible to only have them running if Octane is the selected renderer? This means that in order to use the live viewer you have to have Octane set as your renderer. I am playing around with the render settings and it seems if a file gets saved with Octane as the renderer and then later is switched to something else there is still data left behind by octane.

In a Cinema with octane it wont show up however if you open that scene up in Cinema without Octane installed 'Octane Renderer' shows up in the Render settings tree view. Whatever data that is should be removed if Octane is not the set renderer. Does that make sense?

[aoktar]

i'll try to do somethings about this popup. But it's not possible to change background processes after this moment. We have very big structure and cannot get this risk. Anyway i can check this situation a bit more. Also reorganisation of settings was on my todo list. This can provide a solution to this problems. But i'll do it after a stabile release. Also is it possible to capture a video to show your problem? This may help a little more.