@vladimir_michl wrote:
Do not underestimate Fusion 😁
This isn't a question of underestimating Fusion.
I've done this stuff many times and have demonstrated approaches to "real" textures in Fusion.
The video, which is more than 5 years old by now, shows how I create a procedural texture in Blender and then transfer it into Fusion.
As you have explained (and I explain in the video), the mesh can get pretty dense and the finer the texture the finer the mesh has to be. That means the conversion into a T-Spline and then NURBS surface can be slow.
The imagetosurface tool is a Python script (IIRC) that is naturally not very fast either.
The end result of this exercise is then to be 3D printed, so the output is a triangulated mesh. In essence, the imagetosurface tool uses an image to create a height map representing a quad mesh; that mesh is then converted into a T-Spline, and then a NURBS surface.
That is computationally exopensive and slow. Iterations, for example, because the image doesn't have enough contrast range than require iterations, which make this even slower.
Once done the whole thing is again converted into a mesh. That only makes sense if a user is allowed to limit themselves to a single application.
On the other hand, with mesh modeling tools, the effects of parameter changes are often in real-time.
My post is more of an encouragement for users to broaden their horizons and not get stuck with a single 3D modeling application or, even worse, a single CAD application.