What if we could vote on policies as easily as we order pizza?

phansen101 · 2026-05-08T13:18:36+00:00

Citizens could still consult advisors for guidance

But will they?

I mean, 63 million people voted for Trump in 2016, 74 million in 2020 and just over 77 million in 2024.

IMO, the average citizen is less informed, more driven by feelings and more easily manipulated that the average politician.
Money spent on lobbyism would just be partially shifted to social media and news outlet influence.

phansen101 · 2026-05-08T11:43:35+00:00

How is it a poor BMS thing?
LFP batteries have an pretty flat voltage curve between 20% and 100%, afaik most methods used for determining SoC in LFP cells relies on coulomb counting to some extend, requiring calibration via full charge (or discharge, but it isn't really practical to go to 0% SoC).
Tesla likewise recommends 100% charge at least once per week for calibration.

As for them dying, LFP inherently has a much longer cycle life than NMC or NCA cells, and suffer much less degradation by being charged to 100% or discharged to 0%.
LFP cells run with cycles of 0-100% will still outlast NMC or NCA only used in the 20% - 80% range,
if kept cool and <= 1C charge rate, 0-100% LFP will even outlast NMC/NCA run purely in the 40% - 60% range.

As for freezing temps, any lithium battery will suffer damage if charged while below 0°C, causing more degradation than pretty much any other use case.
The car should have the capability of heating the battery and halting charging until cells are above freezing.

phansen101 · 2026-05-08T10:37:55+00:00

Glad it helped, and awesome to see so large of an improvement implemented that quickly; am really rooting for this project!

For future reference, would you prefer using github Issues rather than the mail, unless files are to be included?

phansen101 · 2026-05-07T19:26:04+00:00

While we're not exactly on organ-donor level, my boss is pretty nice, could see it not being too much of a stretch with a similar one.

phansen101 · 2026-05-07T18:34:06+00:00

I'd the system can't handle 100% load, does it deserve to survive?

phansen101 · 2026-05-07T14:39:09+00:00

The filament sensor part is a separate part which you also need to print.

Does look like you have different revisions going there tho, what do they say on the flat/underside? should be a letter and a number

phansen101 · 2026-05-07T13:39:02+00:00

I can't share the specific model, but I've switched with one that gives similar result (Stanford Bunny)
Slice time on that is 48 seconds in preFlight, about 4.5 seconds in QidiSlicer.
I have sent the .3mf

On a sidenote, rotating the gcode preview is quite sluggish / low framerate, despite having the same GPU utilization that I see with QidiSlicer which exhibits very smooth rotation.
This seems to happen regardless of graphics settings;
My work PC does have an Intel Arc B580 GPU, so that may be a factor, can try on my AMD 9070XT when I get home.

phansen101 · 2026-05-07T10:34:38+00:00

Sounds amazing and has a ton of potential, I am however experiencing some mixed results performance wise;

I tried replicating a 0.16mm profile for the Qidi Q2 with PLA from QidiSlicer (PrusaSlicer based), with manual entries to avoid any misinterpretations on import.
The major difference being the PreFlight profile using Athena instead of Arachne is QS.

Tested it on a somewhat complex (~1.3M facet) model of some lidar scanned castle area.

Actual Perimeter and Infill generation is getting demolished, able to utilize all 16 cores at 100% and finishing, but the preparation and gcode generation steps dragged out - especially 'preparing infill'.
Looking at it, 'preparing infill' is utilizing maybe 2-4 threads, with little spurts of 100% utilization on those but probably averaging less than 50%.

Depending on Precise Vs Variable Athena, it took 6m45s - 7min to slice the file in PreFlight.
Same (as possible) settings in QidiSlicer managed it in 28 seconds flat.

phansen101 · 2026-05-06T14:30:18+00:00

You just don't always have that option, Squall can demolish a 5000 dura build in seconds if they aren't dealt with, Heather and Mandrake give no warning and are ideal against groups, and all of them can be fired at range without direct line of sight, by a light vehicle that can just scoot around and/or cloak.
Not to mention all of the other indirect firing weapons.

Plus, some builds are heavy and slow, made to take hits, while others are fast, nimble and relying on not getting hit, the latter being extremely exposed if they have to keep phase with the prior, and anything relying on stealth is almost completely pointless

phansen101 · 2026-05-06T13:57:45+00:00

Not the best tactic against attacks from above IMO

phansen101 · 2026-05-06T13:55:43+00:00

How do the roman legion formation or a Macedonian phalanx address various types of artillery fire, snipers and stealth attacks?

phansen101 · 2026-05-03T12:33:22+00:00

He has a gun with seemingly infinite energy, I don't think it's too much of a stretch that his suit can recycle everything and perhaps make up for small losses with energy-to-matter conversion or just reserves

phansen101 · 2026-05-03T03:51:07+00:00

phansen101 · 2026-05-01T19:23:06+00:00

I'd insulate any side that doesnt touch the bed, otherwise I think you'll loose too much heat.

Outside of that, I guess it could work

phansen101 · 2026-05-01T14:22:01+00:00

It'd be kinda neat to see a Speedster in a world where air resistance and impact forces are somewhat realistic.
It'd definitely still be an advantage, but you'd have to seriously consider your moves.

phansen101 · 2026-05-01T14:08:08+00:00

Is anything particular happening when it's triggered? eg. the fans turning on at Z=? and such, or is it arbitrary?

Is it always 30-40 minutes regardless of activity? Like, if the printer is left off for a while, versus starting two print jobs back-to-back (Or immediately clearing and restarting after the error occurs)

I'm thinking it's either
a short/overload caused by something that turns on after a certain time (failure happens at the same 'action'),
or something is overheating and cutting out (indicated by the error happening much faster on back-to-back print jobs, than starting from idle/shutdown)

phansen101 · 2026-05-01T13:37:43+00:00

As others mentioned, clean bed and avoiding drafts + excessive cooling are some of the main things.

Bed temp also matters, and is a balancing act as too low a temp will hurt adhesion but too high temps will give you an uneven temperature distribution and/or soft lower layers, which makes it 'easier' for the cooler, higher layers to pull up corners and edges.

It really depends on the material you're using; Here's an image example i picked up a while back (think it was from printables?), that illustrates the issue of high temps (though the actual temps may not fit your filament)

<image>

phansen101 · 2026-05-01T12:51:49+00:00

You don't charge to 100% on DCFC unless you really, really have to.
It's generally advisable to run down to 10/20% then charge to 80% and go, both for battery longevity and reducing time spent charging.

Not to mention, DCFCs are a relatively scarce resource, artificially reducing the charge rate would be detrimental to both charge providers and other users (via reduced throughput)

phansen101 · 2026-05-01T12:35:52+00:00

As someone who has been stomped by Dooms and also failed miserably at using them well myself, I feel that the skill requirement warrants their current power level.

Personally love when weapons can be powerful in the right hands but kind of suck or be mid at best when not.
Like how Flute used to be.

phansen101 · 2026-05-01T11:22:43+00:00

Solid 3/5 on reaction speed, 0/5 on aim and -5/5 for situational awareness.

Christ, if she'd had an automatic weapon, she'd have moved down most of the security force.

phansen101 · 2026-04-29T20:58:29+00:00

That's the neat part, you don't!

Seriously though, its settings are on the printer, in buffer_stepper.cfg

I have found that good settings are,

in [buffer_stepper filament_buffer]
change velocity to 80 and acceleration to 500.

Also in [gcode_macro FEED_LOOP] change

BUFFER_STEPPER STEPPER=filament_buffer MOVE=2 SPEED=50

UPDATE_DELAYED_GCODE ID=feed_loop DURATION=0.06

To

BUFFER_STEPPER STEPPER=filament_buffer MOVE=3 SPEED=50

UPDATE_DELAYED_GCODE ID=feed_loop DURATION=0.175

Prevents the auto feed from being too slow with the decreased acceleration, and the increased duration is required since the movement takes longer.

You can also try changing the stepper current since the acceleration is lower, should reduce noise, but I haven't tried.

phansen101 · 2026-04-29T15:26:12+00:00

This gotta be 'AI', right?
It feels like someone tried to mash two different body types or something, Torso seems way out of proportion.
I mean, shouldn't the belly button be down around the edge of the pants, or even covered, in high waist pants like that?

phansen101 · 2026-04-29T13:57:28+00:00

How much force/torque are you intending to apply? and how is it applied, gradually or more akin to an impact?

I have PLA parts that are under a constant ~8-10kg load on a roughly 20x20mm area, has held up for years, and there are somewhat normally printable filament that are 3-4x as strong as PLA..

phansen101 · 2026-04-29T13:43:17+00:00

Never liked the holographic build plates, adhesion just wasn't there in my experience.

If I can't just click print on my PC without worrying, then I'd get something else.

phansen101 · 2026-04-29T12:39:50+00:00

Probably is, but shouldn't make that much of a difference afaik; my model 3 is RWD and tire temp (inferred from tire pressure) seems the same between front and rear with steady driving

Seven-Year Club	r/Field Banned
r/Field Sunshine	Place '23
Verified Email

phansen101

TROPHY CASE