Prusaslicer: Printer profiles for printers other than Prusa.

[RogueBear]

More printer profiles for printers other than Prusa. I own a Mk.3S with MMU2S but I also own a Cr10S Pro and Wanhao i3 plus. I would love to make Pruca Slicer my one and only slicer, but I have great S3D profiles for them.

_Is this a new feature request?_

Yes.

[neophyl]

Why not create and save your own ? I have a modified direct drive cr10s as well as my i3 and I use PrusaSlicer for both.
Just because there aren't prebuilt ones doesn't mean you can not do it.

Go the forum and start a thread asking if anyone is willing to share any they have already and I'll post a copy of mine and maybe others who have them will post up too. Also I believe there are various CR10 groups that you could ask if anyone has a slicer profile.

[RogueBear]

I have built my own I just think that Josef's team might do a better job than me.

---

From: neophyl [e-mail]
Sent: Tuesday, June 25, 2019 9:19:07 PM
To: prusa3d/PrusaSlicer
Cc: RogueBear; Author
Subject: Re: [prusa3d/PrusaSlicer] New feature request. More printer profiles for printers other than Prusa. I own a Mk.3S with MMU2S but I also own a Cr10S Pro and Wanhao i3 plus. I would love to make Pruca Slicer my one and only slicer, but I have great S3D...

Why not create and save your own ? I have a modified direct drive cr10s as well as my i3 and I use PrusaSlicer for both.
Just because there aren't prebuilt ones doesn't mean you can not do it.

Go the forum and start a thread asking if anyone is willing to share any they have already and I'll post a copy of mine and maybe others who have them will post up too. Also I believe there are various CR10 groups that you could ask if anyone has a slicer profile.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/prusa3d/PrusaSlicer/issues/2560?email_source=notifications&email_token=AEXQ6QJZBCWZSJ6NFHJZJIDP4J4TXA5CNFSM4H3JLVTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYRPA2Q#issuecomment-505606250, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEXQ6QONKVLOHZZY52J2QBLP4J4TXANCNFSM4H3JLVTA.

[bubnikv]

We simply cannot tune and maintain profiles for any 3D printer on the
planet. We will be happy to merge the profiles for other printers if they
are provided by the community. You basically need to provide a file in the
same format as
https://github.com/prusa3d/PrusaSlicer/blob/master/resources/profiles/PrusaResearch.ini

út 25. 6. 2019 v 22:25 odesílatel RogueBear [e-mail]
napsal:

I have built my own I just think that Josef's team might do a better job
than me.

---

From: neophyl [e-mail]
Sent: Tuesday, June 25, 2019 9:19:07 PM
To: prusa3d/PrusaSlicer
Cc: RogueBear; Author
Subject: Re: [prusa3d/PrusaSlicer] New feature request. More printer
profiles for printers other than Prusa. I own a Mk.3S with MMU2S but I also
own a Cr10S Pro and Wanhao i3 plus. I would love to make Pruca Slicer my
one and only slicer, but I have great S3D...

Why not create and save your own ? I have a modified direct drive cr10s as
well as my i3 and I use PrusaSlicer for both.
Just because there aren't prebuilt ones doesn't mean you can not do it.

Go the forum and start a thread asking if anyone is willing to share any
they have already and I'll post a copy of mine and maybe others who have
them will post up too. Also I believe there are various CR10 groups that
you could ask if anyone has a slicer profile.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<
https://github.com/prusa3d/PrusaSlicer/issues/2560?email_source=notifications&email_token=AEXQ6QJZBCWZSJ6NFHJZJIDP4J4TXA5CNFSM4H3JLVTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYRPA2Q#issuecomment-505606250>,
or mute the thread<
https://github.com/notifications/unsubscribe-auth/AEXQ6QONKVLOHZZY52J2QBLP4J4TXANCNFSM4H3JLVTA

.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/prusa3d/PrusaSlicer/issues/2560?email_source=notifications&email_token=ABMPSI4CJL6KC4IKTGKIJ2DP4J5LBA5CNFSM4H3JLVTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYRPSPY#issuecomment-505608511,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABMPSI5V6QZJ56QCEPFHXBDP4J5LBANCNFSM4H3JLVTA
.

[mvadu]

I agree with @bubnikv I use Prusa Slicer with a TierTime Cetus printer. But my printer has its own tweaks which are not even covered by standard gcode (see my Prusa profile for Cetus) which I would never expect to be covered in Prusa Slicer.

[DrLex0]

I have been using Slic3r, then Slic3r PE, and now PrusaSlicer, with a FlashForge Creator Pro and I've made my own profiles and post-processing scripts. I agree that it is not the Prusa team's responsibility to maintain profiles for non-Prusa printers, it's called ‘PrusaSlicer’ after all.
If any effort is to be spent on this, it should be to make it easier for users to get automatic updates for other profiles. There's now this vendor presets thing, but I cannot figure out how I could submit for instance my profiles into it.

[bubnikv]

@vojtechkral is refactoring the support for the 3rd party profiles as of now. We are planning to support 3rd party profiles the same way Cura does, but it will take us some time to tune up the process of accepting the 3rd party profiles, testing them etc.

[Deneteus]

That would seriously save people time when switching back and forth to different printers. I mean I use PrusaSlicer/Slic3r as well as as S3D and Cura and I hate having to transpose settings between programs for multiple printers out the box. You can import those default printer settings from existing Marlin example config files that have already been tested to death. Since the default print speed settings are also in there it could be used to optimize print time estimates as well.

Work Smarter, Not Harder!!

[drmulligan]

I was about to make a feature request to be able to import profiles from the other major slicers but it looks like adding my opinion here would amount to the same. Please add a feature which would allow importing my active profiles from at least Cura and Simplify3D. If they don't quite 1-1 transpose, make it a wizard and ask the user to solve issues.

[neslekkim]

I see there are commits for profile for Ender3, are we going to see support for Ender5 and Ender5 plus also?

[rkarlsba]

I was wondering about CR10S as well. Ender 3 is already in the rc4 and CR10S (or similar) isn't that different.

[bubnikv]

We hope for contributions of 3rd party printer profiles.

st 18. 3. 2020 v 10:43 odesílatel Roy Sigurd Karlsbakk <
[email protected]> napsal:

I was wondering about CR10S as well. Ender 3 is already in the rc4 and
CR10S (or similar) isn't that different.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prusa3d/PrusaSlicer/issues/2560#issuecomment-600520963,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABMPSI6E7QOBPUZVMPJVTZTRICJURANCNFSM4H3JLVTA
.

[bubnikv]

@DrLex0 Are you interested in adding your FlashForge Creator Pro profiles to PrusaSlicer wizard? @rtyr may help you with that.
I understand that we would likely have to bundle the gpx utility with PrusaSlicer, which is roughly 100kB zipped. I don't think that is an issue. Cura distributes gtk utility with the X3GWriter plugin, S3D distributes it by default.

[DrLex0]

@bubnikv That would certainly make things easier for the users of those profiles.
My concern is that getting these profiles to work without surprises on every platform, still requires a bit of a convoluted recipe. This can be seen from the instructions that are now in the README of the GitHub repository. Especially Windows is problematic because it requires getting either a bash post-processing script to work under WSL or Cygwin, or a more limited BAT alternative of this same script (when invoking bash isn't possible).

The post-processing script is currently essential to avoid a problem when printing with only the left extruder, which is caused by inability to specify the tool number per extruder, and code in a single-extruder profile always being generated with T0 arguments (issue #2210 or Slic3r 4003). If this could be resolved, then for basic functionality it would suffice to invoke gpx with arguments -p -r1d as the final post-processing step.

[mvadu]

@DrLex0 any reason why the scripts can't be ported to powershell? since powershell is available on Linux, Windows as well in WSL?

[DrLex0]

@mvadu I have zero experience with powershell, and none of the platforms I use PrusaSlicer on, have built-in support for it. I'd rather convert the script to Perl because at least I'm familiar with that, it is available in Linux (and therefore WSL) and OS X by default, and installing a Perl runtime in Windows is pretty easy (and is by the way required for the non-WSL script anyhow).
But my point was that we could do without any script at all, if the tool number issue would be solved.

[bubnikv]

@DrLex0

The post-processing script is currently essential to avoid a problem when printing with only the left extruder, which is caused by inability to specify the tool number per extruder, and code in a single-extruder profile always being generated with T0 arguments

How about to provide a "replace" script inside PrusaSlicer? Something like S3D
https://simplify3dwiki.com/w/index.php/Filament_change_using_REPLACE
https://forum.simplify3d.com/viewtopic.php?t=1959

We have the boost replace available
https://www.boost.org/doc/libs/1_53_0/libs/regex/doc/html/boost_regex/ref/regex_replace.html

How about to add a multi-line input field for multiple regexp replace commands? Would it resolve the need for an external post-processing script?

[mvadu]

@bubnikv A built in replace command would be an welcome move. It may not solve @DrLex0 needs, but it will definitely help others. In my specific case, I am using a Post Processing Script to trigger powershell to replace M73 with echo because smoothieboard I am using does not support M73, but supports echo.

"c:\windows\System32\WindowsPowerShell\v1.0\powershell.exe" -Command "& { (resolve-path \"$($args -join ' ')\" | get-content | ForEach-Object { if($_ -match \"^M73 P(?"<percent>"\d+) R(?"<timeleft>"\d+)$\") {Write-Output \"echo Completed:$($Matches.percent)%, $($Matches.timeleft) minutes left\"} else {write-output $_}}) | out-file -Encoding ascii $($args -join ' ')}";

[DrLex0]

@bubnikv A replace would help if it supports backreferences, which apparently is the case for boost regex.
But it would still be an ugly workaround, and the workaround also only works by the grace of GPX assuming that an M104 command without a T argument is meant for the currently active tool.
The best solution would still be the possibility to override the implicit tool number with an an explicit one in the extruder settings.