Sure, you can print minis with an FFF machine. But there’s a reason the mini printing folks primarily use SLA. For that particular application, it’s significantly better. I say this as someone who uses an Ender 3 and is quite happy with it. If my main goal was printing minis, I would probably want an SLA machine instead.
If your goal is to make mini figures, what you want is an SLA machine. They are much better at making small detailed objects than FFF. However, it will definitely cost more than a cheap FFF machine like an Ender 3.
The Ender 3 variants are cheap and a great platform if you are OK with tuning/tweaking things. If set up properly they work great and are pretty reliable. But of you want something that works out of the box and doesn’t need any tweaking/tuning, you will probably be disappointed with it.
Nvidia drivers have had way more issues with mobile chips than with desktop. GPU compute workloads (including things like Blender) are very well supported. Nvidia on Linux has dominated the compute market for a long time.
The TPM releases the key to the OS at boot time. Without that, there would be no way for the OS to load (assuming the root FS is encrypted).
The key is bound to PCRs in the TPM, which control under what conditions the key can be released. For example, it can be tied to secure boot, bios settings, etc.
In addition to what others have said, make sure the vents are not full of dust or obstructed.
Aside from the group suggestions, you could also use ACLs. https://wiki.archlinux.org/title/Access_Control_Lists
Arch Wiki for more general info. Official docs/man pages of whatever thing you are working with for details.
Removing orphaned dependencies every once in a while is a good idea. If these were installed as dependencies and are not dependencies anymore, this would get rid of them.
https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#Removing_unused_packages_(orphans)
You need to install the CUDA package to use Nvidia GPUs in blender. This is in the arch wiki page for blender.
I think they already have. I held off on Wayland on my main machine for a long time due to Nvidia issues. For example, I was getting rendering issues where some windows/popups would be totally invisible until I moused over them. Those issues are now gone, and I’ve been running Wayland for the last few months with no problems at all.
Adding a wireframe modifier is pretty simple - I’m sure you’ll do fine with that.
If you want to get into modeling in blender, I highly recommend the donut tutorial series by blenderguru. It’s on YouTube.
The system will be secure for personal use as before.
I wouldn’t be so sure of that. CPU side channels allow data to be leaked across security contexts. For example, from a user process to sandboxed JavaScript in a browser, from kernel space to user space, or from one containerized process to another. This is a problem even on a single user system without any VMs.
https://docs.blender.org/manual/en/latest/modeling/modifiers/generate/wireframe.html
Alternatively, if you just want a render of it and not a 3D print, then there are also various ways to do it with shaders and renderer settings.
Some Chromebooks are pretty hackable. I’ve got an older one that I reflashed with tianocore UEFI firmware. It makes for a pretty decent cheap and lightweight low power laptop. You can run basically any standard ARM Linux distro on it.
Thanks - I didn’t realize that crtouch is optical.
Looks like it’s got a jam. Did you reduce retractions with the direct hotend? If not, you are probably retracting way too far, which will cause filament to solidify in the cold area and jam up.
The architecture is a bit different than octoprint. Fluidd and mainsail are purely client side UI’s, while Moonraker provides the server side API for them to connect to. So any additional functionality would need to integrate with Moonraker - not Fluidd/Mainsail.
A lot of functionality that is plugin based in octoprint is core to Moonraker and fluidd/mainsail. Things like cameras, mesh bed tools, gcode viewer, UI layout customization, power device control, etc are all included.
Spool manager is not something I’ve personally needed or used, but this would probably be a good option: https://github.com/Donkie/Spoolman
I highly recommend switching to fluidd or mainsail. They don’t require any more CPU power than octoprint (possibly a bit less, actually). They are more modern and polished interfaces than octoprint.
CR touch and BL touch are the same. It’s just creality’s name for it.
Inductive probes are probably the cheapest option. I paid around $5 for mine and it works great.
FreeCAD definitely has a steeper learning curve and a few rough edges, but to me it was absolutely worth it to learn. I really don’t like my files subject to the whims of Autodesk.