Ok so, I have the "enable real-time in viewport rendering" option in Octane enabled in all my default scenes. And works great to get faster, smoother previews in Blender's viewport.
Now here's my issue: when I activate the octane AOVs and the Octane compositor output, the blender viewport goes gray. But I can still see the render previews in the Octane viewport. With real-time compositor working and all. If I then disable the real-time option (keeping the AOV and compositor), the Blender viewport goes back to working normally.
Any fixes coming? I love the real-time option, use it all the time as it really helps with viewport speed and smoothness.
Many thanks!!
Real-time issue with Blender viewport
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
It is worth to mention about all these options and their use-cases (and could be the reason why, meaning, a limitation):
As per the available information about the feature, the Real-Time option does not turn the chosen Kernel (e.g. Path Tracing) into a Brigade-like kernel but essentially speed up a set of certain GPU processes, some or most of which relate to image buffer.
Some additional methods to to speed up the IPR (rendering image buffer):
• The Direct Kernel instead of PT, when suitable, is another approach to speeding rendering calculations.
• Render settings and project file data set "scene" optimization, further elaborated on this page.
• Sub-sampling options that come as 2x2 and 4x4 pixel grid; one could think of it as a lower resolution for the first calculated samples which makes "moving around the 'scene' " a smoother experience.
Shown here in Octane Standalone:
As per the available information about the feature, the Real-Time option does not turn the chosen Kernel (e.g. Path Tracing) into a Brigade-like kernel but essentially speed up a set of certain GPU processes, some or most of which relate to image buffer.
Some additional methods to to speed up the IPR (rendering image buffer):
• The Direct Kernel instead of PT, when suitable, is another approach to speeding rendering calculations.
• Render settings and project file data set "scene" optimization, further elaborated on this page.
• Sub-sampling options that come as 2x2 and 4x4 pixel grid; one could think of it as a lower resolution for the first calculated samples which makes "moving around the 'scene' " a smoother experience.
Shown here in Octane Standalone:
- octane-standalone-viewport-sub-sampling.jpeg (22.2 KiB) Viewed 1583 times
Octane resources
OCTANE POSTS (URLs have changed, which will break some links but all content remains available).
OCTANE POSTS (URLs have changed, which will break some links but all content remains available).
Thanks Skientia. Yes I realize RTV is not the be and end all viewport solution and that there are other ways to increase the viewport efficiency. But RTV is fantastic and I would just like to see it work with the Octane Compositor as well. (I heard yesterday that RTV doesn't support Compositor yet)
-
linograndiotoy
- Posts: 1350
- Joined: Thu Feb 01, 2018 7:10 pm
The Real-Time option currently limits other features, such as using the compositor. This is why I always recommend keeping it turned off during "production" workflows.martinmgl wrote:Thanks Skientia. Yes I realize RTV is not the be and end all viewport solution and that there are other ways to increase the viewport efficiency. But RTV is fantastic and I would just like to see it work with the Octane Compositor as well. (I heard yesterday that RTV doesn't support Compositor yet)
Thanks Lino. But what I don't get is why it does (seem to) work in the Octane viewport and not in the Blender viewport?linograndiotoy wrote:The Real-Time option currently limits other features, such as using the compositor. This is why I always recommend keeping it turned off during "production" workflows.martinmgl wrote:Thanks Skientia. Yes I realize RTV is not the be and end all viewport solution and that there are other ways to increase the viewport efficiency. But RTV is fantastic and I would just like to see it work with the Octane Compositor as well. (I heard yesterday that RTV doesn't support Compositor yet)
Many thanks!
Martin
-
linograndiotoy
- Posts: 1350
- Joined: Thu Feb 01, 2018 7:10 pm
That's an interesting question. I'll look into that. Thanks!