Sorry for the issue. Are you facing the same problem as this one: When selecting the scatter in the object list, the right edit panel won’t display? Could you please take a screenshot so I can better locate your problem?
If yes, can you send this scene file to support@d5techs.com for testing? Please attach a link to this post in the email, so I can quickly find you. Thanks!
Here’s a known issue with the current version regarding this.
If you select [Select Material] when using D5 Scatter, and modify the material name in the modelling software later (the material name has changed) and then sync it to D5, the scattered parts of that material will lose data (because the Scatter believes the attached material is gone, and then clean up the data when recalculating, resulting in assets disappearing, and cannot be edited).
We will keep monitoring this, and thanks for your understanding.
The problem occurs even if nothing is altered in the modeling software. D5 simply loses the information upon reselecting the area, whether you’re attempting to modify something or just clicking on the entity. Unfortunately, this issue still persists, and we’re repeatedly offered supposed solutions that aren’t effective. Please provide a genuine solution to the problem. Thank you.
We have addressed this issue with our team, and here is the response:
"I’m a D5 Development Engineer, and I sincerely apologize for the inconvenience this error has caused you.
The previous response was based on my initial assumptions. We have now reproduced the issue, and the results are nearly identical to what you are experiencing.
Our hypothesis is that ‘the name of the material was changed after creating the scatter.’ When the archive is saved and reopened, it fails to work anymore.
If our hypothesis does not align with your issue, we will explore other potential causes for this occurrence.
Currently, we are unable to replicate the entire process with the archive you provided. If you can reproduce the issue, we would appreciate access to the complete process from you, including importing materials, creating a scatter, saving the archive, reopening it, and encountering the error. This information would greatly assist us in resolving the issue!
Once again, I apologize for the disruption D5 has caused in your work and daily life. We are committed to resolving the problems we have identified!
Thank you very much for your continued support of D5!"
I can confirm this, same problem for me too in v2.9. I feel sad, because we all know how much work we put in a project and in the morning when you want to finish the job, you see all the Scatter is gone and you have to do it all over again. Please fix it guys. Thank you!
Hi there, I apologize. As mentioned, this error/issue was only replicated by “changing the name of the material in DCC.” If you did not use this method, can you please provide us with a detailed step-by-step process for reproducing the issue?
Also, can you confirm which was evident on your end:
Missing scatter sidebar
Scatter Error prompt
Any of your response, will be a great help to us. Thank you so much.
As you can see in the first image, when I select the area where I used the “Scatter tool” by material, I get the following error: “Cannot be parameterized now. Please edit scattering surface to activate it.”
The entire process went as follows: In SketchUp, I grouped all the crop areas with different colors. They are part of the same main model, which is linked with D5 Render. I applied scatter everywhere, and then in D5, it worked perfectly. I then hid the group with the objects from which D5 Render had applied Scatter in SketchUp because I had another object in the background (as seen in the first image from Google Maps), and I needed Google Maps to be visible underneath while Scatter was displayed above.
Everything worked perfectly, and I could disable the crops generated in D5 Render to improve my computer’s performance, as there are quite a few generated areas. The problem arose the next day when I reopened the project and tried to hide the scatter crops in certain areas. I managed to hide them, but the issue was that I could no longer reactivate them. The error mentioned at the beginning persisted.
I repeated the process of adding all the Scatter crops at once, and the same issue occurred the next day. Could this be because I hide the material in SketchUp and D5 “forgets” the Scatter position? I don’t delete them—they’re still there—but even if I unhide them, the error persists in D5.
I’m hesitant to test further because of a project deadline. For now, I’m leaving everything active as it is in the first image, sacrificing a faster workflow.
I hope this detailed explanation helps. Have a great day, and I hope you can solve the issue!
Hi there, thank you so much for your detailed steps. I could also replicate the issue by hiding the object or surface (in SKP) where the scatter was applied in D5, and then the error prompt occurred. I will be forwarding this to my team, thank you again.
Hi there, I apologize for the inconvenience this issue has caused. Can you provide some further information regarding the steps to replicate this issue? In order to test it on our end and give you the best possible solution.
May I know which issue was evident on your end? Is it changing the material name in your corresponding 3d Modeling software? Or hide the surface where the scatter was placed? Thank you.
This is indeed correct, I can confirm it. The error persists and displays the message: "Cannot be parameterized now. Please edit scattering surface to activate it.” Kindly address this issue as it is extremely frustrating, particularly for users working with D5 in a professional environment!
This issue also occurs even if the material remains unchanged. Please, for heaven’s sake, test it—it’s not a complicated process. Simply create a surface in the modeling software and apply a grass preset from the Studio library by scattering it onto the desired surface (not regular grass, which works fine, but a preset from the Studio). Once that’s done, disable and re-enable the object. I’m sure you’ll encounter the same error!
I just want to clarify that these two problems have already been reported, and our team is diligently working on fixing them. As for my question asked previously, we just wanted to know which issue was being experienced on your end since there are two problems/errors encountered or being mentioned in this thread (despite both being related to scatter). Thank you for your understanding