Immersion is a system property; presence is a subjective experience

What it is

Field of view, tracking degrees of freedom, persistence, and resolution can be written down without asking anyone. “I felt I was in that kitchen” has no answer until a person is asked. The first set is immersion — an objective description of the sensorimotor contingencies a system can support. The second is presence — a subject’s experience of being there. Slater split the terms because everyday speech and a good deal of product copy treat them as one word.

They answer different questions. Immersion asks what the device and the render pipeline do. Presence asks whether a perceptual system took the current input as the environment it occupies. Raising resolution from 2K to 4K changes immersion; that is a fact. That the same upgrade leaves one person more “there” and another unmoved is presence, and it does not belong in the same spec cell.

Why it happens

Immersion can be a system property because it enumerates checkable capacities: how many degrees the display surrounds, whether tracking includes translation, whether the real world is shut out, which band latency and resolution sit in. Those quantities are fixed before anyone puts the headset on. Presence can only be a subjective experience because it depends on perception collapsing multi-channel input into a hypothesis of “I am here” — a hypothesis that needs attention on the environment and a person who responds to this kind of stimulation. No subject, no presence.

The mix-up lives in measurement language. “The immersion was great” in an interview sounds like a verdict on the system; the grammatical subject is a feeling. “Presence at 120 Hz” in a hardware launch sounds like a verdict on experience; the number is a refresh rate. The two variables differ in scale, error source, and lever: changing a lens and changing a narrative can both move a questionnaire score, but only the lens changes immersion.

Studying it

Operationalise the two with separate instruments. Immersion is an objective inventory of device and software: horizontal and vertical field of view, degrees of freedom, motion-to-photon time, angular resolution, whether reality is occluded. Presence requires a person: the Slater–Usoh–Steed questionnaire, the spatial-presence subscale of the Igroup Presence Questionnaire, electrodermal response to a virtual threat, stopping distance at a virtual pit.

Independent variables: spec tier (this changes immersion); content and task (these change other things that may move presence). Dependent variables: completeness of the spec checklist; questionnaire, behavioural, and physiological presence measures. The decisive contrast is the same hardware across people, or the same person across content — presence will move, the immersion inventory will not. That is how you show they are not one construct.

Do not take an “immersion rating” as the sole dependent variable and claim to have measured system capability. A questionnaire cannot read field of view.

Where it stops holding

Witmer and Singer’s Presence Questionnaire folds involvement, attention, and a felt sense of “immersion” into one instrument; industry talk of an “immersive experience” is closer to that broad usage than to Slater’s cut. Papers and reviews have to say which set they are using. When a CAVE is compared with a headset, field of view, occlusion, and social visibility move together, so immersion sub-items are coupled and a total-score gap cannot be read as presence being driven by a single system factor. Unconscious behaviour (reaching for a virtual rail) is treated by some as an operational definition of presence and by others as sensorimotor performance that immersion makes possible — the behaviour itself does not declare its class; the research question does. A first-time wearer’s gasp mixes novelty with presence and is not a reading of a system property.

Applying it

• Split requirements and acceptance into two columns: one for checkable system capacities (field of view, degrees of freedom, latency budget, resolution), one for experiential claims that must be asked of a person. Ban “very immersive” as a signature on both.
• For a hardware or rendering change, ask first which row of the immersion inventory moved. For a content, narrative, or onboarding change, ask whose presence report is expected to move, and on which item. A change that answers neither should not be justified by presence.
• In study notes, code “the device let me see all around” and “I forgot I was in the lab” as different events. Do not merge them under one immersion/presence tag.
• How to check: take a page of product copy and mark each sentence “can be verified without wearing the device” or “must be asked of a person.” Sentences that fit neither class are where the terms have been fused.

Related

• Same group: N1.01.2 High immersion does not necessarily produce high presence · N1.01.3 What breaks presence is often inconsistency in the details
• Nearby: N1.03 Field of View · N4.08 Spatial Scale and Size Perception
• Search terms: immersion-presence distinction · place illusion · sensorimotor contingencies