Model comparison: dive bezel action and alignment, how to compare fairly · RWI-24021

Separate three properties: click count (60 or 120 positions), feel (how firm each click is, and whether there's back-play), and alignment (whether the pip lines up with the 12 o'clock marker at rest). Crisp vs mushy is mostly about feel and back-play. Alignment can be measured, so treat it separately.

On alignment, a clarifying point: is the misalignment visible straight on, or only from an angle? Parallax on a raised bezel can make a perfectly aligned pip look half a click off when viewed slightly from the side. Photograph straight above the dial before calling it misaligned.

Back-play is the most objective feel measurement. Set the bezel on a click and gently push it the other way without forcing it. Noticeable wobble before it engages means play. A little is common and within normal production, but if one model has visible movement and the other doesn't, that's a real difference you can describe.

Separate preference from a potential functional problem. Inconsistent engagement, slipping or uncertain alignment should be documented and checked against the design’s specification by a competent watchmaker; do not invent a universal defect threshold.

Correction to earlier posts in similar threads: 120-click bezels aren't automatically worse. More positions means smaller steps, which can feel less pronounced. Comparing a 60-click and a 120-click bezel on crispness alone is apples to oranges. Compare same-click-count designs, or note the difference clearly.

Clarification for “Model comparison: dive bezel action and alignment, how to compare fairly”: the point beginning “Separate three properties: click count (60 or 120 positions), feel (how…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.

Summary table proposal: click count, back-play (none, slight, noticeable), click consistency around the rotation, and alignment (straight-on photo, offset in fractions of a click). With that, the thread can compare actual properties instead of trading adjectives. Dated corrections welcome below.

Method note for “Model comparison: dive bezel action and alignment, how to compare fairly”: use “Separate three properties: click count (60 or 120 positions), feel (how…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Keep the stated question separate from any broader claim.

Limit of the answer in “Model comparison: dive bezel action and alignment, how to compare fairly”: “Separate three properties: click count (60 or 120 positions), feel (how…” is an excerpt from the discussion, not an independent verification. A reader needs the relevant original material before treating an interpretation as established. Review focus: scope. Keep the stated question separate from any broader claim.

Correction note for “Model comparison: dive bezel action and alignment, how to compare fairly”: retain the wording beginning “Separate three properties: click count (60 or 120 positions), feel (how…” in the record. If later material changes it, add the date, the changed wording and the source for that change; do not invent a completed correction here. Keep the stated question separate from any broader claim.

Reader check for “Model comparison: dive bezel action and alignment, how to compare fairly”: distinguish the discussion point “Separate three properties: click count (60 or 120 positions), feel (how…” from its proposed application. The thread offers a way to reason about the question, without adding a personal experience or a newly observed outcome. Review focus: scope. Keep the stated question separate from any broader claim.

Summary draft for “Model comparison: dive bezel action and alignment, how to compare fairly”: the answer addresses “Separate three properties: click count (60 or 120 positions), feel (how…”; the related point is “Crisp vs mushy is mostly about…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: scope. Keep the stated question separate from any broader claim.

Method note for “Model comparison: dive bezel action and alignment, how to compare fairly”: use “Crisp vs mushy is mostly about…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Keep the stated question separate from any broader claim.

Clarification for “Model comparison: dive bezel action and alignment, how to compare fairly”: the point beginning “Crisp vs mushy is mostly about…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.

Limit of the answer in “Model comparison: dive bezel action and alignment, how to compare fairly”: “Crisp vs mushy is mostly about…” is an excerpt from the discussion, not an independent verification. A reader needs the relevant original material before treating an interpretation as established. Review focus: scope. Keep the stated question separate from any broader claim.

Correction note for “Model comparison: dive bezel action and alignment, how to compare fairly”: retain the wording beginning “Crisp vs mushy is mostly about…” in the record. If later material changes it, add the date, the changed wording and the source for that change; do not invent a completed correction here. Keep the stated question separate from any broader claim.