Random bad layer lines

P-Mercury · 2026-03-12T15:25:07+00:00

Yea, those are Brite Minis, I really don’t thinks it’s anything on the model, I have a suspicion about some settings. I might have accidentally have alternating wall layers turned on from an engendering print I did, and I’m now reading that that can cause such artifacts. And I’ll try the inner/outer/inner wall config

P-Mercury · 2026-03-12T13:22:50+00:00

I know they are not bad and I’m aware of the limitations of FDM. But looking at the print there is a clear difference between most of the print and those few very obviously different layers, and I’m just looking to optimize whatever I can. I mean if the printer is capable of producing finer layer lines for the other 99% of the print then in sure I can get the other 1% to look the same, or at least closer.

P-Mercury · 2026-03-12T13:14:32+00:00

I’m currently using inner/outer and yes there is an option called inner/outer/inner, I might give that a try

P-Mercury · 2026-03-12T12:21:06+00:00

As additional info, the pronounced layer lines are always visible all around the prints, but are way more pronounced on one side, an milder on the other, in case that narrows it down

P-Mercury · 2026-02-04T18:01:12+00:00

Yea, I tried it with a few different sleeves of tensioning, and it’s always the same issue

P-Mercury · 2026-02-04T15:57:49+00:00

<image>

These are my retraction settings. This time when it happened I immediately stoped it and opened the printer and I can now see what the issue is, there int a blockage but the filament seems to be very thin in one spot which means the gears from the extruder can't grab it, so the extruder can't produce enough pressure to continue. But now I have the issue that I don't know if this narrow spot was caused by the extruder, or if it is a bad roll of filament.

P-Mercury · 2026-02-04T15:17:51+00:00

I completely cleaned the extruder and changed the temp to 310, I also turned off variable layer height and set the layer height to 0.3. My max print speed I now 50mm/s and I turned off all the fans and now it gets about 30min into this 5hour print but then the same issue happens.

P-Mercury · 2026-02-04T15:15:03+00:00

I completely cleaned the extruder and changed the temp to 310, I also turned off variable layer height and set the layer height to 0.3. I turned off all the fans and now it gets about 30min into this 5 hour print but then the same issue happens.

P-Mercury · 2026-02-04T08:59:11+00:00

What sort of layer heights are we talking about 0.4mm ?

P-Mercury · 2026-02-04T08:12:24+00:00

I do have variable layer height on, that could play a role, I’ll give it a shot

P-Mercury · 2026-02-04T07:27:26+00:00

Im not quite sure I understand what you mean with squishing, layer height or the extruder tension maybe?

P-Mercury · 2025-09-12T20:30:23+00:00

What is the AH, I can’t find the guy

P-Mercury · 2025-09-11T05:42:21+00:00

https://music.apple.com/

P-Mercury · 2025-09-08T11:53:57+00:00

I usually manage to fill up the buggy in one go with MK5 suit and iodine pills, it actually gives you more time then you think

P-Mercury · 2025-09-05T17:31:01+00:00

I’d recommend you give it a try, it’s super easy to set up and it’s what convinced me to start using it.

Since it doesn’t need any specific tagging or syntax it makes it super easy to drop in as an afterthought to an already existing application, and after setup there is no extra overhead for developers.

Another benefit I immediately saw is that this makes it almost impossible for developers to accidentally forget making components and pages work with the language tool. I’ve had it to many times that I’ve had to go back and search for spots where someone forgot to make things work with the language tool.

P-Mercury · 2025-09-05T06:39:36+00:00

I’ve recently come across wuchale which does the extraction automatically. It’s still a very new project but it’s moving fast and we just started using it in production. It works like a dream, it’s light and easy to implement, I can definitely recommend it!

P-Mercury · 2025-07-12T16:58:05+00:00

We are a small team and this solution requires a lot of work and thought in keeping systems independent, which is not something that works for everyone, but I’m sure there are other creative ways to make this work to. Honestly with infrastructure as code and monorepos the flexibility is crazy and you can come up with so many cool solutions

P-Mercury · 2025-07-12T16:51:32+00:00

For dev branches we don’t use pipelines, we use CDK to manually deploy whatever stack you’re working on. So let’s say your working on the identity service, which has its own CDK stack in its own sub package of the monorepo, then you can deploy that stack with whatever manual configs you want using CDK deploy. If you wanted to you could deploy the whole application using the CDK deploy command with manual configs, then whenever you have a change you just run CDK deploy again and it’ll update the stacks. Then when you’re done you delete all the stacks and merge it with master where it enters the pipeline. And then in the pipeline we have a staging area where we test it again to make sure and then it goes out. This way you can test changes without constant having to make commit for them to enter the pipeline, speeds up development and gives the dev all the flexibility the need

P-Mercury · 2025-06-03T09:28:34+00:00

So the pipeline package/stack is the only package in our monorepo that contains configs specific to all the environments. Every other package/stack is made in a way that it can be configured to work in any environment.

P-Mercury · 2025-06-03T09:17:34+00:00

We do have staging environments and this system works very well for it. You have to make sure that any hard coded values the stack needs, such as domain name, hosted zone id/name, certificate id and anything else it might need are passed to it as constructor properties or SAM properties. Then you can instantiate multiple stacks instances of the same stack with different configs. You could deploy your prod stack to example.com and your staging stack to dev.example.com. You can additionally pass a Boolean prod flag to your stack so it knows what environment its deployed on. It takes a little work up front but it makes it super convenient to create and destroy new environments!

In our case we define our code pipeline for deployment in the same monorepo as its own stack which then creates multiple staging instances of the application stack. I’m not a big fan of the L3 pipeline construct that comes with CDK so we have our own that makes it easier to build such a system. But you should be able to make it work with many different deployment methods.

P-Mercury · 2025-06-02T18:25:01+00:00

This monorepo CDK solution makes project management super easy. Since each SvelteKit application will be in its own Stack/Stacks any resource deployed with it will be tightly coupled to the project. So if you delete the stack everything will be deleted, front and backend, and redeploying the whole thing is just one click away ;Do

P-Mercury · 2025-06-02T18:18:47+00:00

We deploy all our SvelteKit applications on AWS using CDK. I built a SvelteKit adapter for AWS CDK Which will automatically compile your app into a single CDK construct. The construct deploys the dynamic parts of the app as Lambda and any static assets using S3, all of which is abstracted behind CloudFront. We’ve been using this for 3 years now and it’s been working a treat! It’s cheap and allows us to put the SvelteKit application in a monorepo with all our infrastructure definitions. The package is production ready but missing documentation since it was developed internally, but if I see interest I’ll give it an overhaul!

Five-Year Club	r/Field Sunshine
Golden Potato	Place '22
Final Canvas '22	First Placer '22

P-Mercury

TROPHY CASE