Page 4 of 4
Re: OctaneRender_for_Maya_4.0RC7_-_13.15 [ STABLE ]
Posted: Wed Nov 21, 2018 5:04 am
by BK
leehenshall wrote:This might be a stupid question...but I'm getting some really bad general Maya interactivity performance when rendering in IPR. It seems like Octane is rendering on my display GPU even though I've disabled my display GPU in the cuda device rollout. When I stop rendering everything returns to normal. Could there be some confusion as to which GPU is my display GPU?
compute device.JPG
I've noticed my PRIMARY GPU and my DISPLAY GPU seem to be different? could this have anything to do with my poor performance?
I've tried to specify my openGL device for Maya via the Nvidia control panel but still can't seem to get decent interactivity within the Maya interface when rendering.
Can anyone help with this?
Hi leehenshall,
Thank you for the post.
Not sure if anyone is having the same issue but do you also have display monitors connected on the Primary GPU?
Try using MSI Afterburner and post the screenshot.
Also, check if Maya is running on Primary GPU or Display GPU.
Cheers
Re: OctaneRender_for_Maya_4.0RC7_-_13.15 [ STABLE ]
Posted: Wed Nov 21, 2018 5:10 am
by BK
Vyoor wrote:I think there is something wrong with shading nodes connections.
Keyed octane nodes (rgb spectrum texture or float texture which is connected for example to mix material's amount) are still have very bad influence for viewport update performance (when scrolling the timeline). Some kind of workaround is to delete that (or all) octane shading nodes and undo that, but it's not working anytime. The worst thing is that sometimes after this operation shading networks with that animated nodes are not working anymore in batch render (are rendered white). Viewport renders are fine. I will send PM with sample scene.
Hi Vyoor,
thank you so much for sharing the file. We are currently investigating it.
Could you please try to disable the
Textures Quality and the Swatch quality (SPP) by setting the value as 0 from the Maya Viewport Default rollout?
Hope you will find helpful with the viewport performance.
Cheers
Re: OctaneRender_for_Maya_4.0RC7_-_13.15 [ STABLE ]
Posted: Wed Nov 21, 2018 10:52 am
by leehenshall
BK wrote:leehenshall wrote:This might be a stupid question...but I'm getting some really bad general Maya interactivity performance when rendering in IPR. It seems like Octane is rendering on my display GPU even though I've disabled my display GPU in the cuda device rollout. When I stop rendering everything returns to normal. Could there be some confusion as to which GPU is my display GPU?
compute device.JPG
I've noticed my PRIMARY GPU and my DISPLAY GPU seem to be different? could this have anything to do with my poor performance?
I've tried to specify my openGL device for Maya via the Nvidia control panel but still can't seem to get decent interactivity within the Maya interface when rendering.
Can anyone help with this?
Hi leehenshall,
Thank you for the post.
Not sure if anyone is having the same issue but do you also have display monitors connected on the Primary GPU?
Try using MSI Afterburner and post the screenshot.
Also, check if Maya is running on Primary GPU or Display GPU.
Cheers
Thanks for your response. I noticed the performance improves a lot if I use viewport rendering. I think my performance issues could have something to do with using the Maya framebuffer at higher resolutions. If I go above 4K in IPR Maya starts to drop interactivity.
It seems like the Maya frame buffer is having issues handling high resolution images while IPR rendering. It works better at lower resolutions but then my car is like a postage stamp and I cannot see the shaders at highres from the render cam view. The reason the car is so small in frame is because I am matching to a backplate and I cannot zoom my render view to reduce the empty space in the render and reduce the overall resolution because post scale, film offset and 2d pan and zoom are not currently supported in Octane For Maya. (I will post a request for this seperatley)
I am using Afterburner and can confirm I do see activity on the display GPU even though it is turned off for CUDA in the render globals. I think this is more likely to be something to do with handling a large image in the maya framebuffer rather than rending but I can't be sure.
Lastly can you explain the difference between Primary GPU and DISPLAY GPU?
Surely they should be the same GPU which for most people would be GPU 1.
Re: OctaneRender_for_Maya_4.0RC7_-_13.15 [ STABLE ]
Posted: Wed Nov 21, 2018 9:35 pm
by leehenshall
So I've tried again this evening and still getting some issues even when using viewport IPR. It could have something to do with my GPU configuration but I use Octane for C4D, V-Ray GPU & I-Ray for Maya and do not have this problem.
Camera navigation seems okay when I tumble in the viewport render view. But If I try to use the a regular viewport 2.0 view while rendering in another view or framebuffer it judders and pauses every few seconds. This only happens when I'm rendering and works fine when not rendering. I'm confident I am not rendering on my display GPU but it sure feels like I am when using Maya to edit the scene while rendering.
Here is a video. It's difficult to capture but hopefully you can see my problem.
It seems the only workflow that I can find that makes Octane for Maya run well while in IPR is to set my whole viewport to IPR mode. However my preferred workflow is to have a render on one screen and a viewport in the other where I can edit the scene which is currently causing me problems.
Re: OctaneRender_for_Maya_4.0RC7_-_13.15 [ STABLE ]
Posted: Thu Nov 22, 2018 4:59 am
by BK
leehenshall wrote:So I've tried again this evening and still getting some issues even when using viewport IPR. It could have something to do with my GPU configuration but I use Octane for C4D, V-Ray GPU & I-Ray for Maya and do not have this problem.
Camera navigation seems okay when I tumble in the viewport render view. But If I try to use the a regular viewport 2.0 view while rendering in another view or framebuffer it judders and pauses every few seconds. This only happens when I'm rendering and works fine when not rendering. I'm confident I am not rendering on my display GPU but it sure feels like I am when using Maya to edit the scene while rendering.
Here is a video. It's difficult to capture but hopefully you can see my problem.
O4M_performance_issues.mp4
It seems the only workflow that I can find that makes Octane for Maya run well while in IPR is to set my whole viewport to IPR mode. However my preferred workflow is to have a render on one screen and a viewport in the other where I can edit the scene which is currently causing me problems.
Hi Leehenshall,
Thanks for the video.
It seems Maya is still using the 2nd GPU (Primary) enabled in the CUDA tab.
Primary - is just windows API naming, there is no guarantee is this type used for display by windows or not. It's quite confusing since you have the same GPUs but it is good to know which GPU is used for display.
The plugin just tries to help to the user showing them how windows have typed the GPUs installed, the plugin does not decide anything about the names and meanings of these types, it just directly shows to the user what windows reports about its GPUs.
The Display GPU is also used by the Windows for display and we recommend not using it if you have other available GPUs in your system to not freeze your system with heavy renderings.
Could you try disabling the Primary and see if it make any difference? Hope this help fix the lags.
Cheers
Re: OctaneRender_for_Maya_4.0RC7_-_13.15 [ OBSOLETE ]
Posted: Thu Nov 22, 2018 10:01 pm
by leehenshall
I tried turning off GPUS I also tried changing the wiring of my monitor to different GPUs as well as using display port 1.2 to daisy chain my two monitors off of a single display port.
When ever I change my monitor wiring the PRIMARY & DISPLAY GPUS seem to change to unexpected GPUS:
Mean while all is well in the land of Octane 4 C4D:
Everything is rapid in Standalone:
This seems like a Maya plugin problem. It could be user error on my part but what ever the problem is it's not obvious.
Re: OctaneRender_for_Maya_4.0RC7_-_13.15 [ OBSOLETE ]
Posted: Mon Nov 26, 2018 5:08 am
by BK
leehenshall wrote:I tried turning off GPUS I also tried changing the wiring of my monitor to different GPUs as well as using display port 1.2 to daisy chain my two monitors off of a single display port.
When ever I change my monitor wiring the PRIMARY & DISPLAY GPUS seem to change to unexpected GPUS:
compute device2.JPG
Mean while all is well in the land of Octane 4 C4D:
compute device3.JPG
Everything is rapid in Standalone:
compute device4.JPG
This seems like a Maya plugin problem. It could be user error on my part but what ever the problem is it's not obvious.
Hi leehenshall,
Thank you for showing the comparison.
Unfortunately, we cannot replicate your issue on our side. Maybe you can try to update Maya to the latest version.
Check your NVIDIA control panel> Setup Multiple display settings to find out your Primary and Display.
Also, the see the OpenGL rendering GPU is set to Auto select in the Manage 3D settings.
We will keep looking into this and give you update if we find anything.
cheers
Re: OctaneRender_for_Maya_4.0RC7_-_13.15 [ OBSOLETE ]
Posted: Tue Nov 27, 2018 11:56 am
by leehenshall
I'm installing a new CPU and motherboard in about week and will be moving my GPUS to that board and installing a new OS on a new hard drive. I will test again using a fresh configuration and get back to you.
I think this is probably an issue with how windows in reading my GPUs and then Octane plugin is using that information to decide which GPU is primary or monitor etc.
It still makes me question the Maya plugin though as I am rendering in standalone just fine without any issues... I've tried the nvida control panel workarounds but they don't change anything and using latest version of Maya.
Will keep you updated but in the meantime I'm prioritizing standalone workflows.