this post was submitted on 12 Jul 2024
217 points (92.5% liked)

PC Gaming

8568 readers
493 users here now

For PC gaming news and discussion. PCGamingWiki

Rules:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments, within reason.
  10. Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] hedgehog@ttrpg.network 4 points 4 months ago (2 children)

Personally I didn’t think the pregnancy test one really counted, either, but I’m with you on this one. This isn’t just “I put Doom on a sex toy,” but “I put Doom on a sex toy and used game events to trigger its functionality,” which is a level above.

Also looking at the pregnancy test one now I might change my mind. They did use a different microcontroller and screen, but the pregnancy test already had a microcontroller inside it; it just wasn’t programmable. If the replacement microcontroller and screen had the same specs as the old one, it’s more than fair to call that a win IMO. At that point, it’s the same hardware, after all.

[–] xthexder@l.sw0.com 1 points 4 months ago (1 children)

Except the original pregnancy test screen would have been something like a 2 or 3 segment LCD. They don't need to display anything but yes or no.

[–] hedgehog@ttrpg.network 1 points 4 months ago

Ah, good point. Apparently it shows 4 different things: https://twitter.com/foone/status/1301718864573554689

[–] kernelle@lemmy.world 1 points 4 months ago

Yeah I haven't seen the pregnancy test one, can't really claim it's the test running it when it's not. Definitely agree with your point as well.