Chaos Corona Forum

Chaos Corona for 3ds Max => [Max] Bug Reporting => [Max] Resolved Bugs => Topic started by: karamox on 2016-06-24, 10:21:36

Title: very long scene parsing times using multiscatter and laubwerk trees
Post by: karamox on 2016-06-24, 10:21:36

i noticed very long scene parsing before it starts rendering. laubwerk trees are heavy, and use many memmopry to start rendering in vray. in corona i dont know how it manages memmory, but it does not increase memory usage when scene parses. it is 4 -6 times longer than it take to vray to start rendering. it is very sad. i did not noticed long scene parsing with using proxy trees.

 using laubwerk trees and scattering them as forest using multiscatter.

corona 1.4  3ds max 2016

Title: Re: very long scene parsing times using multiscatter and laubwerk trees
Post by: cecofuli on 2016-06-24, 13:46:59

(*) What's the difference (in seconds) with "Multithread parsing" option OFF (Development rollout).
(*) What about the CPU usage during the parsing stage?

Title: Re: very long scene parsing times using multiscatter and laubwerk trees
Post by: karamox on 2016-06-24, 19:27:22

cpu usage is very low during parsing.
with multithreaded option on - no difference, same long parsing.
after all testing i found it is a problem only of laubwerk trees. they do not render fast in corona, i dont know why but they are parsing very slow.
tested with other hq tree models converted to proxy. it parses in 10-12 sec. 100000 instances using multiscatter. and cpu is loaded fully with generic models.
that is why laubwerk so slow , it dows not use cpu fully when parsing.

Title: Re: very long scene parsing times using multiscatter and laubwerk trees
Post by: karamox on 2016-06-24, 19:34:39

one problem solved. another occured. do you know why corona 1.4 does not use all cpu power to render? it around 70-80 on all cores.

Title: Re: very long scene parsing times using multiscatter and laubwerk trees
Post by: PROH on 2016-06-26, 01:40:42

Hi. Just had a scene with Laubwerk trees where parsing took a loooooooooonnnnnnnnng time. I tried different things to find out why, and found that if I changed the viewport mode of the Laubwerk trees from "Skeleton" to "Render Geometry" then scene parsing took seconds instead of minutes. I would say approximate 10 x faster.

Can't see any logic, but maybe this will work in your too.

Title: Re: very long scene parsing times using multiscatter and laubwerk trees
Post by: Ondra on 2016-06-26, 09:58:45

I would be interested in a scene where this happens...

Title: Re: very long scene parsing times using multiscatter and laubwerk trees
Post by: PROH on 2016-06-26, 11:26:21

Yes. I'll try if I can reproduce it today. It's an old scene where I tested civil view stuff and Max atmospheric. Yesterday I downloaded the new Laubwerk version (1.00.20) and tried it in this scene. I also twice got Max freezing with CPU at 0% because I had a Laubwerk tree selected when I pressed Render. Had to restart Max.

info: 3dsMaxDesign 2014, Corona 1.5 latest daily, Laubwerk plugin v 1.00.20, Windows 10

Where can I upload the file if it's reproduceable?

Title: Re: very long scene parsing times using multiscatter and laubwerk trees
Post by: PROH on 2016-06-26, 17:37:38

OK. So I tested the file today with exactly same result. Since there were a number of other possible influences in the original file I saved the trees out for themselves and cleaned the file. The issue is still there. Even tho it's a very small scene with only a few trees (9 variants instanced to a total of 21) the differences in parsing time is really high:

- When display mode is set to "Convex Hull" parsing time is 44 sec.
- When display mode is set to "Skeleton" parsing time is 45 sec.
- When display mode is set to "Render Geometry" parsing time is 3 sec.

I made the test several times with identical results - only varying 1-2 sec.

I used windows 10, 3dsMaxDesign 2014, Corona 1.5 daily 20 jun 2016, and Laubwerk plugin v1.00.20 (still reads 1.00.19 in "about...").

I attached the file + a picture showing the stats of the different results.

Title: Re: very long scene parsing times using multiscatter and laubwerk trees
Post by: Ondra on 2016-06-26, 19:38:51

it seems like problem with laubwerk trees. I can reproduce the same thing with scanline renderer. I have notified Laubwerk about the issue

Title: Re: very long scene parsing times using multiscatter and laubwerk trees
Post by: PROH on 2016-06-26, 20:23:54

OK, didn't try that. Let's hope Laubwerk gets this solved soon. Until then the advise must be only to use "Rendered Geometry".

BTW - Is the "Max freezing/dying when pressing Render while Laubwerk tree is selected"-bug also a Laubwerk problem?

Title: Re: very long scene parsing times using multiscatter and laubwerk trees
Post by: Ondra on 2016-06-26, 21:31:50

I think I consulted that with them, but we have not solved it yet

Title: Re: very long scene parsing times using multiscatter and laubwerk trees
Post by: maru on 2016-09-14, 11:26:51

The problem of Laubwerk plugin freezing 3ds Max has been recently solved by Laubwerk developers. Please see the following report for more details:
https://corona-renderer.com/bugs/view.php?id=1144

You can download and test the newest beta version of the Laubwerk plugin using the link below, however keep in mind that any problems or bug reports should be sent to Laubwerk, not to us:
https://www.dropbox.com/s/inllgpm86kriu0u/LaubwerkPlantsKitFreebie_1.0.22b5_Win_Setup.exe?dl=0