Hi,
The ETA will be clear once the v3 Standalone moves out of Alpha, as any plugin is dependent on a stable Standalone. The ETA for the standalone is dependent on the outcomes of on-going customer testing. Tentative target dates fall around the late-April mark - again, this is not official, but is the closest to an ETA I'm in a position to give. All v3 plugins should follow on quickly from that point on wards.
As for the performance issue - what I've found on this end is that using multiple GPUs heats up the cards considerably. This is due to an expensive core function being called frequently. This was not an issue in prior plugins, but a lot of additional features has since been layered over the top, exerting an accumulated effect on performance. Making core functions more efficient would call for some refactoring - these efforts are being poured into the v3 iteration of the plugin. At this stage, it is difficult to determine if carrying these efforts over to v2 would be possible - there isn't much more I can say with total certainty beyond that.
When you say that the previous plugin was running smoothly, are you referring to 2.15? If there are settings tweaks or anything else that can be done on your 2.16 version that could minimize the issue you are having, I will look into that for you.
Cheers,
Azen
Major issue with gpu priorities sos
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)
Thanks and yes, i am referring to 2.15 (i dont remember which is the one before that but i think that is the one i tried). If u can take a look and let me know. Thanks again
Hi,
One probable cause for this issue could be derived from the standalone you are using. Are you using 2.24.2 of the standalone together with the plugin, or an earlier version?
The 2.17 version (and on wards) of the plugin works with the 2.25 standalone. Since this issue is being caused by performance overheads from low-level functions dating back to Kabra's original source code, fixes can only really be applied in 3.x along with the ground-up work occurring there. Hopefully using an updated standalone can alleviate your issue somewhat in the meantime.
Cheers,
Azen
One probable cause for this issue could be derived from the standalone you are using. Are you using 2.24.2 of the standalone together with the plugin, or an earlier version?
The 2.17 version (and on wards) of the plugin works with the 2.25 standalone. Since this issue is being caused by performance overheads from low-level functions dating back to Kabra's original source code, fixes can only really be applied in 3.x along with the ground-up work occurring there. Hopefully using an updated standalone can alleviate your issue somewhat in the meantime.
Cheers,
Azen