I paid for S3D years ago and although I haven’t used it since getting the P1S, sadly “retired” my CR-10S, I still love its robust functionality! For me, one of the best features of S3D was being able to pause a print, swap out an E3D Revo nozzle size and then resume printing!
Example:
Base = 0.80mm
Main = 0.40mm
Smaller details could be done with a 0.20mm
I’ve reached out to S3D’s Support, which I was surprised is still active, and they said they would let me know about any Beta testing for multiple nozzle setups on the U1 once they have a unit to work on. While that is encouraging, if anyone here in the Community has S3D and would like to work with me on this, I’d love to hear from ya!
I have started to see the docs and orcaslicer scripts. The biggest issue translating it to s3d is the absolut lack of documentation on the S3D side. Seeing snapmaker orca slicer scripts and the structure shows the basic, and since the tool wipes are done in relative I understand that most of the tool change is managed by the firmware. Clearly there’s extra code to wipe etc, but that can be mimic. I have extracted the full script variables from s3d (simple hex edit) and will start to dig.
Why? Because the Orca/Snap slicer lacks 3 very important features for my business:
Doesnt allow REAL per object settings like x/y expansion (only allows for the Whole print) so I can apply it on small objects like logos without affecting everything
Doesnt have a ‘set NUM’ layer to be Solid, so no full control. Why I need this? Because as soon you have a group stl with small objects on top, the toplayer path changes, and I need a perfect clean top layer, even if is a waste of material
There more stuff, but not critical for me
Anyhow, I have 3 months till my U1 arrives. Lets see what can be done. Worst case scenario I will just rebuild snapmaker slicer and add options. I hate coding, but work is work
Me too! There’s much the slicer is ok, but the real per-object of s3d gives a freedom thats hard to beat. Specially when I need constant repetition. And the lack of ‘save X object’ setting is quite annoying. Got time ofc so will dig it. The full list of variables from s3d might ‘work’ to make a profile, but this will take a serious amount of time without s3d documentation (and that’s something they could provide so easily, it bugs me out they never did)
Just did proper digging into this modifier and yea, doesn’t work for x/y expansion
Found a workaround, but probably the best option is to recompile orca removing the ‘error’ that doesnt allow floating objects unless they have supports. Ofc with the modifier I could deny the slicer to make supports hahahaha. The error is silly in so many levels sometimes makes me thing that slicer-coders only print boxes in their lifes
Have you reached out to Support? They’re still very responsive to initial tickets, for what that’s worth; just not sure about follow-ups. Also, if you want to list out specifics that you need from them, I’d be happy to send in the request. I’ll send over a request right now stating that the Community is looking for S3D documentation as we try to figure out how to properly slice for the U1.
So many great S3D “features” that aren’t standard on other slicers! I remember the first time I tried to put a part in the air and Bambu Studio just kept slamming it back onto the plate…
You’ve got me excited that this may actually get some traction! Always loved how robust S3D is and even to this day, just opening it and see its interface makes me smile
Indeed I did send a support ticket to s3d asking for a) documentation of script to make a profile and b) did send the whole list of U1 orcaslicer scripts just in case they can do one OR show me how to script the before tool/after tool.
So far the best script info I got is from um3 machine, it uses a mix of replace/index and after tool0 etcetc stuff that could be used, ofc the problem is that the way s3d needs the script it could be quite big chunk of script since theres 4 tools and the all combinations of 1/2 1/3 1/4 or 2/1 2/3 2/4 3/1 3/2 3/4 4/1 4/2 4/3 tools
Orcaslicer script info is ok-ish. But seeing the gcode theres also added ‘wipe’ motions. So overall there a lot of stuff to script. I will searching for info and do some the weekend. Overall it looks like a week job, but ofc I cant use all my time to this, so maybe before the printer arrives I have something. Ofc I will publish it so more ppl can check
If you use Simplify3D, please download and use at YOUR OWN RISK! I’m excited to give this a shot and will do my best to test this weekend. Updates will come after I run a couple prints
Thank you for your patience, we have a test profile developed for this printer.
Follow these steps to import and use the profile:
Download the attached file.
Open Simplify3D, go to File > Import Printer Profiles…, and navigate to the saved profile. This will import the settings into the software.
To start using these new settings, click Edit Process Settings, and then choose the new entry at the very bottom of the Select Profile drop down list.
Multi-extrusion processes are recommended to be used with the Multi Extrusion Wizard.
Here are the steps by steps instructions for using the Multi Extrusion Wizard:
Have 2 or more models loaded.
Add a process.
Go to Tools → Multi Extrusion Wizard.
Select the profile of the printer you’re using, and select the desired auto-configurations.
Drag and drop the models to the desired extruders.
If you’re printing a single model with two materials, leave the Align model origins and Group models checkbox checked (bottom left of Multi Extrusion Wizard). If you’re printing multiple models, uncheck those checkboxes.
After pressing OK, you should now see the Processes created and ready to be sliced.
I would highly encourage you to do a few test prints and closely monitor the machine at first. Please pay special attention to the starting and ending behavior.
Please let me know if the thumbnail and build stats show up properly, as well as the performance of the profile.
Got the same email, published in the discord for reference. Will check tomorrow to see the gcode. Good news if this gives a basic start. Also great news my U1 will arrive a month earlier yay!
Did a basic setup to check the gcode (ofc I cant actually print) seems all ‘ok’ at first sight. Ofc to actually see the gcode on s3d one needs to comment temporally the toolchange script Z2 hop, otherwise the gcodepreview shows all a mess, but since is just a relative motion it should just do a Z hop. Comment to preview gcode, uncomment to printtest
.
