Just received K2 Pro. Not sure how it prints yet. I want to understand and solidify a UI. I do not want to use the cloud and creality print does not allow for fuzzy skin painting so I can not use it as my slicer. I currently use prusaslicer but everyone is using orcaslicer, which is fine for me. I want (don’t need) a wifi connection because the printer has cameras and stuff.
I’ve watched videos about using Orca through ip address , Mobaxterm, Fluidd, Mainsail, PuTTy, WinSCP, Terminus, Bitvise and whatever else. I worked with AI for hours with no results but this morning I think I have fluidd connected to the printer using creality print. My head is spinning just to get a wifi connection. I tried root access and got scared because of the WARNING and complications due to my ignorance. I still do not have my head wrapped around what the workflow is supposed to be. You may go into detail (thank you) or just a simple description to help me narrow done my considerations to one solid and understood workflow through this survey.
SURVEY:
A survey to the community as the lightest weight workflow you are using to access & control the printer without using the cloud and using Orcaslicer/Prusaslicer as the slicer? PS: Is there real concern for using Root Access?
I share your concerns about cloud access. Full disclosure: that issue is why I left the Bambu ecosystem after they forced Bambu Connect.
I had already moved to Orca Slicer long before that. As you probably know, Orca is a fork of Bambu Studio, but in my opinion it is the best slicer out there right now. It feels like a tool built by hobbyists for hobbyists, and that shows in both quality-of-life features and overall usability. It is also robust and well tested because of the community behind it.
That said, I would still use Orca as my primary slicer. Also, because both Orca and Creality Print trace back to Bambu Studio, you do not necessarily have to choose only one. You can use them side by side, with caveats noted below.
To address your questions directly:
-
What is the lightest-weight local workflow?
For your stated requirements, I would say Orca Slicer over the local network, and Fluidd only if you want browser-based control or visibility. If Creality Print is off the table for you because of missing features like fuzzy skin painting, then I would not build my workflow around it.
-
Do you actually need all these tools?
No. I think that is where people get overwhelmed. You do not need every tool people mention. In practice, most people only need a slicer, and then maybe one secondary interface for control or monitoring.
-
What role does each tool play?
Orca or PrusaSlicer is for slicing. Fluidd is a browser-based machine interface. SSH tools like PuTTY, Bitvise, Terminus, or MobaXterm are for command-line access. WinSCP is for file access and transfer. Those extra tools are mainly for people who want deeper access or want to modify things.
-
Is root access necessary, and how risky is it for a novice?
For normal day-to-day printing, no, I do not think root access is necessary. It becomes relevant only if you want to change things at the OS or Klipper level. For a novice, yes, there is real risk there if you start changing files or services without understanding what they do.
-
How do you keep Wi-Fi and camera access without cloud dependence?
Local Wi-Fi access is not the problem. The real limitation is software integration. You can still access parts of the printer over your own network without using Creality Cloud, but once you move away from Creality Print, you give up some of the tighter camera and CFS integration.
Since getting my K2 Plus, I have been switching regularly between Creality Print 7.0, Orca 2.3.1, Fluidd, and, surprisingly, the front panel itself for repeat prints or jobs sent from Orca.
These are my personal pros and cons:
|
Pros |
Cons |
| Creality Print |
Tight integration with the chamber camera. Good control over fans and CFS. |
Very buggy and rough around the edges. Some UI changes feel different for the sake of being different. Poor consistency between revisions. |
| Orca Slicer |
Best overall user experience. Strong quality-of-life features and a mature feel shaped by community development. |
No chamber camera integration with Creality, and no real CFS support. |
| Fluidd |
Browser-based and functional if that is your preference. |
Rough UI. It feels more like a utility than a polished interface. |
| Front Panel |
Clear, decisive feedback. Unlike Bambu, you know what button you pressed and what the machine is doing. |
Limited control over print options, and the UI still feels half-baked. For example, some selections are not sticky. If you go back to Print Again, you may have to reselect options like no CFS and no calibration. |
I still have not found a perfect workflow. If Orca could access Creality’s video feed and better support the CFS, that would probably be it for me. On the other hand, if Creality ever chose to work with Orca instead of just diverging from it, they would be very hard to beat. Too often, Creality seems focused on making things different rather than better, and that creates unnecessary weaknesses in their slicer.
1 Like