Core One Start and End Gcode for other slicers
Has anyone been able to create the start and end g-code for other slicers so they can use full functionality? I have an Elegoo Centauri Carbon that is out performing the Core Ones seams by light years. I know it's the PrusaSlicer at fault, I have been doing this too long. I just want my Superslicer back, and it's non existent seams.
Yes... I tried prusas version of scarf joints, their is not enough options. I got close to perfect but the speed during scarf joint math changed and so did the sheen, then went from PLA to PETG and PETG bulges no matter the PA. (stupid values) Elegoo did it better and there was no noticable sheen change, superslicer said scarf joints were crap and moved on. I think the reason was for the abandoning of scarf joints is that the scarf joint is too subtle for many machines and brute force and ignorance is a better choice. Elegance has no place with machines with 10000mm/s/s+ acceleration. I printed a scarf at 2018 speeds and it was kinda nice; but no, we're not doing this.
Yes, I'm tuned with the overly priced shipping cost accelerometer. Notable improvement in surface finish, wonderful surprise.
Yes, tensioned the belts to an insane amount. I know more than you.... Now
1kg lost to pressure advanced tests. it's fine. Look, PA is fine.
I print round things at times, prusaslicer cant even recreate the parts that were printed at prusa headquarters, that are on the machine. If there is any corner to hide the seam, prusa CoreOne is legendary and I forget that failure is an option. The CoreOne, I hit print, drive to work, and the finished product is just.... There, done. It's nuts, it's so good.
yes i printed slow
The reason I bring this up is because, the code that is in the start and end g-code I really want, I just don't know enough to ask the right questions on how to convert it to other slicers.
Give me no seams. please someone, I did it with a anycubic mega s. We can do it with a Core One!
THE FILAMENT CAME OUT OF THE ACTIVE DRYER!
Elegoo wasn't perfect but the sheen didn't change and the it was two half seams as promised.
RE: Core One Start and End Gcode for other slicers
The reason I bring this up is because, the code that is in the start and end g-code I really want, I just don't know enough to ask the right questions on how to convert it to other slicers.
I am not sure I understand. Why would the G-Code be slicer dependent? The startup and end code are all instructions to the printer firmware -- setting temperatures and fans, probing the heatbed Z profile etc. Shouldn't these be the same no matter which slicer is used?
I know more than you.... Now
Would you consider sharing what you know?
RE: Core One Start and End Gcode for other slicers
The slicers I have tried all throw errors as some M codes are not recognised, most really hate the 'if else' coding as well. I guess I'll have keep deleting lines until it works.
The comment about the PA knowledge was my poorly executed humor as always. Mostly I've just printed too many towers and individual samples that I'm confident of the settings on my machine. Sorry no usefully information, other than that I focus on the seam quality more than line quality when tuning.
RE: Core One Start and End Gcode for other slicers
Orca Slicer's "Nightly Build" got a commit on 14th of April with tested Core One profiles and received an update-commit on 2nd of May.
No idea about other slicers, but maybe you can work your way up from the Orca profiles.
https://github.com/SoftFever/OrcaSlicer/releases/tag/nightly-builds