... | ... | @@ -68,7 +68,7 @@ Notice that there is one instance of *NomadPositions* for each Nomad server (one |
|
|
|
|
|
#### Current connection with the Nomad server instances
|
|
|
|
|
|
Currently, the Nomad 3D Server is configured with one Nomad endpoint (in config.json).
|
|
|
Currently, the Nomad 3D server is configured with one Nomad endpoint (in config.json).
|
|
|
The Nomad Position addon maintains a list of *NomadPositions* (small application that forwards the positions) instances managed by Cameo.
|
|
|
There is one instance per Nomad server instance (one real and many simulated).
|
|
|
|
... | ... | @@ -86,6 +86,9 @@ Then the client is sending the *ResetNomadPosition* request with the Nomad id (i |
|
|
On the client, a loop is constantly updating the positions.
|
|
|
At each iteration, the client is sending the *GetPositionsRequest* request with the Nomad id, then the addon contacts the associated requester to the *NomadPositions* instance.
|
|
|
|
|
|
#### Future connection with the virtual Nomad server instances
|
|
|
|
|
|
The connection required with the virtual Nomad server instances is not decided. If the Nomad server are running on VISA, then each one will have a dynamic endpoint that must be passed to the Nomad 3D server. However if they are all running on the same endpoint (VM or physical machine), only the Cameo id is enough to be passed.
|
|
|
|
|
|
## Environment map
|
|
|
|
... | ... | |