Never seems to slice with slic3r plugin

[LivInTheLookingGlass]

Latest version of all components. No log events seem to be issued.

[kennethjiang]

Can you give me a bit more info about this bug @gappleto97 ?

Did you install the Slic3r plugin? It is available here: https://github.com/OctoPrint/OctoPrint-Slic3r

Were you able to see Slic3r as an option when you use Slicer Plugin?

[LivInTheLookingGlass]

I was able to see it as an option, but when I hit slice no processes were started on the computer, and no log events were emitted.

I installed both via the built in plugin manager.

[kennethjiang]

If you uninstall Slicer Plugin, will you be able to use Slic3r successfully?

[LivInTheLookingGlass]

Yes

[kennethjiang]

Sorry for the delay @gappleto97 . I just came back from an extended vacation.

I suspect that the problem you are experiencing is caused by an error in browser. Can you please open the OctoPrint page in Chrome, load an STL in Slicer plugin? Then open Chrome Javascript console, copy the content in Javascript console and post it in the comment. Thanks!

[LivInTheLookingGlass]

Would it make a difference if I ran it in Firefox? Its a mild pain to install chrome on Linux.

[kennethjiang]

Yes Firefox should work too @gappleto97 . What I need is the Javascript console output.

[kennethjiang]

Were you able to capture the Javascript console output @gappleto97 ?

[kennethjiang]

Do you still have the problem @gappleto97 ?

[kennethjiang]

Closing issue b/c of inactivity.

[mikedmor]

Also having this issue. Found this error in the console on chrome

Uncaught TypeError: Cannot read property 'replace' of undefined at packed_plugins.js:36459 at Pn (packed_libs.js:10658) at Function.<anonymous> (packed_libs.js:10679) at OverridesViewModel.self.updateOverridesFromProfile (packed_plugins.js:36458) at Object.success (packed_plugins.js:36513) at fire (packed_libs.js:3188) at Object.fireWith [as resolveWith] (packed_libs.js:3318) at done (packed_libs.js:8758) at XMLHttpRequest.<anonymous> (packed_libs.js:9124) at XMLHttpRequest.d (raven.min.js:2) raven.min.js:2 Uncaught TypeError: result$$1[key].replace is not a function at packed_plugins.js:36557 at Pn (packed_libs.js:10658) at Function.<anonymous> (packed_libs.js:10679) at OverridesViewModel.self.toJS (packed_plugins.js:36556) at SlicerViewModel.self.sliceRequestData (packed_plugins.js:37218) at SlicerViewModel.self.slice (packed_plugins.js:37258) at HTMLButtonElement.<anonymous> (packed_libs.js:10845) at HTMLButtonElement.dispatch (packed_libs.js:4738) at HTMLButtonElement.elemData.handle (packed_libs.js:4550) at HTMLButtonElement.d (raven.min.js:2)

This seems to only happen with the Slic3r engine selected, and only when this addon is active. When i turn it off everything works as expected.

[mikedmor]

I posted a fix for the problem earlier but ran into a few more issues disabling it. Instead i made the following changes to ~/.octoprint/generated/webassets/packed_plugins.js and it seems to have solved my issue. Hopefully this help get it patched in the next version or anyone else experiencing this problem.

Change at line 36457:

if (self.slicingViewModel.slicer() == 'slic3r') {
    _.forEach(['end_gcode', 'start_gcode'], function (key) {
        if(key in profile){
            profile[key] = profile[key].replace(/\\n/g, '\n');
         }
    });
}

Change at line 36555 (36557 after changing the above lines):

if (self.slicingViewModel.slicer() == 'slic3r') {
    _.forEach(['profile.end_gcode', 'profile.start_gcode'], function (key) {
        if(key in result$$1){
            result$$1[key] = result$$1[key].replace(/\n/g, '\\n');
        }
    });
}

Although i want to also want to mention that this does not completely fix the problem if you have an error in your slic3r ini file, which ended up also being a problem for me. Octoprint/Octoprint-Slicer will not warn about this and the above 'fix' may cause other issues. However this did seem to get it to complete the slicing and allow me to print. Hope this helps patch it.

[kennethjiang]

Awesome thank you so much @mikedmor for finding out the root cause and proposed a fix. Can you submit a PR for your fix? I'll be super busy for the following week but will try to merge your PR whenever I get a chance. Thanks again!