10-19-2021, 12:08 PM
Hi
The easy but not optimized solution is to generate the buildings, then test intersections between the buildings' bounding boxes, then delete the intersecting ones.
The optimized solution would be to apply a self-intersection test for the type of the spline you are using. Such test is not implemented in Curvy. I am not familiar with such algorithms, but they do exist, as you can see here: https://www.sciencedirect.com/science/article/abs/pii/0166361589900729
All the splines do offer access, through the API, to the relevant data of their related spline type. So implementing such algorithms using the API is feasible.
I hope my answer helped. Let me know if you have other questions.
Have a nice day
The easy but not optimized solution is to generate the buildings, then test intersections between the buildings' bounding boxes, then delete the intersecting ones.
The optimized solution would be to apply a self-intersection test for the type of the spline you are using. Such test is not implemented in Curvy. I am not familiar with such algorithms, but they do exist, as you can see here: https://www.sciencedirect.com/science/article/abs/pii/0166361589900729
All the splines do offer access, through the API, to the relevant data of their related spline type. So implementing such algorithms using the API is feasible.
I hope my answer helped. Let me know if you have other questions.
Have a nice day
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.