文档

​
​

Development

User Acquisition

Monetization

工业

Vivox Core SDK

Vivox Core SDK

此页面不支持所选语言。
Vivox
​
​
Vivox Core SDK
  • Overview
  • Before you begin
  • Get started
    • Integration guide
      • Phase 1: Planning and organization
      • Phase 2: Implementation
      • Phase 3: Testing
        • Smoke test
        • Feature checkpoints
    • Quick start guide
  • Release notes
  • Developer Guide
  • Reference
  • Privacy overview
  1. Vivox Core SDK documentation

Smoke test

What to look for when smoke testing Vivox.
阅读时间1 分钟
最后更新于 8 个月前

When a user has voice enabled, UI elements indicate channel join state and what options (for example, mute, push-to-talk) are active and usable. Otherwise, UI elements aren't active or indicate that a user isn't in a channel.
  • UI elements
    • User is connected to a Vivox voice network but is not in a channel or call.
    • User is in a channel or call, and they see a personal speaking indication or for another person.
    • Microphone is active or inactive (muted).
    • Push-to-talk is active or inactive.
  • UI function controls
    • Selecting a channel to enter gets the user to the expected channel.
    • If mute for me is implemented, check for persistence by restarting the game.
    • Entering or leaving a channel works.
    • Choosing a different capture (microphone) or render (loudspeaker) device correctly updates the UI.
  • Logging checkpoints
    • Vivox voice network connection, login, and session creation.
    • Channel activity: for example, speaking indications.
    • Capture device or render device changes: for example, volume or changing devices.
    • Vivox connectivity is monitored. For example, an error is thrown when voice unexpectedly disconnects or logouts.

Copyright © 2026 Unity Technologies
法律信息隐私政策CookiesDocumentation Terms of Use请勿出售或分享我的个人信息您的隐私选择(Cookie 设置)

“Unity”、Unity 徽标及其他 Unity 商标是 Unity Technologies 或其附属公司在美国和其他地方的商标或注册商标(此处查看更多信息)。其他名称或品牌是其各自所有者的商标。

为方便起见,一些页面是机器翻译的,可能包含不准确的内容。如有信息不一致的情况,以英文版本为准。


    报告此页面的问题