16.2 and 16.2.2 has extreme compiling time

Forums: 16.2 and 16.2.2 has extreme compiling time
Sub forum for bug reports
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)

16.2 and 16.2.2 has extreme compiling time

Postby J.C » Wed Sep 05, 2018 8:53 pm

J.C Wed Sep 05, 2018 8:53 pm
This version is compiling a single 1 mln triangles object for 20 seconds. Moving it adds another 20 seconds. This version is completely useless.
Last edited by J.C on Thu Sep 06, 2018 1:51 am, edited 1 time in total.
CPU – i9 13900KF, 128GB RAM, GPU – RTX 4090
System – Windows 11
My Behance portfolio, Blender plugin FB support group
J.C
Licensed Customer
Licensed Customer
 
Posts: 1721
Joined: Thu May 13, 2010 6:35 pm
Location: Wrocław

Re: 16.2.2 is extreme compiling time

Postby DrawFun » Wed Sep 05, 2018 10:33 pm

DrawFun Wed Sep 05, 2018 10:33 pm
Hi J.C,

Could you please give a bit more details or share me a demo for debugging? I've built some test cases but there are no significant performance losses compared with previous 16.x.

Cheers,
DrawFun
DrawFun
OctaneRender Team
OctaneRender Team
 
Posts: 350
Joined: Fri Aug 25, 2017 5:02 am

Re: 16.2.2 is extreme compiling time

Postby J.C » Thu Sep 06, 2018 1:49 am

J.C Thu Sep 06, 2018 1:49 am
Sure, here it is. Similar compiling time is in 16.2
The same scene exported to ORBX file compiles in Standalone app in less than a second.
Attachments
compiling.orbx
(75.75 MiB) Downloaded 193 times
compiling.blend
(74.34 MiB) Downloaded 194 times
CPU – i9 13900KF, 128GB RAM, GPU – RTX 4090
System – Windows 11
My Behance portfolio, Blender plugin FB support group
J.C
Licensed Customer
Licensed Customer
 
Posts: 1721
Joined: Thu May 13, 2010 6:35 pm
Location: Wrocław

Re: 16.2 and 16.2.2 has extreme compiling time

Postby J.C » Thu Sep 06, 2018 2:13 am

J.C Thu Sep 06, 2018 2:13 am
This happens only with this particular scene. The object was subdivided before and modifier was applied. Other compile in normal time.
CPU – i9 13900KF, 128GB RAM, GPU – RTX 4090
System – Windows 11
My Behance portfolio, Blender plugin FB support group
J.C
Licensed Customer
Licensed Customer
 
Posts: 1721
Joined: Thu May 13, 2010 6:35 pm
Location: Wrocław

Re: 16.2 and 16.2.2 has extreme compiling time

Postby DrawFun » Thu Sep 06, 2018 3:49 am

DrawFun Thu Sep 06, 2018 3:49 am
Hi J.C,

It seems that the sphere is applied with level 2 OpenSubDiv, which will lead to an extra triangle generation.
Please check the final render result, it contains around 16 million triangles while the original sphere has only 1 million. Therefore about 15 million triangles are generated on the fly, which is quite time consuming.

Regarding the orbx, it renders only 1 million triangles without generating the opensubdiv triangles. To render with subdivision triangles, you can change the subdivision level from 0 to 2 in the "geometry.abc" setting. Then standalone will take times to compile extra triangles too.

Cheers,
DrawFun
Attachments
OpenSubDiv1.png
2018_09_06_14_55_50_OpenSubDiv.png
DrawFun
OctaneRender Team
OctaneRender Team
 
Posts: 350
Joined: Fri Aug 25, 2017 5:02 am

Re: 16.2 and 16.2.2 has extreme compiling time

Postby J.C » Thu Sep 06, 2018 8:41 am

J.C Thu Sep 06, 2018 8:41 am
Thanks DrawFun for pointing this out! This was a false alarm, Sorry for that.
I should have checked the triangles count number in rendered viewport not in Blender viewport. Lesson learned :)
CPU – i9 13900KF, 128GB RAM, GPU – RTX 4090
System – Windows 11
My Behance portfolio, Blender plugin FB support group
J.C
Licensed Customer
Licensed Customer
 
Posts: 1721
Joined: Thu May 13, 2010 6:35 pm
Location: Wrocław

Return to Bug Reports


Who is online

Users browsing this forum: No registered users and 10 guests

Tue Apr 23, 2024 7:37 am [ UTC ]