Bug splat with "tube along path"
-
This is posted for the benefit of the community. Please place this post in the appropriate subforum:
SU6 pro just went awol.
I was constructing a quasi-helical rail to a quasi-helical stair component using Tube Along Path. I say quasi- because I had to construct the stair stringers segmentally rather than with either of the native extrusion tools.I added the helical path, consisting of segments of Arc3points, to the stair component using the windows copy, paste routine. When I invoked the tube along path with 12 segments and radius 1", the Sketchup window disappeared and the BugSplat reporting interface opened. For some reason, it will not do an automatic report. It prompts me to go look for the saved data in a local temp folder, where it is saved in zip form and then send it.
Is the Bug Splat thing a clearing house for error reports?
Does anyone know if Google responds to issues involving 3rd party plugins?
This is the 3rd Bug Splat in as many weeks for me. This is the first one I have posted on this forum.
mitcorb -
Bug Splat is the reporting device for errors in SketchUp that cause the program to crash. I don't know what they do with bug splats that occur due to 3rd party Rubies which most of them are. Perhaps Todd would know that. I've never been contacted about bug splats I've sent. fortunately they are very rare in my experience.
-
A bugsplat is a very efficient tool because it contains a lot of info about your system, model, tools (steps) used etc. Thus most of the time they need not contact you because it is unlikely you could add anyrthing worthy at all (unless they'd like to look into the model itself).
From experience however I guess that they monitor these bugsplats as often I have heard that "yes, we received your bugsplat, thanks..." and such.
-
Yeah, they really do watch them. At basecamp I was approached by one of the developers and he told me that some of my bugsplats helped them pin down and isolate a bug in the drape tool that he had fixed for version 7. He was really excited aboutt he fix.
And its possible that the splat won't tell them whats wrong with the plugin, but it could expose problems with how SU functions. So they probably won't contact the plugin developer about it, but they will evaluate if it helps expose a flaw in SU. You should contact the developer of the plugin directly, especially if you can reproduce the splat.
Chris
-
Thank you all for responding.
I am looking at the process I used and trying to reproduce the conditions. If I figure it out, I will try to post the details of the failure.
mitcorb -
I subsequently was able to construct the rail on the stair. When I defined the path with a series of arcs with Arc3points. I was doing this within edit component.
After highlighting the path and invoking Tube along path, a failure occurred. Looking at the file after restarting, the selected path showed several small segments of a couple of the arcs were not active within the component or the group formed during the tube forming procedure. This interrupted path is apparently what caused the "crash".
Well, that's my best guess, anyway.
I hope this is helpful to others.
mitcorb -
Thank you, TIG:
I was not aware of the short path condition and will keep that in mind in the future.
mitcorb -
My TubeAlongPath.rb can fail if the path's line segments are too short.
Also its cousin PipeAlongPath.rb might be more forgiving and better trapped.Also use sensibly few sides for the tube/pipe - having lots of sides adds little to its appearance but multiplies up the number of faces...
Short path segments are trapped [at least an attempt to trap] since SketchUp's FollowMe tool fails on paths with short lengths where the faces it would make on the innermost part of the turns very small. Alternatively you can scale up the path x10 [and then the pipe's diameter too]... that way the face bits never get too small and so there's no bugsplats=... Scale everything down x0.1 on completion...
Advertisement