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)
Serious issue with latest version... Serious in terms of buying 2 980tis and getting same performance as 1 980 + 1 680 i had before....
- Attachments
-
- Max plugin cannot utilize both gpus.... in fact having both in full priority is like one of em is full and the other works in 1/3 or half.... I need a fix for this asap, or why on earth i paid for 3ds max plugin on the first place??
Some more screenshots to show the problem much better. This is not acceptable when u make us pay both standalone and plugin (for those who want to have the plugin). And going back to previous version and losing all the materials and stuff i created so far seems a major bs. In the previous version btw, both gpus hit the 100% usage in case u wondering,
- Attachments
-
- And the proof that octane works perfect in bench..... both gpus identical performance
-
- 2 cards....
- 2 cars.JPG (11.79 KiB) Viewed 3641 times
-
- 1 card active
- 1 card active.JPG (12.67 KiB) Viewed 3641 times
Hey there, I am using the latest nvidia drivers. 980ti are both cards
Hi,
I have run tests with a Multi-GPU box (TITAN Z models in this case) and the speed changes in a scalable manner when enabling/disabling devices in the 3ds Max plugin. There doesn't seem to be any notable plugin-specific issues impeding scalability. I had both the latest Max plugin and standalone version 2.24.1 installed, running a relatively basic scene.
The issue you are having with 3ds Max could be to do with the scene itself, interference from another running application, or some weird behavior occurring between your 980 TI's and the drivers you have installed. I would be happy to take a look at the scene you performed the renders on if you like.
Any other information that you may believe to be noteworthy would also be appreciated. I look forward to helping you resolve this issue, and getting back up and running.
Cheers,
Azen
I have run tests with a Multi-GPU box (TITAN Z models in this case) and the speed changes in a scalable manner when enabling/disabling devices in the 3ds Max plugin. There doesn't seem to be any notable plugin-specific issues impeding scalability. I had both the latest Max plugin and standalone version 2.24.1 installed, running a relatively basic scene.
The issue you are having with 3ds Max could be to do with the scene itself, interference from another running application, or some weird behavior occurring between your 980 TI's and the drivers you have installed. I would be happy to take a look at the scene you performed the renders on if you like.
Any other information that you may believe to be noteworthy would also be appreciated. I look forward to helping you resolve this issue, and getting back up and running.
Cheers,
Azen
Alright i ll upload the scene when i get home. One other thing i noticed is that if i left click and hold on the frame of the render window, the 2nd gpu goes to 99% and stays stable. If i leave my mouse it does this thing again. In any case i will upload u my scene later. thanks for the help
Sorry for the late reply, i dont have much time during the week. I upload a jpeg to show u something i found out + my scene so u take a look. thanks
link to the scene: https://www.dropbox.com/s/3tqd2hg1lxtaq ... m.max?dl=0
link to the scene: https://www.dropbox.com/s/3tqd2hg1lxtaq ... m.max?dl=0
- Attachments
-
- when i click on the edge of the window and hold both gpus go 100% which is very odd.
thanulee wrote:Sorry for the late reply, i dont have much time during the week. I upload a jpeg to show u something i found out + my scene so u take a look. thanks
link to the scene: https://www.dropbox.com/s/3tqd2hg1lxtaq ... m.max?dl=0
Thank you for providing the scene. I will download and look further into it, and get back to you as soon as I can.
Cheers,
Azen
Hey,
On closer inspection, it seems that some core functionality is placing stress on your GPUs. This is a consequence of limitations with MAX itself (in regards to integrating with Octane). Fortunately, the limitations specific to your issue will be amended, however this will come with Octane 3. With Octane 3 helping to better overcome a lot of the limitations inherent with MAX, this will greatly improve many things across the board.
The focus right now for 2.x is comprehensive bug-fixing - this issue is caused by a consequence of limitations with MAX rather than by an actual bug, so this issue will be resolved as a result of the upgrade to Octane 3.
If you wish for any further clarification, or have any further questions, please let me know.
Cheers,
Azen
On closer inspection, it seems that some core functionality is placing stress on your GPUs. This is a consequence of limitations with MAX itself (in regards to integrating with Octane). Fortunately, the limitations specific to your issue will be amended, however this will come with Octane 3. With Octane 3 helping to better overcome a lot of the limitations inherent with MAX, this will greatly improve many things across the board.
The focus right now for 2.x is comprehensive bug-fixing - this issue is caused by a consequence of limitations with MAX rather than by an actual bug, so this issue will be resolved as a result of the upgrade to Octane 3.
If you wish for any further clarification, or have any further questions, please let me know.
Cheers,
Azen
Well, with the previous plugin there is no such thing as the limitation from max, everything works smoothly. Therefore i do not believe there is something wrong with max, but with the plugin itself. Test it for ur self and let me know.
Speaking of which when is eta of v3 for max? thanks
Speaking of which when is eta of v3 for max? thanks