Whether to consider modifying the "~" algorithm in the split

Question

Whether to consider modifying the "~" algorithm in the split, it is difficult to make adaptive segmentation in the current rules. For example, I created a 15m pattern to invade the values in which I have added ~, which cannot be well adapted. Zoom is applied to the 5m or 30m face. Very limited

For example, in this video, I need to apply the same rule to boxes of different sizes. It has a very bad effect.

YouTube

CherylLau · Answer

You could put a case statement in the Facade rule like this: Facade --> case scope.sx < 15: // make the facade however you want it to be when it is <15m else: split(x) { ~15: Pattern }*‍‍‍‍‍‍‍‍‍‍ You can also skip the case, and then you will get small pieces when the facade is < 15m, which I think is what you wanted to avoid. It just depends on what you want. If you don't want to scale the three tiles proportionally, then you have to tell the computer what you do want.

biaozeng · Answer

Sorry, I changed the previous video permissions,...cityengine CGA - YouTube

In some of the smaller buildings in the video, the facade elements of the standard floor are excessively reduced and squeezed

biaozeng · Answer

Thank you very much for your reply. Your method can solve the segmentation of faces larger than 15m in my problem. If it is applied to faces smaller than 15, for example: 5 7 9 11 this size, we still have to create multiple rules separately to judge by conditions. . Not very convenient.