This is experimental mod-independent multiview protocol implementation This is pure engine-side modification so you obviously need: * 1.32e MV-server to send multiview stream or record multiview server-side demos * 1.32e MV-client to query multiview stream and playback multiview demos =============================== client commands: ------------------------------- \mvjoin [password] - ask for multiview stream (use regular \record command to record multiview demo) \mvleave - return to legacy dm_68/dm_71 protocol after demo being recorded - you can play it with regular \demo command \mvfollow [clientID] - select POV to clientID during demo playback or use MOUSE2 to cycle next =============================== server cvars: ------------------------------- \sv_demoClients 0 - max.number of client slots for \mvjoin|\mvleave notice: this takes about 4x more memory than regular player slots \sv_demoPassword "" - password for \mvjoin \sv_demoFlags 3 - bitmask, periodically issue "score" on client side to get actual stats for 1 - server-side autorecorded demos 2 - client-side \mvjoin's \sv_autorecord - automatic server-side demo recording if there is connected, not affected by sv_demoClients or sv_demoPassword in any way =============================== server commands: ------------------------------- \mvrecord [filename] - start server-side demo recording, resulting demos can be later played client-side via \demo command notice: you need at least 1 connected client to start, recording will be automatically stopped on last active client (not a bot) disconnect \mvstoprecord - stop server-side demo recording