i first blamed TouchUI but we proved wrong and upon uninstallation of the Slicer, the system worked fine again.

This is what I got after installing Slicer and restarting the service:

Apparently it fails only locally, not remotely.

It tries to load WebGL and that is not supported on the RaspberryPi Chromium browser. Hence the function getExtension is not supported, it seems the library Three.js is throwing this error.

Basically there is no check if the browser supports WebGL, what breaks all other features of OctoPrint and TouchUI.

Hi.

I have a problem.
I have the plugin installed, but I cannot find any configuration. It does not show in my settings menu.
I can't find any way how to configure it and add some slicers :(
Can you, plz, advice?

With tiny mouse movements the scale factor can go to tens or hundreds. Very hard to manipulate.

A few bugs that are probably related:

• "Slicer" dropdown: when changed from CuraEngine to Select a slicer..., it still has CuraEngine checked.
• When Printer Profile is changed to Select a printer profile..., Slice it! button is not disabled.
• probably more...

Overall the user interaction on General tab needs rethinking.

An elegant way to do it seems to treat print volume as a geometry (box or cylinder) and use texture to paint wall and floor. This will help with collision detection too.

There are already a PR for it but orbit has noticeable lag on my computer.

With OctoPrint 1.3.0, it's now possible to have folders within the file upload hierarchy. When slicing a file inside a directory with this plugin, the filename defaults to "foldername/filename.gco" - but OctoPrint is already putting it into the folder by default, and actually strips out the "/" from that name when passing to the slicer. This results in UI confusion because the slash isn't removed consistently (might be an actual OctoPrint bug, I haven't dug deeply yet), so it never notices the slicing is "complete", even though it does actually work.

Ideally the folder name should just not be included in the output filename, since it is still automatically added by OctoPrint. This appears to be how the stock CuraEngine slicing plugin works. Thanks!

Tried to use this slicer. I am unable to upload or create a slicing profile. I have a few created for the default cura slicer, but they do not show up with this one and I cannot slice my file to print.

First of all I'd just like to say thank you for developing anything for people to have and change on their own for free. I'll just cut right to the chase - I have a brand new install of OctoPi and whenever I install this plugin via the url address in the plugin manager, I restart OctoPrint, and then it is broken. I can't login or anything. If you can help me or if you need more information please let me know. Thanks in advance.

Hi, can you please add an option for skirt as well as brim? I use skirt when it's a model that won't have adhesion problems just to prime the nozzle and brim when it's needed. Thanks

Currently slicer or profile options are not shown until 1st model is load. It's not an intuitive user experience.

It seems slicer "freezes" when activated in Chrome (Version 55.0.2883.87 m). It woks find in Edge and Firefox.

I realise this slicer only serves a "minimal" set of profile parameters, but I think it would be valuable to see and be able to edit filament diameter. Some spools I own are 3.0, some are 2.85.

With the last release is it possible to slice multiple objects and print them in one go. It is a great feature but should not be enabled by default, or should be a way to control de behaviour. I have already screw some prints thanks to the left overs.

I think it would be good if the arrange button can be toggled and in that mode append the files, otherwise ignore the previous content and start from zero.

Proposed normal workflow:
1- Upload STL file
2- Slice it
3- Print
4- Upload STL file (previous content are discarded by default)
5- Slice it
6- Print

Slice multiple objects workflow:
1- Upload STL file
2- Toggle arrange button
3- Upload STL file (should append to the existing slice)
4- Repeat...

Is it possible to change the gcode-output-path back to the old behavior?
In the older versions, the gcode file was written in the folder of the STL - very good for sorting.
THe newer version (>0.9) is writing it in the Files-"root" - no matter where the stl is - and must be mover manualy for sorting.

Refactor profile_overrides.js to elevate the following issues:

• profile entries of Cura and Slic3r may share the same name but different types (one is array the other is not).
• Jinja files for Cura and Sli3r are mingled which make it hard to maintain.
• A general way to pre/post-process data, such as converting string <-> float, or removing "%"
• Base class OverridesViewModel may be a bad idea. It causes any event to be fired twice, once for BasicOverridesViewModel and second time for AdvancedOverridesViewModel

Hi, thanks for your plugin, i've been longing for something like this for a very long time!
It works very well, except that it doesn't center the generated model on the bed. That's fine if the print isn't that big, but now i have something that needs 225mm width (i have a Prusa i3 MK2 with 250mm) and the generated gcode places the model partially off of the left edge of the bed.
I have slice the very same STL with Cura directly on my desktop, and with the same profile it generates gcode that puts the model right in the center of the bed.

After a file is sliced and saved as .gco, no analysis is performed. The metadata is missing filament/volume information afterwards.

When I download the sliced file, delete it from OctoPrint and re-upload it, the analysis is started and the correct metadata is created.

After slicing:

Marvin_KeyChain.gco
Uploaded: a few seconds ago
Size: 998.9KB
Estimated print time: 18 minutes
Cost: €NaN

After upload:
octoprint.filemanager.analysis - INFO - Starting analysis of local:testing/Marvin_KeyChain.gco

Marvin_KeyChain.gco
Uploaded: a few seconds ago
Size: 998.9KB
Model size: 112.59mm × 109.48mm × 25.00mm
Filament: 0.83m / 2.00cm³
Estimated print time: 18 minutes
Cost: €0.07

OctoPrint 1.3.0
Slicer plugin 0.8.3

Used a working config bundle from slic3r 1.2.9, imported without problem.
Had to modify the temperature & G-codes (which shouldn't have to be done as this information is in the config_bundle
G code is half the size of the slic3r produced code on my desktop.
Printer won't print

Hello, It installed perfectly via plugin manager. NO slicer engine is in drop down. How to install a slicer engine?

Likely the bug in TransformControl

When i hit the rotate button on the left a bubble with x/y/z input. But i'm not able to close this.

• I am using Chrome Version 53.0.2785.116 m (64-bit)
• Octoprint version is 1.2.16 (master branch)

The code is getting out of control now.

If I slice with a printer profile that has the origin set to 'center', and a printer area of 200x200x300 the gcode generated puts the part completely off the bed to the top-right when viewed in the gcode viewer.

Using the built in slicer without any other plugins works perfectly.

Awesome work, thanks for providing this great addition!

Maybe I'm missing something, but the abitlity to move the object is super critical IMHO.
Is there any support for it?

Thank you!

I noticed that your plugin doesn't have any reference back to this repo in OctoPrint's Update Manager, so you don't get any updates unless you install them manually. I'm guessing that's fixed easily with some additional info in setup.py, but i can't offer a solution right away ;-)

There seems to be a javascript error occuring in Chrome but not FireFox.

Chrome reports this line as faulty:

It's currently a grey block.

Just got this ticket on the OctoPrint bug tracker, reporting it being impossible to login on IE11 and Android under 1.2.17rc1 where it still worked fine under 1.2.16. Couldn't reproduce (and it didn't make sense considering the changes between 1.2.16 and 1.2.17rc1 either), then noticed that in between that update the user also installed your plugin. So I installed it as well and then could reproduce. Not only did the login not work anymore, the whole UI was broken.

A look into the JS console showed that IE hiccups hard on the back ticks contained in this and this line:

My guess is you meant to write ' instead and didn't notice because FF and Chrome are a bit less picky here. I haven't looked through the whole code base, but I guess a grep for back ticks might be a good idea to avoid more variants of that issue when fixing the above two incarnations ;)

After installing the slicer and rebooting the system, the JS code fails with this error, rendering me unable to login to the web app and uninstall the plugin.

Please consider allowing for:

1. Set Retraction - Speed and Distance
2. Default Settings - I use PLA a lot and use the same settings often. Would be nice to have the ability to make a PLA preset that I can tweek slightly as needed - rather than having to re-enter ALL of the settings on each print.

Otherwise - thanks for the excellent plugin!

I have 3 profiles and one is default, the default profile settings are loaded but if I change profile nothing happens, there is no JS error either.

steps to reproduce:

1. set default slicing profile to be 2nd on the list
2. load model
3. change one custom slicing setting
4. try to load 3rd slicing profile
5. on prompt, select "abort"
6. BUG: 1st slicing profile now is loaded and all custom settings overwritten

When modifying a model on the platform (rotate/translate/scale), the new STL file must be uploaded to be sliced. Currently the upload overwrites the existing file.

This isn't an expected behavior and it's also a problem for solving #9 . The solution instead is to upload a temporary STL file when the platform has been modified and then delete that temporary file when done.

With OctoPrint 1.3.0 a possibility to create folders inside the upload folder was introduced.

When you create a folder and and enter it, then upload a .stl, the slicer plugin gives you a wrong output path. It shows something like "Vases/Vase_1.gco". This will result in the creation of a file called "VasesVase_1.gco" in the currently active folder.

Side effect of this problem is that the Alalysis is not performed afterwards. I think this is related to the wrong creation path/filename.

This will result in a gcode file which has no proper metadata and is missing filament/volume properties. Plugins which depend on this information like the History plugin and the Costs plugin will fail.

Would it be possible to port the knockout.js to plain old JQuery?