Make Live Viewer match Picture Viewer?

[MichaelJeffreyVance]

Is there not a way to make the Live Viewer render the same as the picture viewer? Cinema has different settings for the editor view and the final render. The stop lights are one example: One object may be set to only be visible in the editor but not the final render, and another object vis versa. The SDS object also offers different settings for the editor and for final render. The live viewer in my experience always matches the editor and respects the same settings as the editor, but sometimes I want the live viewer to respect the settings for final render. So if my SDS object is set to one subdivision for the editor and three subdivisions for the final render, I want to be able to set the live viewer to respect the final render settings (so it renders three subdivisions and not just one subdivision) in the live viewer. I hope I have made myself clear because I've seen the question asked before but have never seen it answered. Thank you.

[jayroth2020]

Hi Michael, some information that will address your question can be found here: https://docs.otoy.com/cinema4d/Anatomyo ... iewer.html

In the case of SDS, have you tried using the SDS from the Octane Object tag, instead of the C4D SDS Generator? With the Octane Object tag, you dial in the resolution you need and the tessellation takes place on the GPU, not the CPU; this means that the object will transfer to the GPU memory much faster than the SDS generator can, as there is simply less data to move over. If you wish to have a different resolution in the editor vs. the render, like the SDS Generator offers, you can still use the SDS Generator, but use the stop lights to prevent its use for renders (Live Viewer honors this setting), or just leave the mesh resolution as is for the editor (without any subdividing). Overall, the Octane Object tag solution is better for Octane.

Hope this helps!

[MichaelJeffreyVance]

Hi Michael, some information that will address your question can be found here: https://docs.otoy.com/cinema4d/Anatomyo ... iewer.html

In the case of SDS, have you tried using the SDS from the Octane Object tag, instead of the C4D SDS Generator? With the Octane Object tag, you dial in the resolution you need and the tessellation takes place on the GPU, not the CPU; this means that the object will transfer to the GPU memory much faster than the SDS generator can, as there is simply less data to move over. If you wish to have a different resolution in the editor vs. the render, like the SDS Generator offers, you can still use the SDS Generator, but use the stop lights to prevent its use for renders (Live Viewer honors this setting), or just leave the mesh resolution as is for the editor (without any subdividing). Overall, the Octane Object tag solution is better for Octane.

Hope this helps!

Thanks Jay. I usually work with Octane's material based subdivision which I find can handle more scene objects, but find it still suffers a render hit depending upon the subdivision level similar to the Cinema SDS object. Is transfer to the GPU memory really a big bottleneck time-wise compared to the longer render times with sds levels?

Also. Besides wanting to keep the scene somewhat render engine agnostic the thing I most want is what I asked for above. Not workarounds. No offense. I take your point that when rendering in Octane using Octane tag sds is more efficient but I just want my question answered yes or no. Does the Octane Live Viewer have a setting to respect Cinema 4D's Picture Viewer render settings or not? I just want that confirmed one way or the other. Thank you.

[jayroth2020]

Regarding the stoplights, the lower item is considered the "render control." That is the one that Octane uses. Does that answer your question?