Drape processing time?
-
I got a terrain mesh of ~25K faces, and a curve with ~380 edges which I try to drape onto the terrain. Started the operation at ~09:30 - it's not 12:20. This isn't normal - is it?
I've worked with large terrains before - but can't remember having problems like this before.
Even tried to extrude the curve and intersect - but that doesn't appear to be much faster...
QuadCore 3GHz, W7 64bit, 8GB RAM.
-
It's not always geometry count as I noticed. There are obnoxious mesh & linework combinations that just don't do it right.
And I bet when it finishes draping, you will end up with a bunch of incorrectly draped lines that for the life do not really want to form faces.
-
@gaieus said:
It's not always geometry count as I noticed. There are obnoxious mesh & linework combinations that just don't do it right.
That's what I was wondering. Got any examples you've managed to identify?
@gaieus said:
And I bet when it finishes draping, you will end up with a bunch of incorrectly draped lines that for the life do not really want to form faces.
The damn thing crashed after 3 hours.
And I often get with drape some lines that is always missing. (considering trying to make my own version)I tried extruding the lines I was draping and intersecting that. No go there either. BUT - selecting parts of the mesh and intersecting worked. So by doing that 3-4 times I got the result I wanted within a couple of minutes.
So that strengthens the theory that it's parts of the mesh that causes problems. But unfortunately Drape takes all or nothing...But now I got lots more edges to drape. The intersecting won't be practical workaround.
Just just reinvent the wheel...
-
Well, this is also a plugin so everything that can be expected from plugins working slowly and poorly is valid here.
An "own version" sound interesting!And no, I do not really work with much CAD geometry so I don't have particular examples but have seen (and experimented with) a bunch in the forums already.
Advertisement