You must be special, M. I cannot find it on mine and it is up to date all the time.

- - - - - - - - - -

Learned something interesting yesterday...

After adding all the filaBoat parts into 3D Builder, it output a file with the extension ".MODEL".
The .3MF file is a zip file so I wanted to know what this was.
Turns out the .MODEL extension is a XML file with a line for every triangle.

What was cool is that when I reloaded the .3mf file, it provided the option to export as .STL and OBJ.

I haven't noticed that before.

This means we can use 3DB's to make build prints and have a ready-to-print .STL based on our build plate.

This means we can use 3DB's to make build prints and have a ready-to-print .STL based on our build plate.

If you are talking about what I think you are, you can do the same with Meshmixer. That's how I prepare all my STL's to print. The ones I post on here are already layed out and oriented the way they need to be printed.

when i connect my cube in windows10, there no happen anything, cube printer successfull instaled, i try print sdk, but still stuck. when using 3d builder, just say fail to load 3d printer capabilities,
i try to use com3 and other, still no happen,

The driver gets confused. It is not a simple printer so it has to have its unique name and registered in the registry as only being available when the printer is plugged in.
I tried to edit the printer and somehow it created a second instance. This one I had to rename and then run the SDK again. I've done that several times until it took.

I use the USB on the computer and the USB-(whatever) on the right side of the Cube.
When the printer is recognized, it allows printing to it. Otherwise it just puts out a junk RAW file.

You say you installed the printer and then ran the SDK? That could have created the confusion mine was having. If you see the printer in your printer folder, don't delete it, just rename it. I think junk lingers in the registry that causes access problems. You shouldn't see the cube printer in "my printers" as installed by the SDK.

At least, that's been my experience. It works but not as robust as we are use to for other printers. This one has some hooks to keep it form being "generic".

Prematurely quitting the print driver will also cause problems. Best solution is to have the Cube display the "maintenance message" which sends a "completed" signal to the print spooler once the file is uploaded to the printer.