A threaded part I created wont open in Slic3r but opens fine in Kisslicer and Cura. Skeinforge fails as well.

Meshlab and netfabb say there are no errors and when exporting the STL from Cura that file opens and slices just fine in Slic3r.
The Cura stl file is about 1/6 of the original file size so there seem to be something removed that Slic3r has a problem with.
Any workarounds to avoid Cura?
The part was created in Sketchup and the problem also appears when trying to open the thread only.

Noone can help you without seeing the original STL file.

Stl attached, printing the cura converted file as we speak. The original file was too large to attach.

Edited 1 time(s). Last edit at 05/30/2015 08:03AM by hsbontop.

Quote
hsbontop
Stl attached, printing the cura converted file as we speak. The original file was too large to attach.

If that's the version from Cura, it's of no use.
That file opened just fine in 1.2.8-dev though.

If the file is too big, link it from a dropbox, onedrive, google drive or whatever place.

Edited 1 time(s). Last edit at 05/30/2015 03:25PM by Mikk36.

Link attached, stl printed just fine (pitch on the thread a bit too narrow though).
Original stl

Quote
hsbontop
Link attached, stl printed just fine (pitch on the thread a bit too narrow though).
Original stl

I see no issue with my Slic3r here even with the original file.

You can use WinRar to ZIP or RAR files that are too large to attach, and enter the max. file size option so that it splits to multiple parts. Then attach each part separately.

Dave

Had to start a new account on my computer as slic3r does not like Swedish letters (åäö) and the administrator account contains one of these which makes saving of settings impossible. That made me wonder if this could be the reason here as well and embarrassingly enough I had renamed the cure converted files without the ä whereas the original file contained that letter. Now everything works fine, thanks for the effort! Have to print another one though as I managed to get the thread the wrong way around, measure once print twice...

Latest versions from github should resolve this unicode character issue.