Itoo Software Forum

Forest Pack => Forest Pro (*) => Topic started by: KO3272 on June 12, 2020, 02:15:51 AM

Title: FPP with large proxies create long scene load times
Post by: KO3272 on June 12, 2020, 02:15:51 AM
Hello,

We have been having some issues with FPP and corona proxies where our scenes become very slow to load.

Last night I did quite a bit of testing and found that there seems to be a limit in the amount of polys you can load into a single FPP to keep scene opening reasonable.

As an example - I had an FPP with 23Mil of polys (mesh mode) across 6 corona proxies. That single FPP took over 2 minutes to load. When I instantiated it took 20 seconds to load. When I reduced the amount of proxies equating to approx 6 million polys it took 30 seconds to load.

Are you aware of this and is this to be expected?
Title: Re: FPP with large proxies create long scene load times
Post by: Rokas on June 12, 2020, 09:40:47 AM
Hi
we have done some testing as well and can confirm that corona proxy workflow is a bit slower than using vray proxies or regular mesh.

Scene. 6 trees, 4M each.
(https://i.imgur.com/KIPc3Gy.png)

Growfx version  / With FP
303s / 350s to load

Just Mesh Version / With FP
8s / 44s to load

Just CoronaProxy / With FP
2s / 72s to load

Just CoronaProxy Version Full Mesh / With FP
32s / 79s to load

Just vrayProxy  / With FP
2s / 2s to load

Just vRayProxy Version Full Mesh / With FP
18s / 64s to load

Just Xref Version / With FP
10s / 47s to load

Delay is caused by reading the mesh of the proxy. It's needed to build the point-cloud and to calculate the proxy size.
V-Ray proxy is much faster because it returns an approximation (the same used for the viewport), not the full mesh.

We will contact corona team to inquire about possible solution.
Title: Re: FPP with large proxies create long scene load times
Post by: KO3272 on June 14, 2020, 07:17:25 AM
Hi Rokas,

That makes sense to what we are experiencing.

Thanks for the quick reply. We will instantiate any FPP's with large poly count trees until there is a solution.
Title: Re: FPP with large proxies create long scene load times
Post by: KO3272 on July 13, 2020, 02:48:19 AM
Hi Rokas,

Did you get a response from Corona team?

Also have you tried with Sini ProxSi?

We were thinking this could be a workaround in the short term.

Grant.
Title: Re: FPP with large proxies create long scene load times
Post by: inkvisual on June 08, 2023, 06:23:44 PM
Hi, has this been addressed in the latest combo, Corona 10 daily and newest FP?
Corona team listed fixing FP /RC bugs & improvements on their logs although there are no specific on what has been addressed?
Is there any place where we can see what are the know issues/limitations while using FP/RC with Corona?
Thanks!
Title: Re: FPP with large proxies create long scene load times
Post by: NL4355 on June 08, 2023, 08:52:04 PM
Hi, has this been addressed in the latest combo, Corona 10 daily and newest FP?
Corona team listed fixing FP /RC bugs & improvements on their logs although there are no specific on what has been addressed?
Is there any place where we can see what are the know issues/limitations while using FP/RC with Corona?
Thanks!

Me too, wish to know.
Title: Re: FPP with large proxies create long scene load times
Post by: iToo on June 09, 2023, 08:32:31 AM
Hi,

Hi, has this been addressed in the latest combo, Corona 10 daily and newest FP?
Corona team listed fixing FP /RC bugs & improvements on their logs although there are no specific on what has been addressed?
Is there any place where we can see what are the know issues/limitations while using FP/RC with Corona?
Thanks!

Yes. We have worked with Corona team to improve performance with Corona proxies.

Anyway, Forest requires to get the proxy mesh at least one time, when scene is loaded. This is needed for some Forest processes.
But for example, with animated proxies now Forest evaluates only the first frame, not all animation frames as before. That should improve loading times.

Said that, if you use heavy objects with Forest and Corona mostly, we suggest to store them as XRef'd meshes, instead proxies. That is still the most efficient method.

Besides that, other issues has been fixed (basically, what you can see in the Corona 10 release notes).