X1c in LAN mode + developper mode - Orca slicer crash when sending prints

I’m a bit at lost , with much less knowledge / experience of 3D printing than most, but would like to use my X1C from Orca slicer , on my home PC
I don’t need any cloud service nor app on my phone , but would like

  • the video to work in Orca, (it only freezes , and suggest to install / reinstall the network plugin),
  • to be able to navigate in the external SD card to add / delete files, without the need to open an FTP client (the printer is in a second building, sharing LAN)

In order to use the drying features of my AMS2, I updated the firmware of the printer from 1.8.2 to the last version,
The firmware by itself is fine, and I was able to slice and print a few models, but 2 weeks later I 'm getting Orca crash when I send a print, or even try to send the file to the printer Same models / files are no problem in Studio on the same printer, so SDcard, LAN settings and so on seem out of concern

It seems related to Orca not being able to reach the printer , as the printer is visible in Orca, but sending a file or print order opens the confirmation pop up, which freezes and orca crashes without any warning message

quite frustrating, and I don’t know where to start to fix this other than reverting the firmware to the old version, and or reinstalling Orcaif there’s a better place to ask

thanks in advance

any suggestion welcome, including a better place to ask , if this not the right one

Orca is a separate program from Bambu Studio. There is no guarantee that Orca will be compatible with your printer. It’s not a supported-by-Bambu tool.

any suggestion welcome, including a better place to ask , if this not the right one

Go back to Studio. Bambu isn’t going to be interested in helping you solve this problem. Is there something Orca does that you need, that Studio does not? As a beginner, I would bet the answer to that question is “no”. So why are you wasting any time with Orca instead of using the tool Bambu actually supports?

I’m sure BBL has no interest in solving my questions, hence the part about posting elswhere :baby_angel:

Thaks for your answer, I’ll give a bit more background to explain why I’d rather keep using Orca (sorry for longish post)
I started using this printer with Sudio, but quickly switched to Orca as prefered the user interface (even cose to the Sudio, the icons are much more readable for me) and some of the calibration tools, following the suggestions of the previous owner

This worked fine , always in LAN mode as my workshop as no internet access, and I don’t find any benefit in BBL cloud system so din’t missed it, my only gripe being the camera stream failing in Orca , while suggesting to reinstall the network plugin

During the last “black friday” period , I bought a 2nd AMS, and choose the AMS2 for its drying capacity. I could not use it until BBL publish an offline X1c firmware I could install, as moving the printer + 2 AMS to my home for internet accces was not practical.
I had contacts with BBL support, who understood my concern, and was informed this firmware should be available Q1 2026, and I have non complain on this

Then Q1 finished, and I finally was able to update the printer, and both AMS, and the drying function is working fine : happy me :grinning_face:

I could print and send G-code as before, but after a few weeks, I had this crash while trying to print a model from makerworld.
Then I discovered this was not one model, but any model , even those I’ve already sent and printed

I suspected some SD card corruption, but I could send and print them from Studio without problem

I still use Studio, when I want to print directly but really prefer using Orca as my slicer, and currently export the sliced file, and copy it to the printer SD card using a FTP client

I may reinstall Orca, to clear any corruption risk, but before going back through several firmware to check if the problem is there or not, I thoughht I could ask on here as I’ve seen I’m not the only one to use Orca

I’m not ranting about the firmware itself, as needed it, and I’m not even sure it’s responsible of this : just looking for a way to diagnose and sort this

The best place for OrcaSlicer questions and help is

There are also OrcaSlicer discussions on Discord. I find it difficult to locate solutions on Discord, but it apparently works for some.

I cannot offer a definite solution for your crashes because I’ve never had OrcaSlicer crash.

On GitHub, look at Discussions or Issues for similar problem reports, or submit your own Issue.

If your computer has both an internal GPU and a discrete GPU, you might try forcing OrcaSlicer to use just one or the other; that could isolate the problem to a video driver.

You might also back up your current installation and try the OrcaSlicer Nightly Build. Many times issues are fixed without an announcement until they become a beta build. Nightlys are pre-beta, so there is some risk, but I have never had a problem that could not be fixed by re-installing an earlier build.

My printer is also in LAN-only mode and blocked from the internet, but I have pre-authorization firmware. You need the newer firmware to use the AMS2, but if you also set Developer mode on the printer, you should be able to print directly from OrcaSlicer (or Studio) without the need to export and use FTP.

2 Likes

I’m sure this should work, as it had worked for a while :smiley:

I went to the Github looking for a newer version, but found none, and the problem could be related to MS updates, or many other causes

I’ll have a search on the Github discussions, rather than Discord (where I struggle to follow the various sub forums)

marking this as solution as I’ve got plenty to read now

edit : such crash are referenced in the Orca GitHub , in relation to Bambu network plugin calls, and bugs are referenced
@lkraus thanks again for pointing me in the right direction