Project

General

Profile

Wiki » History » Version 66

Josip Almasi, 03/03/2022 11:12 PM

1 4 Josip Almasi
{{toc}}
2
3 1 Josip Almasi
h1. Welcome!
4 2 Josip Almasi
5 18 Josip Almasi
h2. External resources
6 4 Josip Almasi
7 14 Josip Almasi
Demo site: https://www.vrspace.org/
8
9 15 Josip Almasi
Github project page: https://github.com/jalmasi/vrspace
10 2 Josip Almasi
11 63 Josip Almasi
OpenSource.com articles: 
12
https://opensource.com/article/20/12/virtual-reality-server
13
https://opensource.com/article/22/1/open-source-metaverse
14 3 Josip Almasi
15 15 Josip Almasi
VR Days video (features, technologies): https://vimeo.com/475142708
16 3 Josip Almasi
17 15 Josip Almasi
Youtube channel: https://www.youtube.com/channel/UCLdSg22i9MZ3u7ityj_PBxw
18 1 Josip Almasi
19 16 Josip Almasi
Facebook page: https://fb.com/vrspace.org
20 14 Josip Almasi
21
Client API jsdoc: https://www.vrspace.org/docs/jsdoc/index.html
22
23
Server javadoc: https://www.vrspace.org/docs/javadoc/index.html?overview-summary.html
24 4 Josip Almasi
25 23 Josip Almasi
h2. Playgrounds
26
27
Multi-user interaction, shared objects: https://playground.babylonjs.com/#ZBK155
28
Multi-user world: https://playground.babylonjs.com/#Y6ILJ5
29
Avatar selection, portals: https://playground.babylonjs.com/#HDV7LA
30 24 Josip Almasi
VR Avatar template world: https://www.babylonjs-playground.com/#VXA0R3
31 23 Josip Almasi
32 17 Josip Almasi
h1. Frequently Asked Questions
33
34
h2. Is this open source, free to use and share?
35
36
Yes, it's all free and open. Server and client code is published under Apache 2 license, all 3D models published by their respective authors under Creative Commons Attribution license.
37
38
h2. Is there any documentation?
39
40
This is good place to start, this page links to all available resources.
41
42 45 Josip Almasi
h2. I want to build my space, where do I start?
43
44 46 Josip Almasi
This question prompted writing Getting Started section of this wiki, but set up basic development environment first.
45
You don't need to modify any of the server code, but you need to be able to get it from github and build it.
46
Once you do, start it up, and everything else is html 5 and javascript ES6.
47 45 Josip Almasi
48 66 Josip Almasi
h2. How do I create my own world(s)?
49
50
You can use any authoring tool that exports glTF: Blender, Unity, Unreal, to name a few. You will likely need some glTF exporter plugin.
51
52
53 17 Josip Almasi
h2. How many users can share a “world/space” simultaneously?
54
55
By default, number of users per space is not limited. There is a server parameter to limit that (org.vrspace.server.maxSessions) that can be specified either in config file or command line. Users that hit the limit remain in the queue for configurable timeout (org.vrspace.server.sessionStartTimeout, zero by default) until someone leaves. An error is raised on timeout.
56
57 39 Josip Almasi
h2. How can I implement custom authentication and/or authorization?
58 1 Josip Almasi
59 39 Josip Almasi
Typically you will authenticate users on your web server, before they enter the world. 
60
If that's not enough, you can implement your own "ClientFactory":https://github.com/jalmasi/vrspace/blob/master/server/src/main/java/org/vrspace/server/core/ClientFactory.java and configure it in "application.properties":https://github.com/jalmasi/vrspace/blob/master/server/src/main/resources/application.properties file.
61 1 Josip Almasi
This allows you to do your own database queries, REST calls or whatever else you may need to identify your users.
62
63 39 Josip Almasi
h2. How is that different from a game server?
64 38 Josip Almasi
65 40 Josip Almasi
It's not all that different, though the emphasis is different: vrspace.org is not focused on games specifically. It's more about multi-user 3D web, in particular WebXR, open standards and open source.
66 39 Josip Almasi
So while game servers usually don't bother with video/audio streaming, vrspace.org provides it out of the box, using WebRTC. On the other hand, there's nothing like game level in vrspace.org.
67 59 Josip Almasi
Basic difference is that, while game servers focus on sharing the state of the game, vrspace.org server shares the state of any number of objects. No object in particular special in any way, there's no 'game loop' object.
68 38 Josip Almasi
69 42 Josip Almasi
h2. How does inverse kinematics and motion tracking work in vrspace.org characters?
70 41 Josip Almasi
71 62 Josip Almasi
Everything is encapsulated "Avatar class":https://github.com/jalmasi/vrspace/blob/master/babylon/js/ui/avatar.js, but relies on observed glTF avatar structure. Heuristics used to analyze the character structure is explained in depth in "this research paper":https://www.researchgate.net/publication/356987355_TOWARDS_AUTOMATIC_SKELETON_RECOGNITION_OF_HUMANOID_3D_CHARACTER.
72 41 Josip Almasi
73 56 Josip Almasi
h2. Why websockets?
74
75
Since death of internet explorer, websockets just work, in any browser. Some reliable multicast protocol would do better job for object state distribution, but no such protocol is supported by web browsers. WebRTC on the other hand is widely supported, but is unreliable, and requires complex development environment setup.
76
77 60 Josip Almasi
h2. Can I make/buy and use my own unique avatar?
78
79
Sure you can, but note that technically you can't prevent anybody else from copying and using it. Using video avatar is the only practical option to have unique appearance.
80
81 64 Josip Almasi
h2. How to enable https?
82
83 65 Josip Almasi
The server comes bundled with self-signed certificate, so all you need to do to enable SSL is change *server.ssl.enabled* property in "application.properties":https://github.com/jalmasi/vrspace/blob/master/server/src/main/resources/application.properties to true. You may also want to set *server.port* to 443.
84 64 Josip Almasi
85 47 Josip Almasi
h1. Getting started
86
87
So, you're new to VRSpace, and you want to make yourself a new virtual world.
88
You will not need to change any of the server code, but you need to get it from github, build it, and start it.
89
Once done, familiarize yourself with directory structure, and especially with template world, as this is intended stating point.
90
91
h2. Directory structure
92
93
h3. server
94
95
Contains the server code and configuration. Generally you don't need to change the code, but you may want to change the configuration. Main configuration file is in src/main/resources/application.properties, have a look at what you can change.
96 50 Josip Almasi
The server executable is a jar file in target subdirectory.
97 47 Josip Almasi
98
h3. babylon
99
100
This is reference Babylon.js client implementation. You don't really need any of it, but it is highly recommended to build on top of it, using javascript code provided there.
101
Html files there implement and/or test different functions available, like avatar loading and movement, video/audio streaming etc.
102
Most important one is avatar-selection.html, this is main entry point that allows user to select avatar and enter a world.
103
104
h3. web
105
106
This is the actual web site that's available online on vrspace.org, your final web site will probably look somewhat like this.
107
108
h3. content
109
110
Actual web content used to build virtual worlds, with self-explanatory directory names. Two of these contain special attention though:
111
112
h4. char
113
114
Characters, under female, male and other subdirectories. These directories are listed and presented by avatar-selection.html, you will probably to change how it works eventually.
115 48 Josip Almasi
But adding or removing characters is as simple as dropping them here.
116 47 Josip Almasi
117
h4. worlds
118
119 48 Josip Almasi
Available worlds, also listed by avatar-selection.html, and displayed as portals. Every subdirectory contains one world, and also note there's an image with the same name - that's thumbnail displayed on the portal.
120 49 Josip Almasi
Every world has some specific features.
121
Paris is huge, a real-life model.
122
Persian city and Aladin both feature the same procedural terrain and plants.
123 1 Josip Almasi
Cave is an actual game level, and utilizes floors built with vrspace.org floor editor.
124 50 Josip Almasi
Classrooom allows for sharing screen.
125
But the template is where you start - copy it over to another directory, and edit to suit your needs.
126
127
h2. Your first world
128
129 51 Josip Almasi
So with the server running, copy the template directory to your own. This world is immediately listed at http://localhost:8080/content/worlds/ and also available in http://localhost:8080/babylon/avatar-selection.html as a portal.
130 1 Josip Almasi
All you need to do to replace that dolphin with your own world is to replace this.file='dolphin.glb' in world.js with your own file name. Or really, delete the entire constructor, and save your world as scene.gltf in the same directory.
131 51 Josip Almasi
Hit reload button/key in your web browser, changes become visible immediately.
132 50 Josip Almasi
133
There are two files there, a html and a js, but html also contains some javascript.
134 52 Josip Almasi
The idea behind this separation of concerns is that world.js contains all programming logic that relates to the world itself, it should not depend on any server functionality. So build your world first, then add multi-user functions to it. Javascript in the world.html file shows some basic multiuser functions. As these grow, you'll probably want them in another javascript file, but these are minimum to get started.
135 50 Josip Almasi
136 51 Josip Almasi
Hopefully comments world.js and world.html explain enough to get started. As you need more functionality, look at other worlds and copy it over.
137 47 Josip Almasi
138 4 Josip Almasi
h1. Setting up development environment
139
140
Here's all you need to start development on Windows.
141 20 Josip Almasi
Linux distributions include all these tools as native packages, so no additional downloads should be required.
142 4 Josip Almasi
143
h2. Basic setup
144
145
h3. Git bash
146
147
IDEs can work with github directly, but whatever you ask, you'll get a command line answer.
148
Command line git is simply a must have. Bash also includes a lot of goodies like ssh.
149
150
https://git-scm.com/downloads
151
152
h3. Java
153
154 21 Josip Almasi
Java 8 will work, java 11 recommended. JDK is required to build the server.
155
Get it either from Oracle or elsewhere, e.g. Zulu OpenJDK: https://www.azul.com/downloads/zulu-community/?package=jdk
156 4 Josip Almasi
157
h3. Node.js
158
159
Node is used by IDE to evaluate javascript. You'll also may need it if you modify any of babylon.js source.
160
Mind that IDE will complain if you installed unsupported version of Node; should that happen, remove Node, and install latest one supported.
161
162
Get it from https://nodejs.org/
163
164 19 Josip Almasi
h3. Maven
165
166
Apache Maven is used to build the server from command prompt.
167
168
Get it from https://maven.apache.org/download.cgi
169
170
171 4 Josip Almasi
h3. IDE
172
173
Eclipse for Java developers (not enterprise), with Spring and Web plugins:
174
175
Download eclipse here: https://www.eclipse.org/
176
177
And then go to Help -> Eclipse Marketplace
178
Search and install Spring Tools 4 and Wild Web Developer plugins.
179
180 6 Josip Almasi
You'll also need to download and install https://projectlombok.org/
181 8 Josip Almasi
Once done, restart the eclipse.
182 6 Josip Almasi
183 5 Josip Almasi
h2. Import and start the project
184
185 22 Josip Almasi
h3. IDE
186
187 5 Josip Almasi
In Eclipse, you can use either default or new workspace for the project.
188
Assuming you have cloned the project from the github, 
189
Go to File -> Open Projects From the Filesystem
190
Then choose vrspace directory.
191
192
This will import vrspace folders and project subfolders, click Finish.
193
194
In vrspace project folder, in src/main/java, there's org.vrspace.server.ServerApplication.java.
195
Open it, then right click on the code.
196
From the menu, choose either Run as or Debug as -> Spring Boot App.
197
198
Open http://localhost:8080/babylon/connect.html with two browsers, and navigate around.
199
200
That's all, you're all set!
201 22 Josip Almasi
202
h3. git bash
203
204
git clone https://github.com/jalmasi/vrspace.git
205
cd vrspace
206
mvn clean install
207
java -jar server/target/server-0.2.2.jar
208 4 Josip Almasi
209
h2. Advanced setup
210
211 12 Josip Almasi
h3. SSL
212 4 Josip Almasi
213 12 Josip Almasi
HTTPS is required for pretty much everything - WebXR, camera, mic access.
214
By default, the server runs on 8080 port with plain HTTP. To enable HTTPS, edit application.properties (found in src/main/resources), and change following properties:
215 1 Josip Almasi
216 12 Josip Almasi
<pre>
217
server.ssl.enabled=false
218
# default port 8080
219
#server.port=8443
220 13 Josip Almasi
</pre>
221 12 Josip Almasi
222
h3. Apache
223
224
Apache reverse proxy setup, linux, windows, TBD
225 4 Josip Almasi
226
h3. Docker and OpenVidu
227
228
OpenVidu voice/video chat server runs as docker image. This is only required for development of voice chat functions.
229
230 10 Josip Almasi
Local execution (development):
231 11 Josip Almasi
docker run -p 4443:4443 --rm -e OPENVIDU_SECRET=YOUR_SECRET -e DOMAIN_OR_PUBLIC_IP=YOUR_IP openvidu/openvidu-server-kms:2.17.0
232 10 Josip Almasi
233
Running on server:
234 1 Josip Almasi
https://docs.openvidu.io/en/2.17.0/deployment/deploying-on-premises/
235 11 Josip Almasi
236
Then either modify openvidu.publicurl and openvidu.secret in application.properties, or run server.jar with -Dopenvidu.publicurl=YOUR_URL and -Dopenvidu.secret=YOUR_SECRET
237 25 Josip Almasi
238
h1. Software Architecture
239 26 Josip Almasi
240
!https://redmine.vrspace.org/attachments/download/15/vrspace-diagram.png!
241
242
h2. Client-Server Communication
243
244 31 Josip Almasi
Clients communicate with server by sending JSON messages over "WebSockets":https://en.wikipedia.org/wiki/WebSocket. Reference javascript implementation of client communication layer is in "VRSpace.js":https://www.vrspace.org/docs/jsdoc/VRSpace.html.
245 26 Josip Almasi
246
General approach to communication is rather obscure Half-Object pattern: server-side and client-side object have same properties, but different implementations.
247
Whenever an object's property changes in (any) client's address space, it's transmitted to the server, that broadcasts it to all clients currently 'watching' the object.
248
249
Whenever a client wants to perform any change to any object in the space, it has to go through the VRSpace server.
250
Clients may or may not communicate directly, but this is out of the scope of VRSpace server.
251
252
h2. Server Responsibilities
253
254
Sole responsibility of VRSpace server is management of 3D space: persisting space objects, tracking their properties, processing and distributing events from/to objects.
255 27 Josip Almasi
Whenever we talk about objects, that includes clients, i.e. users - a client is a special case of an object.
256
The server does not even handle the authentication - it is assumed to be responsibility of web app serving the space.
257
3D geometry is also not in server's scope, it's just another property of an object (mesh).
258
259
h2. Server design
260
261
Key concepts here are Active Objects, Actor model, and Live distributed object.
262
263 53 Josip Almasi
"VRObject":https://github.com/jalmasi/vrspace/blob/master/server/src/main/java/org/vrspace/server/obj/VRObject.java is a basic shared object, with some basic properties like position and rotation, and of course, mesh. It essentially a "Business object":https://en.wikipedia.org/wiki/Business_object acting as a "Live distributed object":https://en.wikipedia.org/wiki/Live_distributed_object.
264 27 Josip Almasi
265 28 Josip Almasi
"Client":https://github.com/jalmasi/vrspace/blob/master/server/src/main/java/org/vrspace/server/obj/Client.java extends VRObject, and adds capabilities to communicate over web sockets, and listen to changes to other objects. Typically, a client represents a remote user, but it can also represent a robot connected over a web socket, or be a base class for a server-side robot.
266
A Client can be thought of as "Active Object":https://en.wikipedia.org/wiki/Active_object or an "Actor":https://en.wikipedia.org/wiki/Actor_model, 
267 27 Josip Almasi
268
Server relies on Spring Boot and embedded Tomcat to handle all I/O and threads.
269 29 Josip Almasi
270 55 Josip Almasi
Design does not require websockets in particular, in fact some reliable multicast protocol would surely fit better. Websockets work in web browsers.
271
272 33 Josip Almasi
h3. Client
273 29 Josip Almasi
274 30 Josip Almasi
Each "Client":https://github.com/jalmasi/vrspace/blob/master/server/src/main/java/org/vrspace/server/obj/Client.java has it's own "Scene":https://github.com/jalmasi/vrspace/blob/master/server/src/main/java/org/vrspace/server/core/Scene.java that tracks all shared objects - including other clients - visible by the client. The scene is initially populated once the client logs in to the server, and starts the session. Scene is refreshed periodically, after a movement, or explicitly.
275 29 Josip Almasi
276
Scene maintains the event model, by adding the Client as listener to all other active objects (usually other users) in the scene.
277 1 Josip Almasi
278 30 Josip Almasi
Client simply notifies it's own listeners on any changes to any of it's own properties. As a listener, it propagates any observed change on any other object over the network, to the user.
279
280
Client has just a couple of persistent properties, like position, rotation and name. The name must be unique.
281
All other properties are transient.
282
283 33 Josip Almasi
"ClientFactory":https://github.com/jalmasi/vrspace/blob/master/server/src/main/java/org/vrspace/server/core/ClientFactory.java allows for customization of Client class and instances.
284 1 Josip Almasi
285 33 Josip Almasi
h3. Events and messages
286
287 30 Josip Almasi
Typically events exchanged are changes to properties of active objects, e.g. user moves around, changing own position and rotation. However, an object may emit any event, and the event gets propagated to all listeners.
288 1 Josip Almasi
This is to simplify client development: simply emit any custom event you want.
289 32 Josip Almasi
All distributed events are encapsulated in "VREvent":https://github.com/jalmasi/vrspace/blob/master/server/src/main/java/org/vrspace/server/dto/VREvent.java class.
290
291
However, there are other types of messages that are not distributed to other clients: commands and their return values, and errors.
292 1 Josip Almasi
Client will typically execute at least one command during the session - "Session":https://github.com/jalmasi/vrspace/blob/master/server/src/main/java/org/vrspace/server/dto/Session.java start. It will not receive any messages before that.
293
Should any server-side exception occur during the session, errors are sent to the client as simple JSON maps.
294 33 Josip Almasi
295
"WorldManager":https://github.com/jalmasi/vrspace/blob/master/server/src/main/java/org/vrspace/server/core/WorldManager.java manages clients and event distribution between them.
296
297
h3. Worlds
298
299
A server can host many worlds, i.e. shared spaces. A world contains users and other objects that are shared only within the world. It can be thought of as a chatroom, but mind the difference: being in the same world does not mean that users can see and talk to each other.
300
Client can enter another world by issuing "Enter":https://github.com/jalmasi/vrspace/blob/master/server/src/main/java/org/vrspace/server/dto/Enter.java command.
301
302 35 Josip Almasi
h3. Ownership and privacy
303
304
A class can be annotated as Owned, and all of instances automatically become owned as they are created. An owned object does not receive events from anyone by owner(s). A Client is owned, and nobody but himself can change his name.
305
On the other hand, a generic VRObject is public, and receives events from anyone. Like a door, anybody can open and close it. But even public objects can have some properties annotated as Owned, that can't be change by anyone but owner.
306
Fields of a class can be annotated as Private, and their contents will never be published.
307
308
"Dispatcher":https://github.com/jalmasi/vrspace/blob/master/server/src/main/java/org/vrspace/server/core/Dispatcher.java takes care of it before property changes are applied, and before they are published to listeners.
309
310 33 Josip Almasi
h3. Package structure
311
312
Package "org.vrspace.server":https://github.com/jalmasi/vrspace/tree/master/server/src/main/java/org/vrspace/server contains only main application class. Under it,
313
- config package contains server configuration classes that are executed only on server statup
314
- core is the core of the server
315 34 Josip Almasi
- dto is misnomer that stands Data Transfer Objects, though this package contains all objects that are not shared nor persisted
316 33 Josip Almasi
- obj contains persistent objects, most importantly Client and VRObject
317
- types are custom types used elsewhere, be it interfaces or annotations
318
- web is a primitive admin interface, disabled by default
319 54 Josip Almasi
- api contains REST controllers