well, I think the Displacement issues are not 100% resolved.
This is what I’ve noticed till now:
On heavy scenes, it happened twice, the render started relatively fast (no parsing issues) but all the objects that have a displacement map were disappeared from the render.
I attached an image where this happened for the second time. No road, some trees are missing, no walls, ecc.
Sometimes parsing times are ok, but not always. This behavior is not constant.
today I have no parsing slow downs like yesterday by the way. Very weird…
In any case, I can send you all the scene so you can investigate better. It’s still a WIP but I warn you that the file will be quite big cause of the textures, (6GB with textures packed).
I’ll send you a private message with the link once everything is packed and uploaded.
So far I was not able to reproduce this issue. I rendered the scene 20 times and each time it rendered correctly..
Do you get any warning or error messages during rendering?
At this point I would maybe suggest resetting your 3ds Max ENU folder, I experienced some strangeness like this in the past where resetting this folder helped.
Yesterday everything worked fine for me as well but 2 days ago I had parsing time slow down and then the objects disappeared from the render twice! This is the reason why I opened the post here again. I had no warnings or errors at all. Only slow parsing time which wasn’t as slow as before the fix we are using now. Just a bit slower than normal.
Yesterday I did a lot of tests and previews on that scene and me too as you, no issues. -.-
At this point I want to report something but I don’t want to complicate things, just for you to know.
A month ago I decided to start using the Substance materials and as you probably know, we have 2 ways to use them:
Via the Substance plugin.
By exporting from Substance SW all the maps and build each shader manually.
My experience:
A disaster! A lot of crashes, very often the plugin was resetting the parameters and then guess what? Object with displacement were disappeared very very often from the scene.
I naturally thought that this issue was related to the plugin itself and not to Corona or 3ds Max 2021.
Transforming the parametric materials in maps then manually created the shaders and had no issues at all.
So, this behavior I saw twice the other day really surprises me as there are NO SUBSTANCE parametric materials at all in the scene. Since I had those problems I never used them again. I just use their maps (which I like) but not their native shaders.
Let’s keep in touch, I have a lot of work to do these days so I’ll have more change to check if this behavior turns back or not and figure out when.
For now I have no more clues.
Thanks for helping as always.
Hi, today the scene I’ve sent to you it behaves very strangely again.
Parsing time became slow and right now objects are again disappeared. I am sending you an image…
The only thing I did was to merge some new plants in the scene. I have the feeling that when I add something new in the scene, it starts behaving like this. But as you noticed it doesn’t happens always.
Close Max and restart resolves temporary the issue.
I am going to pass to you the original files of those plants.
Now in my case everything works fine, as I said, I closed Max, run it again and no issues.
I only merged them in the scene, in a first step I pointed the software to the new maps and rendered in interactive to tweak the materials and suddenly happened again.
Thanks again for the assets, I am still not able to reproduce this issue.
Would you 1) be able to send me a video of exactly how you manage to reproduce this, and 2) could you try to reset your enu folder as I suggested above and see if this resolves the issue?
I had the very same issue of all displacement objects being invisible at some random rendering. And then again just fine right after.
Not replicated myself, happened twice with the previous daily. Unlike Dionysios, I never installed any Substance plugin, so I am 100perc. sure it’s unrelated to it and it’s purely Corona issue.
I am not sure I remember correctly… but I believe this issue was at IR, not regular rendering.
Hi Juraj and I hope you’re fine first of all.
Yes, it happened to me as well only in IR mode. But the problem is that I can’t replicate it! Now everything works perfectly fine… New displacement fix as well.
last weekend I launch the final renders of that job, everything went well but during the last IR tests it happened again 3 times.
Objects were disappeared, stop, restart and was ok.
The point is always the same, is not happening always unfortunately. I can send you again the update file and assets if you want.
Last time it happened, I just loaded the file hit IR Render, waited for a long time for parsing and happened.
BTW, my system is based on AMD chipset and CPU in case may help. It happened to Juarj as well from what I read, he is on AMD as well.
Let me know, maybe send you the assets again may help.
Just an update:
We finally managed to reproduce this issue with the following steps:
Start IR
Immediately Resize it during the scene parsing
Observe the models with displacement are gone
It looks like something goes wrong if the VFB is resized during the parsing stage. We actually already had this reported, however previously the displacement would calculate incorrectly but the objects would still be visible which is why you maybe didn’t notice this before.
As this seems to have gotten more serious I will bump our devs and see if we can do something about this.
As a workaround I would suggest not to resize the VFB until after the initial scene parsing has completed.
Would you be able to send this scene to me I would like to investigate it asap?