SWIFTPOINT//HUB
Support

Profile Builder · Deep-click & pressure zones

Turning the Z3's two-stage buttons and tilting click zones into extra actions that fire exactly when you press hard enough.

The Z3's headline trick: a selected set of buttons measure how hard you press, scaled 0–100 % along the force axis, with a physical tactile dash halfway down. A normal light press stops before the dash; pushing through it is a deep press. Each button can have several deep zones, so one physical button can trigger completely different actions at different press depths.


1. Which buttons measure force?

Only 5 buttons carry the force sensor:

  • Left Button
  • Right Button
  • Middle Button
  • Left Fingertip
  • Right Fingertip

All other inputs (Triggers, Thumb, Edges, Wheel) are binary on/off switches — no pressure. The Builder shows these as separate + Deep zone rows only on the force‑capable button cards, so you can click any of the 5 buttons and see the option.


2. The Press stages card

When you select one of the 5 buttons, the right rail shows a vertical pressure axis (0–100%) with three layers:

  1. Light press — the default Button press trigger, i.e. anything before the tactile dash. You can add several "light" bindings (e.g. one Key and one Haptic), all fired together on a normal click.
  2. Drag range — the deep part of the axis you drag a range across to form a zone start→end.
  3. + Deep zone — click to add another force band. Multiple zones stack along the axis, e.g. 40–60 %, 60–80 %, 80–100 %.

Everything you create here is literally the Deep-click zone trigger from bindings.md — the card is just a nicer way to build the same thing.


3. Zone fields (what they mean)

Actual trigger fields for a deep zone:

Field Range Meaning
Direction increasing / decreasing / both Only fire when force rises through the zone, only when it falls, or both. Usually increasing for a push.
Entry start % / Entry end % 0–100 The force band where the zone is considered entered.
Exit start % / Exit end % 0–100 The force band where it's considered left. Often a slightly lower band than entry so the press feels stable (hysteresis).

Default zone suggestion the Builder offers: entry 20–100 %, exit 0–80 % for a classic "deep press" feel.

Ranges are expressed in percent (0–100); steps are in 1 % — pressure is stored at 0.1 % precision internally.


4. The key rules

  • A button's light press is a separate mapping from its deep zones. They don't conflict: light actions fire on a light click, zone actions only when the press actually crosses into the zone.
  • Zones are per button, sorted along the force axis. Zones on different buttons don't interact.
  • Two zones must not overlap. The Builder checks this in the Diagnostics tab and flags e.g. Left Button: deep zones overlap at NN%.
  • One force axis = one thing at a time. Since a physical press is a single force value, enter exactly one zone at once — that's the intended design.
  • Entry and exit differ to avoid jitter. As you hold a deep press, tiny force wobbles shouldn't re‑toggle the zone; the (lower) exit band absorbs that wobble. You can make them equal for a strict band if you prefer.

5. Example setups

Two‑stage trigger (classic):

Mapping Trigger Activation
light Button press (Left) Key 1 [tap]
deep Deep zone 20–100% Key 2 [tap]

Light tap throws the flashbang; pushing through the dash throws a different one — without moving your hand.

Hold‑to‑ADS on the Fingertips:

Mapping Trigger On activation / deactivation
light Button press (Left Fingertip) (nothing — dead zone)
deep Deep zone 40–100 % On act → Mouse button Right [hold down] · On deact → Mouse button Right [release]

Relax = nothing; lean on it = right‑button held (ADS); ease off through the exit band = released. Because you keep your grip the whole time, this feels faster than left‑hand Ctrl.

Three‑band scroll wheel: zones 30–60 %, 60–90 %, 90–100 % on Middle Button → Mousewheel down +N with different notches per band (N = 1 / 4 / 12). Push progressively harder to scroll faster.

Fingertip DPI clutch: deep zone on Right Fingertip → DPI selection select to a low value; deactivation → back to high. Perfect for sniping or micro‑adjustments, with no keyboard key used.


6. Troubleshooting

Symptom Likely cause
Deep actions never fire Zone entered but release happened first (you click too fast) — widen the entry band and press with intent.
Fires twice per press You have one trigger as increasing and one as both on the same band — they both fire.
"overlap at NN%" in Diagnostics Two zones on the same button share part of the axis — shrink/redo the ranges.
Light actions fire and deep fires on a hard tap Intended. Button press catches the whole light stage; your force passes through the deep zone on the way down. Use direction increasing if you want zone actions only on force rising.
Haptic feels weak on a zone Check Haptic pulse strength % (0 = off) and per‑zone settings; also make sure the default depth of the zone wants a stronger value than 0.

7. Tips

  • Put your most‑used action on the light stage — deep presses are slower and tire the finger.
  • Use fingertips for clutch/hold roles (ADS, weapon cycle) because the deep‑click grip already sits where your aim doesn't move.
  • If a game treats deep presses as double‑clicks, give zones a small hysteresis (wide entry, narrow exit) and test how fast you can mash.
  • Check the force axes read‑out in Diagnostics / the OLED deep‑click forces display while testing — it visualises where your real presses sit on the 0–100 % axis.