• 0 Posts
  • 51 Comments
Joined 1 year ago
cake
Cake day: August 9th, 2023

help-circle
  • Let’s say notifications are like walkie-talkies. You push a button, it sends an alert or your voice to the paired device. Neither one is storing the information, they are just relaying to each other. Now, in this case the government has issued a court order stating that a third party be given a walkie-talkie with the ability to understand the information transmitted by the first. There is still no storage being done, but a second party now receives all the information being broadcast.

    It’s not about not having the information. You don’t actually need to store it anywhere to facilitate communication, at least beyond it being in memory which most would agree doesn’t constitute storage in this situation.

    Now, could that third party store the information? Absolutely.
















  • A loose FEP wouldn’t cause the print to essentially perfectly skip over multiple layers. Once the FEP finally releases, there would be multiple layers missing, resulting in a very gloppy thick layer, or the remaining layers printing directly on the FEP.

    I can’t think of any situation a loose FEP could result in the above image without at the very least one “extremely large” layer.

    Not to mention, the FEP wouldn’t suddenly tighten, meaning you’d have the same issue over and over.


  • Suction cupping causes the print to rip from the build plate/supports, it wouldn’t cause this. Especially since it continues along as if a few layers were cut out of the file, which just isn’t something caused by suction cupping. It would essentially need to be stuck to the FEP to such an extreme degree that the stepper motor is unable to move.


  • Pauses do weird things with 3D printing, though it’s generally better with resin printers, it will still suffer. Higher end models have ways of compensating, but will still see weirdness.

    It’s generally a loss of precision/placement of the bed, and (on some faulty firmware) missed layers from the read.

    This looks like it could be the latter, or potentially even both.

    I’d definitely try again without a pause, and if it goes properly just avoid pausing moving forward. A firmware update wouldn’t be a bad idea either, if available.