Trimble Business Center

I'm having issues with the surface tie function,

I created a surface tie then went into properties to decrease the maximum spacing as at creation it doesnt seem to want to have a maximum spacing less than 0.5m, my issue is that I seem to have clicked twice on the same spot after setting the maximum spacing, this seems to have caused Business Centre to attempt to create a surface tie with a maximum spacing of 0.000, this is obviously impossible and I have ended up with this.

Gutted as I was about 5 minutes away from my 30 minute save reminder.

I asked development to look at this to see if this is really the issue you are seeing - apologies that you got a hang up - this is a trap that we should be checking to make sure that a 0 interval cannot be set if this was really what happened - and we will add a fix for the future that traps that if that is the case. 

I tested this and when I enter 0 for the Max spacing - it just computes the rounded corners for me and comes back instantly - I tried -1 and then .1 and they worked pretty well on my test case and then I tried .01 and then it went off for a long time - so maybe that was what you actually did here (but mine did come back after a while) but I guess we should stop really small values being entered in here as that is likely what happened here I think.

There are so many test cases that are possible that product managers and developers and QA people never think of until they happen - so getting feedback like this really helps to increase robustness of the product if we have defects like these. Normally they are a relatively easy fix when we know about them.

Alan

Thanks for the reply Alan, might be that I have clicked a miniscule distance apart, it was a reasonably significant surface tie, but even with maximum spacing set at 0.050m it regened in about 5 seconds, as it was I had other projects to work on the I opened another instance of BC and carried on working on a separate site for 30-40 minutes. It still hadn't finished at that point so I'd have to guess that it was a minute value not 0.000 as I originally speculated.

We have adjusted the Maximum Interval Setting so that it cannot now be less than 5mm / 3/100ths of a foot - this will be in the next release and will stop the long compute time that you were able to ceate

Alan

That was what I found, and we have now set a min threshold to stop that happening again - thanks for letting us know of this issue - it helps to continually improve things for everyone - much appreciated

Alan