• 0 Posts
  • 58 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle






  • Genuinely as hard as “bring back the NGage.” Nobody wants to buy a smartphone that’s also a console platform. There’s no three-year contract required, and AT&T doesn’t get to micromanage the dashboard, but it’s still two wildly different commitments for no sufficient benefit. It means being stuck with a wonky smartphone on a longer console lifecycle and overpaying for a console with all the limitations of a smartphone.

    By contrast - this is a controller with a screen in it. That’s all. Why wouldn’t they sell that? What’s the downside, for them? You buy another accessory priced well beyond its material costs, you provide all the electricity and electronics necessary for it to do anything, and they don’t care if you ever play games on it. It’s not lashed to the success of yet another online store. It’s not even a vehicle for recurring subscription fees. It’s a dongle for another toy. They have no incentive to force it to catch on. If it doesn’t sell - they’ll just stop.




  • I’m not surprised. You did your worst immediately and learned approximately nothing. You escalated to a tantrum over getting what you asked for, alongside - again - gentle offhand criticism.

    And you’re still doing edgelord bullshit like you really flexed on someone by calling them the n-word.

    Nevermind the irony of your complete inability to wonder - were you called “prickly” on account of your own actions? Does your back-of-a-Big-Dogs-t-shirt philosophy apply to you?

    … do you maybe think “prickly” means someone called you a prick?


  • Yes. You immature font of toxicity. I linked to a page specifically about how a short script, from scratch, can convince Linux you have a joystick attached. Is it a trivial turn-key solution? No. Does that justify the screeching slurs you’ve spat? Not at all, you fucking gremlin.

    edit: Saw your contrary follow-up, doesn’t change anything. Be better in the first place. And I don’t mean your grammar.










  • Good answer. Especially if it could degrade gracefully for low performance, without temporal artifacts. E.g., have ray-surface hits act like point projectors with approximate visibility, so indirect lighting splashes brightness on a soft region instead of creating a hotspot.

    I think there’s a general solution to noise that’s gone unused.

    Okay, Metropolis light transport jiggles steps in each bright path, to find more low-probability / high-intensity paths. Great for caustics. But it’s only used on individual pixels. It samples a lot of light coming in to one spot. We want the inverse of that.

    When light hits a point, it can scatter off in any direction, with its brightness adjusted according to probability. So… every point is a light source. It’s not uniform. But it is real light. You could test visibility from every hit along any light path, to every point onscreen, and it would remain a true unbiased render that would eventually converge.

    The sensible reduction of that is to test visibility in a cone from the first bounce offscreen. Like if you’re looking at a wall lit by the moon, it goes eye, wall, moon, sun. Metropolis would jitter to different points on the moon to light the bejeezus out of that one spot on the wall. I’m proposing to instead check moon-to-wall visibility, for that exact point on the moon, but nearby spots on that wall. (Deferred rendering can skip testing between the wall and your eye. Pick visible spots.)

    One spot on the moon would not accurately recreate soft moonlight - but Blender’s newer Eevee renderer proves that a dozen can suffice.

    One sample per pixel could be a million.

    You don’t need to go from all of them, to every point onscreen, to get some pretty smooth results. Basically it’s “instant radiosity” but with anisotropic virtual point sources. It’s just a shame shadowing still needs to be done (or faked) or else applying them would be doable in screen space.