mirror of https://github.com/godotengine/godot-demo-projects.git synced 2026-01-04 15:00:09 +01:00

Files

Hugo Locurcio a45b84a5ad Handle multiple resolutions in most demos

This makes demos render correctly on hiDPI displays,
while also demonstrating how to handle multiple resolutions.

The 3D in 2D demo now uses "3D No-Effects" for the 3D viewport,
which is faster to render. Thanks to this, 4× MSAA is now enabled
for a better result.

The background loading demo now uses mipmaps for better-looking images.

The material testers demo now samples mouse input in a
resolution-independent manner when panning.

Default clear colors were also changed in some projects for visual
consistency with the project's theme.

2020-01-28 19:08:03 +01:00

client

Add webrtc signaling example

2019-06-14 06:15:22 +02:00

demo

Handle multiple resolutions in most demos

2020-01-28 19:08:03 +01:00

server

Add webrtc signaling example

2019-06-14 06:15:22 +02:00

server_node

Add webrtc signaling example

2019-06-14 06:15:22 +02:00

.gitignore

Add webrtc signaling example

2019-06-14 06:15:22 +02:00

project.godot

Handle multiple resolutions in most demos

2020-01-28 19:08:03 +01:00

README.md

Add webrtc signaling example

2019-06-14 06:15:22 +02:00

README.md

A WebSocket signaling server/client for WebRTC.

This demo is devided in 4 parts:

The server folder contains the signaling server implementation written in GDScript (so it can be run by a game server running Godot)
The server_node folder contains the signaling server implementation written in Node.js (if you don't plan to run a game server but only match-making).
The client part contains the client implementation in GDScript.
- Itself divided into raw protocol and WebRTCMultiplayer handling.
The demo contains a small app that uses it.

NOTE: You must extract the latest version of the WebRTC GDNative plugin in the project folder to run from desktop.

Protocol

The protocol is text based, and composed by a command and possibly multiple payload arguments, each separated by a new line.

Messages without payload must still end with a newline and are the following:

J: (or J: <ROOM>), must be sent by client immediately after connection to get a lobby assigned or join a known one. This messages is also sent by server back to the client to notify assigned lobby, or simply a successful join.
I: <ID>, sent by server to identify the client when it joins a room.
N: <ID>, sent by server to notify new peers in the same lobby.
D: <ID>, sent by server to notify when a peer in the same lobby disconnects.
S: , sent by client to seal the lobby (only the client that created it is allowed to seal a lobby).

When a lobby is sealed, no new client will be able to join, and the lobby will be destroyed (and clients disconnected) after 10 seconds.

Messages with payload (used to transfer WebRTC parameters) are:

O: <ID>, used to send an offer.
A: <ID>, used to send an answer.
C: <ID>, used to send a candidate.

When sending the parameter, a client will set <ID> as the destination peer, the server will replace it with the id of the sending peer, and rely it to the proper destination.