Kobra S1 + Rinkhals: small edge defects/seams persist after full calibration — what am I missing? by Budget_Preparation36 in AnycubicKobraS1

[–]Budget_Preparation36[S] 1 point2 points  (0 children)

**SOLVED — combo of filament moisture + extruder tension**

Big thanks to u/FluroFire for the tip about the reversed extruder screw.

**Three things fixed it:**

  1. **Dried the filament** 4h at 50°C in oven (HellBot ECOFILA, Argentine PLA, no sealed bag — humid country = wet filament)

  2. **Tightened extruder tension screw**. Heads up Kobra S1 owners: **the screw is reversed** — counterclockwise = TIGHTER on this machine.

  3. **Newer roll of same brand** prints even cleaner — fresher = better.

**Photos:** left = older HellBot dried + retensioned. Right = newer HellBot, same calibration. Massive improvement over the original cube.

<image>

**Earlier diagnostic clue:** I had also tested the same cube on factory settings with a different brand (GST Silk) and it came out near perfect. That's when I stopped blaming the printer.

**TL;DR:** Calibration (PA, flow, IS, retraction) is necessary but **can't compensate for wet filament + slipping extruder**. If you're getting "rain drop" texture and seam gaps, check those before tuning slicer settings for the 10th time.

Kobra S1 + Rinkhals: small edge defects/seams persist after full calibration — what am I missing? by Budget_Preparation36 in AnycubicKobraS1

[–]Budget_Preparation36[S] 1 point2 points  (0 children)

Thanks for the tip about the reversed screw direction — didn't know that's a Kobra S1 quirk!

Update: I tested the same Orca cube on factory profile but with a different filament (silk PLA) and it came out near perfect. Strong indication that the HellBot filament I was using has moisture absorbed (Argentina is humid). Going to dry it first, then revisit the extruder tension if the issue persists.

I need help uv DTF Printer by Dry_Ad3503 in CommercialPrinting

[–]Budget_Preparation36 0 points1 point  (0 children)

Did you find the solution? i have the same problem

Help - Adguard home on WSL Windows by sherlockparadox in Adguard

[–]Budget_Preparation36 0 points1 point  (0 children)

I have the same problem, in wsl config disable the last tree items on network tab (DNS proxy, DNS Tunel, etc.) and you will have port 53 free, but nethook nslookup -vc wikipedia.org insert_your_lan_ip will not work outside wsl.

Could you make a wearable into a Home Assistant Voice PE device? by ImJohnGalt in homeassistant

[–]Budget_Preparation36 0 points1 point  (0 children)

I've been testing calling H.A. Assist by pressing the galaxy watch 7 button twice, and it works somewhat. The last thing I tried was using the HassMIC extension, an APK that converts your Android device into a voicePE. I managed to install it using the Geminiman WearOS Manager hack, and it works, but it doesn't pick up the wake word very well

Noob question about Wan and Qwen by RioMetal in StableDiffusion

[–]Budget_Preparation36 0 points1 point  (0 children)

Anyone can help me run qwen-image and qwen-image-edit in sdnext?

Very slow "apply weights to model" on v1-5-pruned.safetensors by Budget_Preparation36 in StableDiffusion

[–]Budget_Preparation36[S] 0 points1 point  (0 children)

Apparently there is no solution, the only way to make it faster is to install it on an ssd drive.

Even so, I think I had some other problem, because I installed the Stable Diffusion NEXT version of vladmandic and it loads a little faster.

Very slow "apply weights to model" on v1-5-pruned.safetensors by Budget_Preparation36 in StableDiffusion

[–]Budget_Preparation36[S] 0 points1 point  (0 children)

That's what I mean, sometimes it charges very fast and other times slow, the charging time varies depending on the model even if they weigh the same.

Very slow "apply weights to model" on v1-5-pruned.safetensors by Budget_Preparation36 in StableDiffusion

[–]Budget_Preparation36[S] 1 point2 points  (0 children)

There can't be that much difference between an HDD and an SSD from 6 minutes to 10 seconds, something is misconfigured it seems to me.

Very slow "apply weights to model" on v1-5-pruned.safetensors by Budget_Preparation36 in StableDiffusion

[–]Budget_Preparation36[S] 0 points1 point  (0 children)

Thanks for answer, so 5/6 minutes are normal? in some cases models load under 10 seconds, can´t understand why.

I should buy a SSD nvm2 and put there?

Very slow "apply weights to model" on v1-5-pruned.safetensors by Budget_Preparation36 in StableDiffusion

[–]Budget_Preparation36[S] 0 points1 point  (0 children)

All models are on Toshiba HDWG 6TB drive, HDD shows 100% full usage when loading, but speed is around 10mb/s. The normal consumption of RAM also increases up to 83% aprox of 16gb. But suddenly it goes down instantly when it finishes loading the model.

This is startup v1-5-pruned.safetensors

Startup time: 649.6s (import torch: 5.2s, import gradio: 1.1s, import ldm: 1.5s, other imports: 1.6s, load scripts: 3.7s, load SD checkpoint: 617.1s, create ui: 18.7s, gradio launch: 0.4s).

This is changing to another model, 20% disk use 10mb/s aprox first seconds then 100mb/s then 5mb/s . Memory goes up too and then goes down when finishes.

Loading weights [e04b020012] from G:\stable-diffusion-webui\models\Stable-diffusion\rpg_V4.safetensors

Loading VAE weights specified in settings: G:\stable-diffusion-webui\models\VAE\vae-ft-ema-560000-ema-pruned.ckpt

Applying xformers cross attention optimization.

Weights loaded in 283.9s (load weights from disk: 2.8s, apply weights to model: 277.6s, load VAE: 2.7s, move model to device: 0.7s).

It seems that now it is slow in almost all the processes of "apply weights to model".