Forest Pro + Corona Displacement = BUG parsing time?

Corona Corona for 3ds Max Issues
1

Hi all,

I am getting crazy the last 2 days with Forest Pro and the latest 08/01/2021 daily build.
Basically I found out the problem now and I don’t know if you are aware of this. Now I understood why my parsing times are huge and slow!!!

  • This is what happens, you create a plane, you distribute on it hundreds of objects, more you have, worst the situation.
  • Apply a material on the DISTRIBUTED OBJECTS (no displacement for now), render and the process starts almost immediately.
  • Now put a displacement map on the DISTRIBUTED OBJECTS and the parsing time gets hugely high!!!

Is this related to the 2.5D mode which is the default one in the new daily build?

Thanks and let me know.

Dionysios !

2

Hi, we have some problems with parsing time in the few last daily builds. It’s a nice coincidence, because I’m just looking into this code right now :smiley:

Anyway, it would be really great if you could share some of the problematic scenes with us, so that we can look into those and make sure that when we fix this issue that it’s fixed for your case as well.

3

Hi Dionysios,

Could you please send through a simple scene where you can reproduce this? I tried quickly and I must be missing a step somewhere..

Thanks,

Rowan

4

Hi guys!

FYI, I also contacted the itoosoftware support which will receive the same assets/scene I am sending to you right now.
They suggested to me to use Forest Tools and export all Forest objects in instances. I did this and the render works perfectly!!! So in this case Corona works fine.
There is something serious wrong with the combination of Corona + Forest.

Here is the test scene: https://1drv.ms/u/s!ArWIfyOfVovjgtsw82Orw0uVq8suDQ?e=E4MhXw

  • It’s very simple, load the scene and point the maps to the folder included in the ZIP.
  • By default, displacement is disable, render and you’ll see the rendering start immediately.
  • Now go in the material editor and activate the displacement map on the material which is preloaded in the 1st slot. Parsing time would be extremely low…

Let me know if this works for you.

Thanks,

Dionysios -

5

I forgot!

I use

  • Latest Corona Daily Build
  • 3ds Max 2021
  • Forest latest Beta but it happens also with the last commercial version V6.3.1

Dionysios -

6

Hey,

Thanks for the scene and detailed reproduction steps! I have reproduced it here and our dev team is investigating this currently.

I’ll let you know when I have some more information.

Cheers,

Rowan

(Report ID=CRMAX-257)

7

Thanks to all of you for the hard work.

If you guys can resolve this, a lot of us would get drunk from happiness… :smiley:
I am looking forward for your news and updates.

Cheers!

8

Hi guys,

just a small update directly from iToo Software which I received a while ago:

"Hi Dionysios,

As we can see from some further testing, the Forest object itself is built “almost instantly” (IForestRenderBegin > IForestRenderEnd) as you can double-check by setting General - Log Level to Debug in any Forest object in your scene, before sending it to the renderer (optionally by setting forceLog=1 in the forestpack.ini)? I’m afraid we can’t do much more in this case at the moment (like debugging the rendering process) and I hope you/we’ll get some more info regarding it from the “Corona team” soon. If you’ll be interested, the mentioned log file is located at:

C:\Users<user name>\AppData\Local\Autodesk\3dsmax<max version>\ENU\Network\Max.log

Once again, big thanks for your collaboration, your feedback is very important to us."

In a few words, the Forest plugin seems to do it’s work correctly. The long parsing times should be a problem of the rendering engine at this point.
I guess you know it but I thought was useful to paste here their answer.

Thanks!

9

Hi,

So good news, we found the cause of the issue and we are currently testing a fix for it.

If everything goes to plan it will be in the next daily build :smiley:

Cheers,

Rowan

10

Fantastic!!! Thanks for the update!

11

Hi,

This will be in the next daily build. Keep an eye on the forums :wink:

Cheers,

Rowan

12

Thanks so much, such good news!!!

Have a nice weekend.

Dionysios -

13

Hi guys,

do we have an idea of when the fix will be published? I am working without displacement right now and sooner or later I need to activate it again.
Thanks and excuse me for asking such information.

Dionysios -

14

We’re trying really hard to get a new build out.. Hopefully really soon :wink:

15

Thanks and this is the reason why I excuse myself before, I know your hard work.
Have a nice weekend all.

Dionysios -

16

And as if by magic! https://forum.corona-renderer.com/ Corona Renderer 7 for 3ds Max - Daily Builds Changelog #msg182024

Have a nice weekend too :smiley:

17

Yeah!!! :smiley:
I saw it 5 min ago and I already downloaded it and it works perfectly.
Thanks so much for your support guys, really, you’re all so talented.

Dionysios -

18

Hi!

I work with the new displacement fix for 2 days now and till today I had some very good performance and no issues with parsing time.
But, today, while working, I merged a couple of new tree models in my scene and the problem appeared again. Actually, turning off Displacement got only a bit better. Something happened and it slowed down all the parsing process…

I close 3ds Max, open my scene again and the problem disappeared.

Just to let you know even if I know that is not too much info for you now.

Thanks,

Dionysios -

19

Hey,

Thanks for reporting this.

If you experience it again please can you create a new thread and I will investigate it?

Cheers,

Rowan

20

Yes of course! We’ll keep in touch.

Dionysios -