Difference in render speed between plugin and standalone Tweet

[VISUAL360]

Hi Juanjo,

I had imported a obj (originally exported from a houdini scene) and tried rendering with plugin and then standalone.

The plugin took about 2min52 seconds to render, while the standalone rendered it within 38 seconds.

Are there certain parameters I need to adjust for GPU rendering with the plugin? I have a 1080 gtx.

Thanks

[juanjgon]

The plugin should have the same rendering performance than standalone, of course using the same render settings and the same render resolution. I think that this difference only can mean that the render settings or the render resolution that you are using are not the same.

All the render settings are inside the render target HDA, specially inside the kernel menus.

Thanks,
-Juanjo

[VISUAL360]

Tried to keep them as close as possible and ran them again. Had to export the Houdini file as alembic and imported into standalone.

I've provide both files with time references. Can you see or do a similar test and see what times you get? Maybe I'm missing a critical area that I need to change.

2;22 for Octane plugin
1:27 Standalone

Thanks

[juanjgon]

Can you send me the Houdini scene to test it here?

The best test to be sure about the rendering performance can be export the .orbx scene from Houdini using the scene export feature from the ROP or from the IPR. It is clear that the images are not the same, and it is hard to say where can be the difference in the settings between the two scens.

Thanks,
-Juanjo

[VISUAL360]

Hi Juanjo,

I tried to export the Houdini Indie file to .orbx and it gave me the following message. Are you able to export to a native octane file with Indie?

I used the right mouse click on the IPR window and tried to export from there.


Here's the file from indie.

https://dl.dropboxusercontent.com/u/61888104/OctaneHoudini_SpeedTest/Octane_Houdini_Bottle.hiplc

[VISUAL360]

Hey Juanjo,

I just realized something. The reason my render took longer in in the plugin was because my IPR window was enlarged.

Ex1. IPR Window resolution of 800 x 450 = 39s (2000 samples)
Ex2. IPR Window resolution of 1595 x 811 = 2min24s (200 samples)

Didn't realize that the render size of the file (from one of the nodes) is overridden by the IPR window size. I have Octane plugin for Modo and don't believe it behaves that way.

Is that correct? What about MPlay? What is that relationship.

...Lord, so much to learn! Totally appreciate your help. Thank you.

[juanjgon]

Well, Octane must render the scene using the current IPR window size. If you resize it, the render will restart using the new resolution.

Thanks,
-Juanjo

[juanjgon]

Hi Juanjo,

I tried to export the Houdini Indie file to .orbx and it gave me the following message. Are you able to export to a native octane file with Indie?

I used the right mouse click on the IPR window and tried to export from there.


Here's the file from indie.

https://dl.dropboxusercontent.com/u/61888104/OctaneHoudini_SpeedTest/Octane_Houdini_Bottle.hiplc

Yes, this is correct. Due to the Indie license restrictions, all the Octane scene export functions are disabled. Sorry.

Thanks,
-Juanjo

[VISUAL360]

That's too bad. It is quite handy. I know the modo plugin allows you to do that.

Wonder why such a restriction. Do most plugins not allow you to do this?

[juanjgon]

The restriction comes from the Houdini side due to the Indie licensing terms, not from the plugin.

The Houdini Indie version allows third party renderers, but only if the plugins run with two restrictions: the plugins can't export the scene data to files or to the cloud, and the render resolution while rendering sequences is limited to 1080p. These are the same limitations that Indie has with it's own renderer.

The same plugin working in the commercial Houdini versions doesn't have these restrictions.

Thanks,
-Juanjo