donovan6000

You generate it with a slicer program such as Cura or Slic3r. Since I haven't full implemented the same G-code preprocessor as M3D's official software, the printed model won't compensate...

The quality and fill detection are kinda specific, and are based on the official software for the Micro 3D printer. So they were used in M33 Fio to make the...

I looked at the Pursa Slic3r Edition and saw the "Support on build plate only" setting that your talking. You should just be able to add this line, `support_material_buildplate_only =...

Not really sure why it can't create the settings file. You can try manually creating the folder '/usr/share/m3d-linux' before hand in case that's what's causing the problem. I haven't worked...

Unfortunately this isn't something that can easily be fixed by changing M3D Fio's code. M3D Fio and TouchUI are both overriding OctoPrint's CSS to accomplish changing the GUI. OctoPrint generates...

You could implement it in the same way that [M33 Fio](https://github.com/donovan6000/M33-Fio) does.  It uses this [blueprint API](https://github.com/donovan6000/M33-Fio/blob/master/octoprint_m33fio/__init__.py#L11966-L12035) to overwrite an existing slicer profile or create a new slicer...

I created [my own API for fetching the slicer profiles](https://github.com/donovan6000/M33-Fio/blob/master/octoprint_m33fio/__init__.py#L3256-L3308) that's used to [convert the slicing profiles stored in OctoPrint back into their original formats](https://github.com/donovan6000/M33-Fio/blob/master/octoprint_m33fio/__init__.py#L1508-L1720) before sending them to the...

No, M33 Fio doesn't support Micro+ or M3D Pro printers.

I don't plan on buying either of those printers, so I don't have much of a reason to add support for them. So if support is added for those printers,...

Adding support for the Micro+ or M3D Pro printers requires reverse engineering M3D's software and those printers' firmware and bootloader. There's a lot that we don't know about those printers...