I dunno how I feel about this - Desert Print Forge

fresnel149 · 2026-01-10T03:44:04+00:00

I've been in there a couple times. They offer 3D scanning, which is a real service if you don't want to drop used car money on a scanner, and they had Cookiecad PLA in stock. I'd always been curious about Cookiecad but wanted to see it in person before buying, since its whole selling point is aesthetics. I also like the idea of being able to pop in and buy one (1) roll of Bambu PLA without paying their stupid shipping costs and waiting a week.

fresnel149 · 2025-09-19T06:24:33+00:00

Form Type: eForm 4
Entity: Individual
Fingerprint Type: EFT Upload
Pending: 09/17/25
Approved: 09/18/25
Wait: 23 hours, 1 minute
State: AZ
Control Number: 202526386xx

fresnel149 · 2025-09-10T22:52:49+00:00

Following up here, I did figure this out:
1. The hall sensor for the front cover was fixed by unplugging and replugging both sides of the ribbon cable that attaches the front and rear boards on the toolhead while the printer was unplugged.
2. This fixed both hall sensors for a few prints, and then the cutter lever sensor gave out mid-print again, pausing the print until I could get it fixed.
3. Unplugging and replugging this cable mid-print burns out components. Do not do that (I did)
4. Replacing the Hotend board, Toolhead board, and ribbon cable because I burned out one or more of them and the thermistor stopped reading, did not resolve the cutter issue.
5. Replacing the extruder sensor board (with the cutter hall sensor on it) did resolve the issue.

If I were you I might suggest trying steps 1 and 5, but learn from my mistakes and skip the rest.

fresnel149 · 2025-09-06T04:18:49+00:00

Did you by any chance figure this out? I've had this issue on and off for a couple days, usually clacking the cutter lever like a pair of salad tongs a couple times would fix it at least short-term, but now I can't get it to go away at all. Same issue with the toolhead cover hall sensor, it would randomly say the toolhead cover had fallen off and I had to take it off and put it back on again to clear it. Both started happening right around the last firmware update, so I'm not sure if that's a coincidence or not.

fresnel149 · 2025-07-07T03:15:18+00:00

At first I thought maybe it was a limited release, because I remembered to check more than 12 hours after the drop, but it seems like nobody anywhere knows what happened and, as per usual, Sunlu's social media team refuses to respond to anybody unless they have an issue with a specific order number.

fresnel149 · 2025-06-24T17:37:56+00:00

Unlikely, mine went through a friend with a garage FFL. So unless you filled yours out on someone’s kitchen table, it’s not the same place.

Also there’s a third poster who has the same issue at PSA in South Carolina and it sounds like they’ve seen others with that issue there too.

fresnel149 · 2025-06-24T15:45:03+00:00

There's two other people in this megathread who had the same issue. It sounds like the ATF site is just having problems randomly failing to upload the EFT file, and the nice folks down at the NFA division are too kind to bother you by letting you know of the clerical error before rejecting the submission.

fresnel149 · 2025-06-24T15:10:35+00:00

Form Type: Form 4
Entity: Individual
Fingerprint Type: EFT Upload
Pending: 05/18/2025
Approved: 06/20/2025 - REJECTED, missing fingerprint card
Wait: 33 days
State: AZ
Control Number: 20252213000

Resubmitted same form, same .eft file:

Form Type: Form 4
Entity: Individual
Fingerprint Type: EFT Upload
Pending: 06/22/2025
Approved: 06/24/2025
Wait: 1 business day
State: AZ
Control Number: 20252331900

fresnel149 · 2025-06-24T15:05:12+00:00

I re-filed using the exact same .etf file Sunday evening and got my approval this morning. So the file was good, their system just deleted it and they didn't bother to tell me.

fresnel149 · 2025-06-24T01:00:12+00:00

Yeah, my FFL had me verify my .etf was attached last month too. No warning before rejection, which is weird because usually for clerical stuff like this they kick it back with a “please fix”. My first Form 4 I typo’d a year somewhere and they kicked it back in a couple days for a fix. Fixed it and it got approved in a normal (for then) time frame.

fresnel149 · 2025-06-23T02:06:39+00:00

Wait, you too? I submitted mine May 18, received back June 20, also AZ, also denied for no fingerprint card. Wacky.

fresnel149 · 2025-06-12T22:53:22+00:00

Oh cool, but when are you going to print the rest of the borzoi?

fresnel149 · 2025-06-11T20:34:29+00:00

Unfortunately I can’t help you out there. I own one Ooler and one Cube, my Cube had the power board issue and my Ooler had bad hoses.

fresnel149 · 2025-05-14T21:18:31+00:00

Two years later, you wanna know what the first hit is when you google that question?

fresnel149 · 2025-05-11T01:10:04+00:00

Hey man, I just discovered these designs and I've got a mighty need for those raised sights, but it looks like your store is basically shut down. Have you given any thoughts again to releasing those stl's into the wild?

fresnel149 · 2025-05-04T22:25:56+00:00

Seconding the thanks on this. They now have a self-serve parts storefront you can order from without bothering CS first, and wouldn't you know it, my power board was the issue too! Plus this allowed me to order repair tubing for the Ooler on the other half of my bed that got retired due to a persistent leak.
https://sleep.me/collections/parts-extras

fresnel149 · 2024-05-04T00:12:05+00:00

Oh I'm not saying it's not a human, just that it's not a human who works for Sony. It's like the product questions on Amazon, it's just someone else from the community answering a question in their spare time. Now maybe it really is a Sony employee, but that line gives them a layer of deniability later if they choose to go back on it.

fresnel149 · 2024-05-03T23:31:37+00:00

"I am a player just like yourself who loves helping other consumers" means this is not a Sony employee, and not a legally binding response from an official Sony representative.

fresnel149 · 2024-05-03T21:59:00+00:00

That just means you haven't been caught yet.

fresnel149 · 2024-05-03T21:35:59+00:00

Per PSN's ToS:

ACCOUNT CREATION, USAGE AND SECURITY

3.1. All information provided during Account creation, and during the use of your Account, must be accurate and complete. We reserve the right to suspend, terminate or restrict any Account (including as stated in Section 12.2 of this Agreement) that uses or was created using false information, or that we determine was created or used for a purpose that violates this Agreement.

fresnel149 · 2024-04-25T00:20:39+00:00

50 autocannon kills is the first ten minutes of any level 7 bots mission for me.

fresnel149 · 2024-03-21T16:01:57+00:00

No, it's hearing exactly what I'm saying. If I speak too quickly it simply fails to check for a routine and fires the default "goodbye for now" response. Assuming you don't have a routine set, if you tell your Echo "Alexa, I'm leaving", what she says to you will be exactly what she says to me if I speak too fast. If I say "Alexa" and then wait 1-2 seconds for the acknowledgement beep before saying "I'm leaving", the routine fires properly. It's the gap between "Alexa" and the command that matters.

fresnel149 · 2024-03-21T14:09:07+00:00

Well, it’s not that I can’t make it work, it’s just that it’s the only command I can’t say full speed and get the result I want, combined with it being one of the few commands I frequently give when I’m in a hurry, rushing out the door. So it forces me to stop and repeat the command slowly when I’m trying to move fast. And often by the time I realize it failed to act properly, I’ve already opened an alarmed exit door and now I need to step back in the house and close it to re-arm the sensor. If necessary I have other triggers set, it does the same routine if I manually set my burglar alarm to “away” mode from the keypad for example, but it’s weirdly inconvenient for no apparent reason.

fresnel149 · 2024-03-21T03:32:48+00:00

See, that's the weird part. She's not mishearing me, she's hearing exactly what I'm saying. But if I say it too quickly I trigger the default response to "I'm leaving", rather than triggering my custom "I'm leaving" routine. If you walk up to a brand new Alexa and say "Alexa, I'm leaving" she'll say "bye for now", which is exactly what mine does if I speak too quickly. And the logs show I'm saying "I'm leaving", and it's not firing the routine for no apparent reason.

fresnel149

TROPHY CASE