OctaneRender_for_Maya_4.0RC7_-_13.15 [ OBSOLETE ]

[calus]

HI Maya users,
do you also have problem with a lot of instances and slow evaluation times like we have in 3ds max?

Hi Coilbook,
- with 100k instances, evaluation time is fast (few seconds) for interactive or batch render.
- With 1 million instances, evaluation time takes less than a minute for the first frame as expected, but takes more than 1 hour for the second frame !!!!!!!

So yes it seems we have the same issue.

[BK]

HI Maya users,
do you also have problem with a lot of instances and slow evaluation times like we have in 3ds max?

Hi Coilbook,
- with 100k instances, evaluation time is fast (few seconds) for interactive or batch render.
- With 1 million instances, evaluation time takes less than a minute for the first frame as expected, but takes more than 1 hour for the second frame !!!!!!!

So yes it seems we have the same issue.

Hi Calus,

Thanks!! Could you share a sample scene? which Instance you were using?

cheers

[calus]

Could you share a sample scene?

Hi Bikram.

Here is a sample scene with the bug, this is a static particle instancer with 750k instances.
When batch rendering, the first frame have expected evaluation time (about 30s) but following frames have insane evaluation time.
the bug happen whatever value have the "frames to precache" setting.

instancer750k_BatchBug.7z

(11.13 MiB) Downloaded 210 times

For comparaison, the same scene with only 500k instances don't have this bug with batch render:
- when frames to precache = 0 : same expected evaluation time for each frame of the sequence.
- when frames to precache = 10 : slightly longer evaluation time for the first frame then only a couple of seconds for the other frames, as expected.

instancer500k_Batch_noBug.7z

(7.48 MiB) Downloaded 204 times

_

[coilbook]

HI Maya users,
do you also have problem with a lot of instances and slow evaluation times like we have in 3ds max?

Hi Coilbook,
- with 100k instances, evaluation time is fast (few seconds) for interactive or batch render.
- With 1 million instances, evaluation time takes less than a minute for the first frame as expected, but takes more than 1 hour for the second frame !!!!!!!

So yes it seems we have the same issue.

Thank you

[BK]

Could you share a sample scene?

Hi Bikram.

Here is a sample scene with the bug, this is a static particle instancer with 750k instances.
When batch rendering, the first frame have expected evaluation time (about 30s) but following frames have insane evaluation time.
the bug happen whatever value have the "frames to precache" setting.

instancer750k_BatchBug.7z

For comparaison, the same scene with only 500k instances don't have this bug with batch render:
- when frames to precache = 0 : same expected evaluation time for each frame of the sequence.
- when frames to precache = 10 : slightly longer evaluation time for the first frame then only a couple of seconds for the other frames, as expected.

instancer500k_Batch_noBug.7z

sampleInstancerRef.jpg

_

Hi Calus,

Thank you so much for the scenes!!
It seems to be working on my side when the Animator data of the Cube, nparticles and instancer are set to Force load even though my precache is 0.
Still, need to do further test. Will keep you up to date.

Cheers

[BK]

HI Maya users,
do you also have problem with a lot of instances and slow evaluation times like we have in 3ds max?

Hi Coilbook,
- with 100k instances, evaluation time is fast (few seconds) for interactive or batch render.
- With 1 million instances, evaluation time takes less than a minute for the first frame as expected, but takes more than 1 hour for the second frame !!!!!!!

So yes it seems we have the same issue.

Thank you

Hello Coilbook,

Could you share us a Max's sample scene or PM if there is a copyright issue?

Thanks again!!

[calus]

It seems to be working on my side when the Animator data of the Cube, nparticles and instancer are set to Force load even though my precache is 0.

This doesn't change anything on my side, still have the bug = very long evaluation time (hours) except for first batch render frame.
You may have change something else, can you share back the "working" modified scene ?

[leehenshall]

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?

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?

[Vyoor]

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.

[BK]

It seems to be working on my side when the Animator data of the Cube, nparticles and instancer are set to Force load even though my precache is 0.

This doesn't change anything on my side, still have the bug = very long evaluation time (hours) except for first batch render frame.
You may have change something else, can you share back the "working" modified scene ?

Hey Calus,

Thanks.. We are able to replicate the issue now with the same setting. I have created a ticket on our bug tracking system.

cheers