Hi, does anyone know if it is possible to make a floor using smartpart? The floor should adapt to the shape of the room. Or is it better to make it with the "smart installation" function? the attached scheme is a simple typology but it could also be more elaborate (for example with octagons or other types of flooring)
There is nothing to add to the answers given here.
If you do want to implement it in a SmartPart, have fun!
Not impossible, but far from easy!
Not impossible, but far from easy!
Not impossible, but far from easy!
I have asked you several times NOT to do this!
The inadequate performance in the SmartPart was also a reason for this! The creation of hundreds of plates and the subsequent
boolean intersection with the outline body simply takes time. This cannot be accelerated any further. In the preview, you could cancel the creation after 10-20 plates so that the mouse can be moved. In any case, the final construction of all plates takes time!
The inadequate performance in the SmartPart was also a reason for this! The creation of hundreds of plates and the subsequent
boolean intersection with the outline body simply takes time. This cannot be accelerated any further. In the preview, you could cancel the creation after 10-20 plates so that the mouse can be moved. In any case, the final construction of all plates takes time!
No, I didn't say that. I merely advised against a user wanting to create such a SmartPart who knows little or nothing about SmartPart programming.
There is actually nothing that is not possible with SmartParts. With a few tricks, you can also get the performance of Boolean operations under control. As proof, here is my implementation for this task. (see Plattenbelag.smt)
You can view, analyze and improve the SmartPart...
I tried the smartpart and it works well...the only aspect to improve is the behavior in section as the hatch, pattern and facestyle are seen superimposed between tiles and joints as the joints are created with a "prism" over the entire occupied surface
This problem ist fixed here
