The workspace setting can be accessed by pressing the rightmost gear icon in the toolbar.
This brings up the following panel. There are 4 different tabs (Server, Scene, Gateway and Logs), the settings for each tab are explained below.
In this tab, all settings related to the current server can be configured.
Displays the version of the connected server.
Displays the domain name of the server.
Displays how much time is left before the server shuts down (online servers only).
The status is 'Connected' when the app is able to communicate with the server.
A list of all users currently logged in on the server.
This setting specifies how frequently the collision visualization is updated when the function is active.
Displays the update frequency of the physics engine.
Displays how long the emulation has been running. It's the same as the server time shown in the toolbar, but with higher resolution.
Displays how many nodes are currently loaded in the workspace.
A higher value means that all constraints and collisions are calculated more accurately.
Display physics engine joints and constraints.
Debug Contact Points
Display physics engine contact points. The contact points are visualized as yellow lines to show where collision geometries are touching.
Default is 0.005
Server communication interval in seconds to send UPDATE to the gateway.
If CFM is set to zero (which is the default value), the constraint will be hard. If CFM is set to a positive value, it will be possible to violate the constraint by "pushing on it" (for example, for contact constraints by forcing the two contacting objects together). In other words the constraint will be soft, and the softness will increase as CFM increases. What is actually happening here is that the constraint is allowed to be violated by an amount proportional to CFM times the restoring force that is needed to enforce the constraint. Note that setting CFM to a negative value can have undesirable bad effects, such as instability. Don't do it.
The ERP specifies what proportion of the joint error will be fixed during the next simulation step. If ERP=0 then no correcting force is applied and the bodies will eventually drift apart as the simulation proceeds. If ERP=1 then the simulation will attempt to fix all joint error during the next time step. However, setting ERP=1 is not recommended, as the joint error will not be completely fixed due to various internal approximations. A value of ERP=0.1 to 0.8 is recommended (0.2 is the default).
Float point resolution for values coming from the physics engine. Value betweem 3-6. Default 3 (1 mm resolution).
The time relation can be used to slow down or speed up the emulation time. The default value is 1.
In this tab, all settings related to the scene can be configured.
Determines whether shadows are drawn or not. Having shadows active can have a big impact on performance. It is turned off by default.
Toggles the ambient light on or off.
Determines the color of the ambient light.
Determines the intensity of the ambient light.
Toggles the point light on or off.
Determines the color of the point light
Determines the intensity of the point light.
Determines the position of the point light
Toggles the ground plane on or off.
Length of the ground planes sides in metres.
Determines how many squares are distributed along each side of the ground plane. If this value is equal to the ground size parameter, every square will be one square metre.
Determines the color of the ground plane.
In this tab, all settings related to the gateway can be configured.
Displays the version of the installed gateway.
Displays the address and connection state of the gateway.
Sets the URL of the gateway.
This tab displays log messages sent from the server. Black text is used for INFO messages, while red text is used for ERROR messages. Errors from behavior scripts in components will show up in red text here.
This button clears all messages from the log.