Re: OctaneRender 3 for ArchiCAD [TEST and STABLE]
Posted: Wed Apr 12, 2017 11:15 am
Hi Paul,
To begi with.. there is no issue, but I like to share my testing anyway,
..maybe these numbers give you usefull information or insight comparing standalone versus plugin.
I have tested and compared 3.06, 3.05 and 3.00 and no serious differences in renderspeeds.
(for your information: the scene has 11962 processing elements, 7.3 million triangles, 547 meshes, 3,3 gb vram used)
There is a huge difference in the using the orbx in the standalone and when rendering plain fromout ArchiCAD plugin.
The first rendering after loading the scene seems about the same for standalone and plugin.. with networkrendering both were about 30sec. The difference is after changing camera or restart rendering.
i.e. When having rendered in the standalone the first time (53-58 sec),
and I restarted rendering the second time it took only 34-39 seconds to render the same.
In the plugin there is no restart button (only reload), so I could not test the same.
I did change camera and back, and then after rendered the first time (... sec),
and I reset camera to rendering the second time it took 47-49 seconds to render the same (not 34-39 seconds).
Testing another way not changing the camera, but the resolution back and forth (to force rerendering).. now the rendertime was 62 seconds.
I did the same in standalone and that resulted in 44 sec
Looks like when jumping from camera to camera (using view map names with same rendertarget name).. there is an unneeded loading time?
the rendertarget names are the same by the way, so only ArchiCAD camera's are changing within the same scene.
And if so I might be loosing the speed of networkik rendering as well by extra loading time needed there?
So I tested networkrendering on same rendertarget.
In the Standalone the rendertime was 30 seconds after having loaded the scene the first time. After restart rendering the rendertime was 15 seconds.
In the plugin the rendertime was 29 seconds after having loaded the scene the first time. After reset camera the rendertime was 15 seconds.
When refreshing by using View Map (used in BatchRender).. then the rendertime was 20-23 seconds.
The strange thing is I have doing the BatchRender, and then they take about a minute per render.
So I did the BatchRender again.. . I did the same sequence of 13 visuals as yesterday.. yesterday it took 10-11 minutes, just now half the time.
Conclusion: none
because the same thing I did yesterday took me half the time today.. so something else must have be going on. I also had a bluescreen yesterday.. (WHEA_UNCORRECABLE_ERROR), so maybe Windows or the cpu was strubbling all the time in background causing also bad perfromance in rendering
sorry to have bothered you. And now I am oblivious and just will go on doing the project.
Probably next time when I suspect slow rendertimes, I better restart my PC and see if that makes a difference.
btw: There seems to be much faster loading the scene in Standalone comparing to plugin to begin with!?|
greetz,
To begi with.. there is no issue, but I like to share my testing anyway,
..maybe these numbers give you usefull information or insight comparing standalone versus plugin.
I have tested and compared 3.06, 3.05 and 3.00 and no serious differences in renderspeeds.
(for your information: the scene has 11962 processing elements, 7.3 million triangles, 547 meshes, 3,3 gb vram used)
There is a huge difference in the using the orbx in the standalone and when rendering plain fromout ArchiCAD plugin.
The first rendering after loading the scene seems about the same for standalone and plugin.. with networkrendering both were about 30sec. The difference is after changing camera or restart rendering.
i.e. When having rendered in the standalone the first time (53-58 sec),
and I restarted rendering the second time it took only 34-39 seconds to render the same.
In the plugin there is no restart button (only reload), so I could not test the same.
I did change camera and back, and then after rendered the first time (... sec),
and I reset camera to rendering the second time it took 47-49 seconds to render the same (not 34-39 seconds).
Testing another way not changing the camera, but the resolution back and forth (to force rerendering).. now the rendertime was 62 seconds.
I did the same in standalone and that resulted in 44 sec
Looks like when jumping from camera to camera (using view map names with same rendertarget name).. there is an unneeded loading time?
the rendertarget names are the same by the way, so only ArchiCAD camera's are changing within the same scene.
And if so I might be loosing the speed of networkik rendering as well by extra loading time needed there?
So I tested networkrendering on same rendertarget.
In the Standalone the rendertime was 30 seconds after having loaded the scene the first time. After restart rendering the rendertime was 15 seconds.
In the plugin the rendertime was 29 seconds after having loaded the scene the first time. After reset camera the rendertime was 15 seconds.
When refreshing by using View Map (used in BatchRender).. then the rendertime was 20-23 seconds.
The strange thing is I have doing the BatchRender, and then they take about a minute per render.
So I did the BatchRender again.. . I did the same sequence of 13 visuals as yesterday.. yesterday it took 10-11 minutes, just now half the time.
Conclusion: none
because the same thing I did yesterday took me half the time today.. so something else must have be going on. I also had a bluescreen yesterday.. (WHEA_UNCORRECABLE_ERROR), so maybe Windows or the cpu was strubbling all the time in background causing also bad perfromance in rendering
sorry to have bothered you. And now I am oblivious and just will go on doing the project.
Probably next time when I suspect slow rendertimes, I better restart my PC and see if that makes a difference.
btw: There seems to be much faster loading the scene in Standalone comparing to plugin to begin with!?|
greetz,