AI & ML
Slide to Report: Continuous Reporting Symptom-Specific Cybersickness in VR
arXiv cs.HC0 views
arXiv:2611.07345v1 Announce Type: new Abstract: Cybersickness is often assessed during VR exposure through discrete overall sickness, which cannot capture specific symptoms or their changes over time. Post-exposure questionnaires such as the Simulator Sickness Questionnaire provide symptom-specific measures but cannot be collected during immersion. We investigate whether separating cybersickness into three symptom-specific dimensions -- nausea, oculomotor discomfort, and disorientation -- during immersion provides more informative continuous measurements. We conducted a between-subjects study with 52 participants in a VR-rollercoaster, comparing a three-slider interface with a single-slider interface. Concurrently, participants also completed an auditory Simon task to measure attention. We additionally collected multimodal set of physiological signals, including GSR, ECG, PPG, eye and head tracking. Results show that each slider correlated most strongly with its corresponding SSQ subscale, whereas the single slider correlated with all SSQ subscales. Using three sliders did not significantly affect usability, workload, or attention. We publicly release the multimodal dataset to support future cybersickness research.
Source:https://arxiv.org/abs/2611.07345PreviousVector alignment in matrix Lie groupsNextBreaking the Modality Barrier: Multimodal Fusion With Missing Modalities for Cybersickness Prediction
Related posts
如何像 osFoundry 一樣用 Python 包裝 Codex CLI
0dev.to Python

The Microsoft Lab That Worked on AutoGen Is Over. AutoGen Already Gets No Security Fixes
0dev.to Python
GitHub Copilot Just Separated Your BYOK Spend From Its Own — Here's What the New Usage API Actually Shows You
0dev.to DevOps
Why AI Infrastructure and DevTool Companies Need a Different Approach to GTM
0dev.to DevOps
Dependabot Now Updates Your AI Agent's Skills Too — Here's How GitHub's APM Support Works (and Why You Still Have to Read the Diff)
0dev.to DevOps
"Bug genealogy: why a returning bug looks new in code review"
0dev.to DevOps