I also have a DTSE9 and it’s been on my keychain for at least 10 years now :D

Recently I have just gotten 2 nvme ssd enclosures and have been very happily using them for the super quick image writes. I just checked if there’s some compact 2230 enclosures and some of those even have keychain attachment points… they definitely are a bit bulky for a keychain but I’d argue they still are an option and will look similar to a keyfob :)

It’s a wobbly affair but it does work and Bambu does offer it as an option with a mounting bracket you can print. I… just put my AMS to the side because my table is already kinda scuffed :D

Ideally you would never have to because you just have the two people come up with their part of the password and then initialise the LUKS partition together. Sorta like a key ceremony

You can also just split the password for a single LUKS into two parts and give one each to the two people :D

But does it splatter better than Vegemite?

Don’t bring the marmite into this!

well it was less underextrusion and more the printhead just trying to go supersonic at those spots and the material just didn’t flow fast enough :D

I also figured out, I can adjust the max volumetric speed of the PETG filament settings and that will limit the wall speeds autumatically

Edit: This turned out to interact weirdly with layer height changes, I ended up just reducing the max speeds.

Looks like the default speed settings in the slicer was just too fast :D

So yeah, that solved it! Set it to 50mm/s maximum and it just disappeared! Thanks for the suggestion :)

I just spent some more time observing and yeah, the printer tries to go super sonic for the walls there with up to 150mm/s :kekw:

I added some pics

It’s kinda not at the start or end of the layer. The layer starts with the inner wall, which prints fine and then it does the outer wall which doesn’t do fine.

Which corresponds to the wall here

What slicer are you using?

Bambu Studio 1.8.4.51

Thanks for the input!
So the thing I was trying to print was this: https://www.thingiverse.com/thing:6365845
Ideally you’d just print it in PLA but I only had one colour PLA so I thought, might as well gather some PETG printing experience :D
The part in question is red_panda_low_poly_V1_-_head_A_red.STL and I tried to print it on an odd angle to make sure that most of the outwards facing walls were on the top, because anything that needed support turned out so hideous.

Also it seems to appear on any side of the model, where you have a slight overhanging angle, in no particular axis :)

I’ll print it in pla once my current print is done :D

I tried to observe it but it just goes straight over it… It seems a bit like a cascading issue, where one layer has a bit missing and then the next one blobs onto the next because it’s trying to print on nothing, idk

It also sometimes catches itself again and you get these patches of weirdness and then it’s okay again

It seems to be more for if you actually want something that makes use of the screen and gamepad input and then you can launch it from the UI.
https://github.com/ValveSoftware/steamlink-sdk

I read it :) I can’t seem to get started on stardew… I planted some stuff and went to bed and then didn’t really feel motivated to do more 🤷

I thought this too, but unfortunately in terms of modding and general use they are very limited, afaik. When I looked into it, it boiled down to: There’s an sdk to develop stuff for it and you can get root access but good luck trying to replace the os or anything like that. That being said, this is what I remember from ~2 years ago, so if it can be customised more now, please let me know. I kinda bought 2 in hopes of being able to do that :D

Hey, not sure how in depth your linux/docker knowledge is. Please disregard if irrelevant. I would recommend you pick a fixed mountpoint for the drive and set up a systemd service to mount the drive for you (systemd .mount file). Then you add an extra line “RequiredBy=docker.service” (look for systemd RequiredBy) This way the drive always has to be mounted by the system before docker is started and should always be visible before you start a container.

Hope this helps :)

Sounds exciting!