CTR Pia
4.11.3
Game Communication Engine
|
$CTRPIA_ROOT/sampledemos/session
Go to the $CTRPIA_ROOT/sampledemos/session
directory and execute as follows.
% omake
The executable (.cci
) file is generated in:
$CTRPIA_ROOT/sampledemos/session/(sample demo name)/images/(platform name)/(target name)/
As an example, the files are generated in the following folder:
$CTRPIA_ROOT/sampledemos/session/RandomMatchmake/images/CTR-TS.Process.MPCore.fast/Release/
session/RandomMatchmake Sample Demo | This demo performs random matchmaking as a simple example of using nn::pia::session::Session . |
Advanced Session Sample Demo | This demo performs random matchmaking, browse matchmaking, and friend join-in matchmaking using nn::pia::session::Session . |
session/Mesh Sample Demo | This demo illustrates the usage of the nn::pia::session::Mesh class. It uses the host migration feature, station identification tokens, and the relay communication feature. |
session/JointSession
sample demo because the demo itself was removed. session/RandomMatchmake Sample Demo
, Advanced Session Sample Demo
, the session/JointSession
sample demo, and session/Mesh Sample Demo
in keeping with changes to the structure of the Session
sample demo. MeshAdvanced
. MeshSimple
demo. SampleFramework
. PiaInet
when transitioning from a "communicating" state to a "matchmaking" state (while logged on to the game server). Reinitialization was not required in this situation, so the code was revised accordingly. MeshSimple
demo nor the MeshAdvanced
demo used the packet-signing feature of the PiaTransport
class, but this demo was modified to use this feature because it is recommended to sign packets when going over insecure communication routes, such as the Internet. UserName
of the UDS host. TemporaryId
was shown on the screen as the information about nearby networks discovered in the matchmaking state (local). Now the UserName
of the UDS host is shown instead. UserName
of the host for local communication and the GatheringID
for Internet communication) appears on the screen. Pia
library to the screen display. SAMPLE_SUB_ID
; in Internet communication: MATCHMAKE_GAME_MODE
) from within the communication route selection state using button operations. MeshSimple
and MeshAdvanced
demos to ExpHeap
only. nn::pia::local::UdsNode
layer when local communication ends. Session::Cleanup
function is now always called when communication ends, in consideration of the potential for a disconnection immediately after calling a function that leaves the session, such as nn::pia::session::Mesh::LeaveSession "Mesh::LeaveSession"
. nn::socket
and nn::ac
API functions when ending Internet communication. Mesh::Startup
in MeshAdvanced
to provide an example of using an overload of the Mesh::Startup
function that enables you to specify settings, such as the timeout period of the session participation process. nn::pia::session::Mesh::JoinSession "Mesh::JoinSession"
function by adding a Result
value returned when an asynchronous process fails. MeshAdvanced
so that when Internet communication ends, stations just leave the matchmaking session instead of deleting it, even if you are the session owner. Mesh::Cleanup
function is now called immediately.