SoftFever / OrcaSlicer

G-code generator for 3D printers (Bambu, Prusa, Voron, VzBot, RatRig, Creality, etc.)
https://discord.gg/P4VE9UY9gJ
GNU Affero General Public License v3.0
6.7k stars 785 forks source link

Allow import of Prusa slicer .ini files for filament profiles (not stale!) #1648

Closed MAVProxyUser closed 6 months ago

MAVProxyUser commented 1 year ago

It feels remiss that you didn't include a conversion tool to import the plethora of slicer profiles available in the community for Prusa, and make them available to Orca.

Comparing the two we can see similarities. https://raw.githubusercontent.com/SoftFever/OrcaSlicer/6c8b01199107dae1bbb0a10cbf337b1795e5faea/src/libslic3r/Print.cpp

https://raw.githubusercontent.com/prusa3d/PrusaSlicer/287e1e28cd6de02585671d7f74d4e36fddd46674/src/libslic3r/Print.cpp

Sure, let's specifically compare the steps_gcode sets in both snippets to identify the differences related to the "BBS" printer model (Bambu Studio) in the code:

Here are the common steps_gcode entries in both snippets:

Entries specific to the first snippet (not found in the second snippet):

Entries specific to the second snippet (not found in the first snippet):

As we can see, the second snippet (Bambu Studio, or "BBS") includes many additional configuration options specific to their printer model or features, which are not present in the first snippet. These additional options are mainly related to cooling, bed and plate temperatures, extruder clearance, filament properties, gcode control, nozzle behavior, and other printer-specific settings.

On the other hand, the first snippet does include one option, "filament_soluble", which is not found in the second snippet. This option seems to be related to support material and soluble filament.

These differences in the steps_gcode sets reflect the variations in supported options and printer-specific features between the two versions of the code. Each version caters to the specific needs and functionalities of its respective printer model (OrcaSlicer and Bambu Studio).

How can we get a tool to convert the supported elements between both from .ini to .json?

theophile commented 1 year ago

https://github.com/SoftFever/OrcaSlicer/discussions/1636#discussion-5455618

Just about done with a version that does print profiles too.

MAVProxyUser commented 1 year ago

@theophile your base work is great for the Filaments... let me know when you get the print profile too, I've got one I need to convert! Are you also going to do printer profiles, or just the print?

github-actions[bot] commented 10 months ago

GitHub bot: this issue is stale because it has been open for 90 days with no activity.

MAVProxyUser commented 10 months ago

make this fresh...

ALEX-9-99 commented 9 months ago

It would be great if they had some kind of converter layer. I need the whole thing for PP printing with my own profiles.

These two problems could be brought together with one solution OrcaSlicer #575 This would be a bit cumbersome, but certainly feasible for one-off handling, and certainly better than transferring the values by hand and estimating the rest.

SPAZv commented 9 months ago

Im waiting too, maybe will be posibility yo move prusa profiles to orca :)

theophile commented 9 months ago

In the meantime, see if this works for you: https://github.com/theophile/SuperSlicer_to_Orca_scripts/

SPAZv commented 9 months ago

Im not that good in programing language and i try it before but dont know how to do it right :)

wt., 5 gru 2023 o 18:28 theophile @.***> napisał(a):

In the meantime, see if this works for you: https://github.com/theophile/SuperSlicer_to_Orca_scripts/

— Reply to this email directly, view it on GitHub https://github.com/SoftFever/OrcaSlicer/issues/1648#issuecomment-1841282752, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKGQPQA3Y6OIA2KM4WUHHYTYH5KVRAVCNFSM6AAAAAA26VJ2AKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBRGI4DENZVGI . You are receiving this because you commented.Message ID: @.***>

github-actions[bot] commented 6 months ago

Orca bot: this issue is stale because it has been open for 90 days with no activity.

github-actions[bot] commented 6 months ago

Orca bot: This issue was closed because it has been inactive for 7 days since being marked as stale.