ドキュメント

サポート

Vivox Core SDK

Vivox Core SDK

Couch co-op configuration

Configure couch co-op for local multiplayer.
読み終わるまでの所要時間 1 分最終更新 2ヶ月前

Many Vivox API request and event types include an additional
account_handle
field that identifies a particular user on a device. In those request types, this field is optional; if left unset, the first user who signs in is the default.
No changes are required in the Vivox SDK initialization workflow for the
vx_initialize3()
or the
vx_req_connector_create
request.
To begin a multi-user voice play session, simultaneously sign in multiple users by using the
vx_req_account_anonymous_login
request, with different
account_handle
values specified for each of the different users.
For couch co-op implementations, you receive a unique set of events for each user who is signed in. Use the
account_handle
attribute to differentiate the events for each user. For more information, refer to Network connection state events.
After multiple users are signed in, you must assign them separate render and capture devices. You can design your game to automatically select these devices, or the game can present a UI to allow users to select their specific devices. Set other device attributes on a per-user basis, such as the mute status, volume, and voice activity detector (VAD) properties, by supplying the corresponding user's
account_handle
in the request type.
You can also add users to their own independent sets of session groups and sessions, or add them to the same sessions. If you add multiple users on the same device to the same session, then use the
vx_req_session_set_participant_mute_for_me
request to locally mute those users to each other so they do not hear an in-channel echo of anyone who is speaking that is physically nearby to them.