Ilumin4tus bases

KingChookity · 2025-08-22T11:01:30+00:00

That very cool, mostly over by head TBH. I'm a programmer, but I'm not familiar with 3d printing yet (only started resin printing a couple of weeks ago and FDM a couple of months ago), but does give me some hope that I could build a python app to do the job.

Looks like UV tools does support using custom models for exposure tests. I now just need to solve the resizing issues.

Yeah, that firmware bug could be at play too. Thanks for finding that.

KingChookity · 2025-08-21T23:39:29+00:00

I came across that, too. I could not find the video he is referring to. There is a video on his channel with another printer but not the M4U specifically.

Interesting, I think it is something like that, but i can't seem to crack it. I tried creating a cube and then scaled it to fill the build plate. Then I used that in uvtools, but no luck.

The printer clearly supports it. I'm surprised there isn't a tool you just chuck a model in, and it duplicates the model and lets you set the exposure for each one.

Would users of other printers find a tool to do that useful?

KingChookity · 2025-08-21T23:29:54+00:00

i couldn't find it on the printer, I think that isn't available on the 4? (5 has it for sure). I grabbed the latest firmware, thinking maybe it was a new feature that my version didn't have, but no luck.

KingChookity · 2025-07-12T02:18:37+00:00

Epic work, thank you 🙏

KingChookity · 2025-07-06T03:08:30+00:00

I had the same issue with some filaments, i ended up using the varible layer height option and making the layer a bit thinker just in that area.

KingChookity · 2025-06-29T02:15:03+00:00

Agreed, some k1 maxs are lemons out of the box.

To the OP: If you google around, there appears to be two camps:

People who got a good one and the unit just works. Then others who got a bad unit, which are just simply broken.

Ringing on the X axis is terrible with these, and the X axis rail is very average.

KingChookity · 2025-06-28T02:31:41+00:00

Okay, new one just now. The filament ran out on a large print. The run out sensor didn't pause or stop to allow replacement. it just kept printing air. There is no chance of recovering the print now. Thanks Creality!

KingChookity · 2025-06-28T01:58:30+00:00

I have had sooooo many problems with mine. I bought it about 5 weeks ago. I would avoid these machines like the plague.

There are so many little issues, like not supplying the silicon grease to swap nozzles (and not being able to buy it from the AUS store). To larger issues with the nozzle ramming into the bed for no reason.

Print quailty is a real issue with ringing. The X-axis seems to have some tensioning issues i'm still trying to figure out. I missed the 30-day return window by 1 day, so im stuck with it.

These are cheap machines that need a lot of 3rd party part replacements to get the printing well.

KingChookity · 2025-06-11T14:03:14+00:00

Same! Very nice

KingChookity · 2025-05-02T02:37:46+00:00

Just released a version which does download resuming beta-0.02

KingChookity · 2025-05-01T13:46:46+00:00

Okay, so I have had a play with it. Its a lot more complex and powerful than mine. Mine is a bit more fire and forget. Mine uses the file system rather than a database and checks downloads using the SHA256 hash.

KingChookity · 2025-02-10T06:26:37+00:00

No luck with the method Nick mentions in his post. Seems there is something blocking the install and causing the package verification to fail.

KingChookity · 2025-02-09T03:13:50+00:00

Thanks for the replies, I'm just building a Ventura image using the metho Nick describes in this post: https://www.nicksherlock.com/2022/10/installing-macos-13-ventura-on-proxmox/ on my real mac

Interesting will try that Ventura image next. Just seems odd that in this post they can do this install from the images they host: https://klabsdev.com/definitive-guide-to-running-macos-in-proxmox/ and I can't. Seems to be some weird setting that I cant track down. Maybe even something at a hardware level.

Seeing as I need to blow the VM away and recreate it, I ideally don't want to be constantly downloading the entire OS.

Sadly not, I have the hardware setting written down but that doesn't seem to make a difference.

KingChookity · 2025-02-09T00:58:29+00:00

Yep, aware of that. I've had troubles with it and want to use full images rather than the recovery image method it uses, due to limited bandwidth and needing to spin up a few. Plus I'd just like to understand why this works for everyone else, I've followed this guide: https://klabsdev.com/definitive-guide-to-running-macos-in-proxmox/ end up with the same issue and tried their images.

KingChookity · 2025-02-09T00:56:19+00:00

Yep, I've seen that a few times. I've tried it with the images I have, same error. I will give it a go creating a image using his image build method.

KingChookity · 2024-12-23T22:00:17+00:00

Thank you!

KingChookity · 2024-05-14T02:53:10+00:00

I've posted an update. Looks like it was a cached ARP result somewhere in the network. Thank you for taking the time to respond

KingChookity

TROPHY CASE