In the model information dialog, “activate length snapping” is ticked and the value is 0.100000.
Why would this have an impact?
Length snapping is known to create accuracy issues because it forces edges to a specific length.
Try turning it off and see what you get with 52.4105
Best to turn it off in all your templates.
You could turn off the angle snap too but I don’t think that is the issue, it usually respects what you type, although only displays to 3 decimals.
Sorry, yes you are correct, you do need to calculate the angle fully to get the correct length. Once again display precision can round things up, I didn’t realise when you said you were working in cm that you meant 8m of cm.
So yes, when done that way it does show the .000026 error that you got.
I was originally just doing 10 units, not 1000 units.
Again, sorry about that.
Alas, the screenshot shows the line with the error but the error message itself is scrolled off the top. Please stretch the console taller, try again, and make sure it is scrolled to the top. I suspect there may be an issue from the new version of Ruby used in SU 2024 but I haven’t been able to reproduce what you are getting.
Good, No problem.
Btw also mathematically calculated you get the .000026:
c² = a² + b² + 2ab * cos(52.4105°)
= sqrt( 25 + 100 + 2 * 5 * 10 * cos(52.4105) )
You get 8.00000026
1 Like
Sorry, didn’t realize.After entering the second radius (8) and press enter, the console shows:
Error: #<TypeError: allocator undefined for SLBPlugins::CircleIntersect::UndrawnCircle>
c:/users/uwebe/appdata/roaming/sketchup/sketchup 2024/sketchup/plugins/sb_trilateration/trilateration2d.rbe:291:in `new’
c:/users/uwebe/appdata/roaming/sketchup/sketchup 2024/sketchup/plugins/sb_trilateration/trilateration2d.rbe:291:in `createCpoints’
c:/users/uwebe/appdata/roaming/sketchup/sketchup 2024/sketchup/plugins/sb_trilateration/trilateration2d.rbe:136:in `increment_state’
c:/users/uwebe/appdata/roaming/sketchup/sketchup 2024/sketchup/plugins/sb_trilateration/trilateration2d.rbe:279:in `onUserText’
BTW, I have both plugins installed: the SB Trilateration and CircleIntersect.
Sorry, wrong file.
See this one. The precision is not perfect.
Triangle from 3 known sides.skp (174.9 KB)
Aha! I’ve seen that error reported elsewhere as being due to a back-end change in Ruby 3.2, which is used in SketchUp 2024. I’m researching what to do about it ( and why I didn’t get the error). I suspect it may somehow result from those two extensions clashing with each other.
Thanks for bringing this to my attention! I’m surprised and disappointed that no one brought this to my attention earlier. It suggests that nobody is running the extension 
1 Like
I discovered that for some reason I hadn’t installed SB Circle Intersect in SU 2024. I did so, and then I could reproduce the error. So it definitely is some kind of clash between them. I think it is because I shared some code between them without adequately isolating it, though why that provokes the error I still don’t understand. Anyway, I modifed SB Trilateration so that it isolates its version, and now I don’t get the error any more. Please try the attached version and let me know if it cures the error for you. If it does, I’ll post the fix on SketchUcation for others who may have the extensions.
SB_Trilateration.rbz (609.5 KB)
1 Like
I use it sometimes but haven’t used it in 2024 yet because I subscribed only a month ago…
I tested the version you attached and it works. Great job!
Also the 3D trilateration still works.
Btw, I installed the CircleIntersect plugin only after I discovered that the 2D trilateration did not work. So the error was not related to having both plugins installed at the same time.
And you have one customer more now 
Thanks. This makes sense and is as good as it gets, when intersecting arcs with many segments in SketchUp.
Side remark: when I open the file in my SU 2024 version, it tells me that the file was created with a newer version of Sketchup.
I have Win 64 bit 24.0.594.241 and I thought this is the latest version.
What version do you have?
2024, maybe it is because I use a Mac.
The mac version is a bit higher, probably that‘s why.
The final digits of SketchUp versions on Mac are always higher than on Windows, I think just to distinguish between the two builds.
The only reason I drew the guide line between the guide points was that the points can be very hard to see if you are working with a model that already has content in the general area where they land. The guide between them makes them easier to find. You can add guide lines along the imagined sides by activating the tape measure then clicking on an end of the baseline and one of the guide points. Quick and easy, so I didn’t see the option to draw them as necessary. But if enough users ask for it, I’ll add them (per previous comment, there don’t seem to be very many!).
I am fine with the way it is.
Maybe there are more users than you think. Having to intersect arcs is not needed on a daily basis. As an alternative, one can calculate the position of the point manually or approximate it. But knowing that there is now an easy way to intersect arcs precisely will help me going forward.
FWIW, I took a look and drawing the triangle sides vs the centerline is very easy.
The origin of this extension was to provide people who do surveys indoors or outdoors using digital range measurements to easily plot the triangle corners to full computer accuracy, without any approximations (such as circles or arcs with many sides, which are still approximate) or manual calculations.
1 Like
Just installed v 1.1, all fine now as it is. Thanks!
1 Like
I can confirm that v 1.1 is working here too.
1 Like