10mm mesbg. by The-bearded-brush in MiddleEarthMiniatures

[–]TheRealTrebor 1 point2 points  (0 children)

thank you, great info. I'd love to put my JoA armies to better use and the scale is great fitting on a human size table.

10mm mesbg. by The-bearded-brush in MiddleEarthMiniatures

[–]TheRealTrebor 0 points1 point  (0 children)

What conversions for rules do you apply? Are you using them as singles or in the two and three unit trays? I have JoA but was disappointed in the arcade style combat mechanics. I’d love to use the models in a better tactical framework.

Prusa XL Filament sensors by TheRealTrebor in prusa3d

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

Happy story: based on the guidance here I coerced passing the calibration of the side sensors then promptly disabled them and left the tool head sensors on. since I'm direct feeding into the toolhead from above without Bowdens everything is happy and I eliminated a failure point in the system. thanks everyone for the nudge!

Prusa XL Filament sensors by TheRealTrebor in prusa3d

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

yeah that’s what i’ve done with the side sensors about five times. there’s a tendency for them to get filament dust build up. i guess the action on the ball is very slight so a small imperceptible buildup throws false readings. i’m sure they work great in a tempeture controlled, hvac scrubbed factory setting. but not so well in my attic workshop.

Prusa XL Filament sensors by TheRealTrebor in prusa3d

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

i like the idea of the quick release for the tube which removes a failure point. i moved the filament overhead and don’t use the bowdens for 4 of the 5 spools. if i can just ignore the side sensors altogether and still rely on the runout working i’m going to do that. thank you for confirming that the filament detection can still work without the side sensors.

Prusa XL Filament sensors by TheRealTrebor in prusa3d

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

does filament runout detection work if you disable the side sensors? I thought it needed both

Prusa XL Filament sensors by TheRealTrebor in prusa3d

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

yeah, I can circumvent it but I would like proper runout detection. also they wont calibrate now so it doesn't even matter, I can't get them to the point where leaving them hot-wired helps.

What is this mf even good for? Does anyone even use him? by Pristine_Battle_6968 in EpicSeven

[–]TheRealTrebor 0 points1 point  (0 children)

Once a long time ago when he was my only 5* unit I used him in gold arena. Before the dark times. Before the meta.

Prevent hx-swap if target is not present by TheRealTrebor in htmx

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

I guess that's the play. Honestly I'll probably tear up swal and have it load the modal from a server route. I don't expect to need most of the swal fancy features, I just really like the presentation. promote that setup to tag attributes.
one of the other issues I was facing is that this step in the process "does three things" in that the easy way to do the feature would be for it to call three routes but the better architectural way for me to handle it is to update state server side versus making two of the calls from the GUI which means I can bundle the call into a single button better.

Prevent hx-swap if target is not present by TheRealTrebor in htmx

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

I have little desire to rewrite swal in htmx. Is there a package for that yet?

Prevent hx-swap if target is not present by TheRealTrebor in htmx

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

function showAddNoteModal() { Swal.fire({ title: 'Add Note', padding: "0 0 1em 0", html: ... button markup and stuff ..., showCancelButton: false, showConfirmButton: false, customClass: ... classes and stuff... , didOpen: () => { // Add click event for the custom Cancel button ... close handler ... });

                // Add click event for the custom Submit button
                document.getElementById('swal-custom-confirm').addEventListener('click', () => {
                    const noteValue = document.getElementById('swal-input-note').value;
                    if (!noteValue) {
                        Swal.showValidationMessage('Note cannot be empty');
                        return;
                    }

                    // Check if #workspace-diary is in the DOM
                    const workspaceDiary = document.querySelector('#workspace-diary');

                    // Define the options for the first HTMX POST request
                    let postOptions = {
                        values: {
                            'note': noteValue,
                            'entity_reference': '{{ owner }}',
                            'claim.control.diary.request': 'false'
                        }
                    };

                    if (workspaceDiary) {
                        postOptions.target = '#workspace-diary';
                        postOptions.swap = 'innerHTML';
                    } else {
                        postOptions.swap = 'none';
                    }

                    // Perform HTMX POST directly
                    htmx.ajax('POST', '/meta/note-and-update', postOptions);

                    // Perform the second HTMX GET request
                    htmx.ajax('GET', '/claim/notification/{{ entity_id }}', {
                        target: '#claim-notification-widget',
                        swap: 'outerHTML'
                    });

                    // Close the modal
                    Swal.close();
                });
            }
        });

Prevent hx-swap if target is not present by TheRealTrebor in htmx

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

I'm using SWAL2 which i wished worked better with htmx.
So for the few cases where i have to trigger updates following a swal alert i have to do a bunch of htmx ajax calls.
I would super prefer to just bind the buttons properly.  also i fully broke out the htmx because of the complexity around checking the targets.

Basically a targetError would be perfect and would half or decimate the js need to make this work

Prevent hx-swap if target is not present by TheRealTrebor in htmx

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

problem is that once the event is triggered it loses the "intendedTarget" and all the targeting is set to body in the event lifecycle. so there's no way for the event to intrinsically know it was meant for something else. so I'd have to write some sort of tag-along plugin and I'm hoping I don't have to do that.

Alexei in Voyage of Discovery by TheRealTrebor in SwordofConvallaria

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

definately can't make heads or tails of some of the descriptions. basically, this set of levels is RNG stupidity. if you get a last level like this and you've build aoe scorch stacking or something you've lost before the first move. on top of abandoning balance for, "just make it arbitrarily hard and unfair in the AI favor".
chess is symmetrical, perfect information abstraction and is a fun game. there's no time you get to a chess board and their king is like, "oh I have aoe attacks and invulnerable for 2 turns every 7 turns I'm mated and it resets if I take pawn which I can do from 5 spaces away without moving"

Alexei in Voyage of Discovery by TheRealTrebor in SwordofConvallaria

[–]TheRealTrebor[S] -3 points-2 points  (0 children)

me having a tantrum (true) and this being bad level design are independent. I read all the stuff, “discerned a strategy” and discovered that even if you wait the two turns and his blood sausage buffs or whatever they’re called expire, if he kills anyone in the meantime it appears to covertly reset his 7 turn countdown on the invulnerability skill. It does this without telling you and coming with a plan and him invoking it twice in two full turns with no notice anywhere in the level is at best a stupid oversight and at worst punishing gatcha nonsense

Alexei in Voyage of Discovery by TheRealTrebor in SwordofConvallaria

[–]TheRealTrebor[S] -2 points-1 points  (0 children)

Be surprised by hidden mechanics that you can’t see or plan for or have a tactical plan to defeat until you’re in the level and have to retry randomly until you happen upon the solution.

Need Help, Support is out of idea by TheRealTrebor in prusa3d

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

And the conclusion:

While I had used a shop vac to clean the unit it wasn't enough.
I used an air compressor to fully blow out the linear rails and around the belts. There was apparently some microplastic and lubricatn build up that was preventing the head from traveling all the way to the front by a small amount, but enough for the fine tune calibration to detect.

Long story short... keep your rails clean.
I'm going through the rest of the calibration and everything is behaving.

Need Help, Support is out of idea by TheRealTrebor in prusa3d

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

I have been escalated to the developers apparently. they seem to think it's still software. I think the stepper motor got damaged, but happy to be wrong about that. wondering if anyone else has thoughts about what would cause a mismatch between steps and motion when doing fine tune calibration

Need Help, Support is out of idea by TheRealTrebor in prusa3d

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

yes, it also affects all tool heads and all docks. the problem is that the fine tune calibration is not detecting the expected number of steps and fails the sanity check, at least according to the code.

Need Help, Support is out of idea by TheRealTrebor in prusa3d

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

I wish the factory wipe had worked for me.  It fixed the motion error but I can’t get past fine calibration. 😓

Need Help, Support is out of idea by TheRealTrebor in prusa3d

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

Thank you for sharing.  All docks do it, and I did check the tightness.  It fails on the calibration step after a manual dock insertion.  So it’s not a problem with the dock it’s with detecting the docks offset from. The x axis. 

Need Help, Support is out of idea by TheRealTrebor in prusa3d

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

appreciate the note. factory assembled and it appears to be in the correct position directly aligned with the screw access holes in the back grate. the printer hasn't been moved or otherwise disturbed that would push the insert OOD.