Closed vin750 closed 8 months ago
I played with your config bundle and pushed some commits that should help the script process it, but there are two caveats (so far).
First, the script expects the first line of the file to be in the format:
# generated by PrusaSlicer 2.7.1 on 2023-12-30 at 19:47:00 UTC
It must start with a hash, then a space, then the phrase "generated by", then another space, then the name of the slicer. The script needs to be able to identify the source slicer so it knows what conventions to follow when trying to translate the settings. So you will need to modift the first line of your config bundle accordingly.
Second, OrcaSlicer doesn't appear to permit profile names to contain illegal characters such as the asterisks you use frequently. The script will try to convert these and will try to preserve the names, but I don't think OrcaSlicer will respect them. This means that the inheritance structure you've set up probably will not work.
Thank you very much for this, I managed to import everything by the looks of it. Now I need to figure how what works and what doesn't in my Flashforge Creator Pro 2. The first thing is to work out what flavour will work best Kilpper or Marlin.
Do you have any experience with this?
I think you would use whichever matches your printer's firmware.
Hi there,
I am trying to covert a custom profile that uses as post processor for a Flashforge Creator Pro 2 but I am getting some errors. This basically lets me use a dual extruder printer by putting the gcode through a post processor and each extruder is basically seen as a different printer inside the slicer.
Would you be able to assist me with this issue?
Here is the link to the Prusaslicer profile I am trying to convert.
https://github.com/Jacotheron/FlashForge-CreatorPro2-PS-Profile/blob/main/vendor/FlashForge.ini
Thanks in advance