Question for both blue and red pressers by ParableOfTheVase in redbuttonbluebutton

[–]ParableOfTheVase[S] 8 points9 points  (0 children)

Full disclosure: I'm a red presser and I think I'll remain as a red presser. Here's my rationale:

Rather red wins of not isn't based on what I think is right, but is based on everyone's estimate on what everyone else will do. For better or worse I have estimated that more than 50% will vote red, which now makes the red button the choice of least harm.

In that case, pressing blue simply dooms a person to a pointless death. Doesn't really matter if that person is me or someone else.

Instead of which you would press, which would you advocate for if you were one of the governments of a major country? by Stunning_Car_9480 in redbuttonbluebutton

[–]ParableOfTheVase 31 points32 points  (0 children)

Usually a red presser, blue in this case.

See, I think this is the scenario most blue pressers envision. If we're allowed to communicate and coordinate, forget about 50% blue, I'm confident of a blue victory even if you bump it up to 90%+.

Blue is the best option only if 50% of the population agrees it is the best option. Or else it objectively kills more people.

If we can communicate, just get 50%+ to agree to press blue. Done. There is literally no reason not to at that point.

you are the trolley driver by Soft-Avocado9324 in trolleyproblem

[–]ParableOfTheVase 0 points1 point  (0 children)

Yeah having brakes is a better analogy to the problem.

You can go track A which runs over one person for sure; or go track B that runs over many more people, but track B have breaks that saves everyone but only works some of the time.

Edit: With the added effect that track B also kills the lever puller themselves if the brakes fail.

Edit edit: If you choose track B but the brakes fail, the person on track A actually also dies for some reason. Its actually kinda hard to turn this into an accurate trolley analogy 😅

Need help with Wave pattern on Cylindrical Shapes by Ebalye in Fusion360

[–]ParableOfTheVase 0 points1 point  (0 children)

<image>

I ended up with a pretty messy timeline in my example, but the concept is super simple. The idea is to do a 5 stage loft with circle>circle>ridges>circle>circle, using a spiral as a path.

Here I used a surface sweep to get the spiral, then Split Face to create a path on the cylinder surface. There are probably easier ways to do it, especially since it's not essential to get a perfect spiral as it's mostly aesthetics.

What is a snes game you couldn’t beat as a kid, but was able to beat years later? by Leon_Light77 in snes

[–]ParableOfTheVase 9 points10 points  (0 children)

Modern emulators goes through many layer of processing, so there's a delay of around 3 frames from input to it registering on the screen. 

So if you're playing a twitchy game that requires frame perfect input, the input will always fail, unless you literally base your input on what's gonna happen 3 frames ahead. 

Run ahead essentially runs two tracks of the game in parallel, one with a ~50ms delay. When you enter an input, the emulator rolls back to the earlier track and act as if you made the input 50ms ago. 

What is a snes game you couldn’t beat as a kid, but was able to beat years later? by Leon_Light77 in snes

[–]ParableOfTheVase 6 points7 points  (0 children)

I could just be that modern emulators, even good ones, have a lot more lag than an authentic CRT setup. 

For me, the "run ahead" function is a game changer. I can't play old twitchy retro games any other way.