When I run the RPS version of convert to linestring my system looks like it completes it but then hangs for 30 seconds to over a few minutes. But if I run the Trimble “vanilla” version it completes quick like normal. Anyone else seeing this?
Can you send me your file, our tool does more tan the TBC Tiol so it could just be the extra things that we are doing that TBC is not doing that may be the difference but I would like to check
Alan
1 Like
Just sent them to you in a message. I’ll try and find the other one I was having issues with the other day and send that to you. I ran the CAD cleanup process first. Then did the Convert process. Last try at the end of yesterday it took the cleanup process 2:30 seconds.
I have forwarded to the devs to take a look. We are planniong to roll Convert to Linestring and Optimize Linestrings into CAD Cleanup anyhow as these are generally used in the “cleanup phase” of a CAD File project, so the timing is good to get this looked at. I saw the same behaviour as you saw at the end of the process. The conversion seemed to take 15 secs for us after regen vs 22sec for TBC but then we have that long lag at the end for some reason which we need to understand what the cause is and where that came from.
Alan
1 Like
Here is a link to a file that will blow up the convert to linestring command. It’s an old .dgn file that has every centerline in Utah in it. Might be a good file to test with.
Tysen
1 Like