Failure when sclicing some objects

Hi,

I'm not sure if this is a bug or (more likely, I expect) I'm just doing something wrong.

Some objects fail when I try to slice fail with this message (repeated)

"segment = boundarySegment.getSegment(boundarySegmentIndex, boundarySegments,
self.perimeterWidth, self.runningJumpSpace)
File "C:\Reprap\Reprap Running Apps\skeinforge 47_reprap_python_beanshell\skei
nforge_application\skeinforge_plugins\craft_plugins\comb.py", line 149, in getSe
gment
end = self.boundary.segment[1]
AttributeError: 'list' object has no attribute 'segment'"

Processing halts here - no activity after this point.

Full slice history for this is here:
Alligatorfail-16-02-12.txt

The Skeinforge help tab says version is 12.01.13
(though I think it's also version 47 as can be seen in the error messages)

This happens for some but not all objects. In this case it was:
[www.thingiverse.com]

I know it also happens with this:
[www.thingiverse.com] (front part)

I suspect it may be related to objects that are 'imperfect' (e.g. say things like "This should never happen, there is a hole in the triangle mesh, each edge should have two faces.180412 [119833] [60503, 60533] Something will still be printed, but there is no guarantee that it will be the correct shape.")

Things I tried:
- Making sure all code & the object are in the same directory structure on C: (Windows 7)
- I use 2 monitors. I saw a thread that seemed to suggest that might be a problem - so reduced back to single monitor mode. No luck.

Any suggestions???


Thanks

Pete

The alligator STL file does have some problems.
You might try using the FREE netfabb Studio Basic program to fix the problem.

There is nothing wrong with the Tie Interceptor STL files although I would recommend printing my derivative with registration holes instead as it makes it easier to assemble.

---

Bob Morrison
Wörth am Rhein, Germany
"Luke, use the source!"
BLOG - PHOTOS - Thingiverse

For anyone who finds this page and has this issue: its a bug in the Comb plugin from Skeinforge, see for example: [groups.google.com]

Key part of this topic:

Quote

Got it, if you edit the file
"skeinforge_application/skeinforge_plugins/craft_plugins/comb.py"
On line 149 it says "end = self.boundary.segment[1]", as far as I can see
this should be "end = self.segment[1]"
This code normally never seems to trigger, only when there are really small
or thin areas to be found.