• 1 Post
  • 48 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle

  • In addition to “format shifting,” which is a well-recognized use case, and game preservation, which is a huge and under-recognized public interest in emulator development, emulators are also used for the development of homebrew software. E.g., there’s a port of Moonlight for the Switch, which lets you play Steam games streamed from a PC using your Switch, letting it serve many of the purposes of a Steam Deck. That’s huge! It would be way less practical to develop this kind of software if you could only test on real hardware. Testing on real hardware is also essential, of course, but testing on an emulator is vastly faster for rapid iteration.



  • Doesn’t the “missed step detection” on the Prusa printers already achieve a lot of that? I think it monitors the current to the motor and flags any abnormal behavior, without needing extra hardware on the motor.

    That’s not to knock the value of positional feedback, which is clearly superior, but just to say that I don’t think this idea has been entirely neglected.


  • I had a similar issue on my Pixel 6, where I’m using Nova launcher. (I know they changed hands and are not great now, but it’s still more usable than the Pixel Launcher.) There the solution was to go into the Apps settings, find Pixel Launcher, and choose force stop, then clear cache, then clear settings. Apparently there was some bug in Android 14 causing both launchers to try to intercept the “recent apps” press, and it caused it to hang like that.

    Obviously that’s not going to be exactly the same issue on your phone, since presumably Pixel Launcher isn’t on there, but maybe doing the “force stop, clear cache, clear storage” on the default launcher on your phone would help?



  • You know that the other two words also exist though, right? Like, you can effect change in an organization, and there can be something strange in the affect of a psychopath. So there’s a verb “to effect” and a noun “affect” (although here the pronunciation is different–the accent is on the first syllable). It’s true that the most common usages follow the rules you’re laying out, but it genuinely is an oversimplification.






  • I dunno, I prefer swipe typing and this doesn’t seem like it would work with that.

    To me the biggest barriers to long-form typing on the phone are that so many websites screw up form handling for long-form content, and that the cursor maneuvering is still pretty broken.

    Websites do weird things when you’re typing. Sometimes the input field won’t scroll, so you can’t see what you’re typing. Other times it’ll force-scroll to put the current line you’re working on at the very top of the screen, so you can’t see anything you wrote previously. At least they finally fixed the weird behavior where if you deleted more than a few characters it would start jumping around in the text and duplicating huge sections of it–I think it was around Android 9 that they finally fixed that.

    As for moving the cursor, the “swipe on the space bar to move the cursor left and right” works, but trying to go back further, like going up a few lines, is very, very difficult. The cursor will scroll the text box if you move to the edge, but there’s no delay in the scrolling, so instead of scrolling a couple of lines and then pausing briefly to give you a chance to stop there, it just immediately scrolls again on the next frame of rendering, so effectively your choices are “scroll within the few lines of text still visible” or “jump all the way to the beginning of your text.” Anything else you need to scrub through character by character using the space bar control, which is very slow.

    Basically, I don’t think the issue is the keyboard itself. I think the issue is that Android has never prioritized long-form text entry, and so it’s just very buggy.






  • Could still be temperature if the thermistors on e printers read differently–that is, the same setting doesn’t necessarily work out to the same physical temperature on two printers, even if they’re the same model, because the thermistors vary. My suspicion would be that you’re printing a little hot, and the filament is contracting after it’s extruded. On the first few layers it can’t shrink much because of all the material in the middle, but on the vase mode layers there’s nothing preventing it.

    Another possibility is that your overlap percentage between your infill and perimeters is too high. This leads to something that basically is overextrusion, but it’s usually visible as more of a ripple.

    A third possibility is that it’s just the filament.