User Interface Details
The following is a brief overview and additional images of the user interface within LupsMON.
When a LupsMON client connects, they are presented with a series of 3D stars. Each star represents
a real world UPS unit. The 3D stars are positioned together above various floating platforms,
which help logically group the UPS units as to represent their real world geographical locations.
The 3D stars may rotate, bounce, change colour or change size depending on a number of state variables at exist
on each UPS unit. (Such as output load, battery time remaining, current status and if any alarms are present.)
- Floating platforms are used to logically group entities
- Different platforms represent different real world geographic locations
(Note: The 'inspector tool' is only one of a number of techniques supported by L3DGEWorld 2.2 for interacting with
in-world entities. LupsMON restricts you to only use the gun that allows inspection of in-world entity state.
Other systems based on L3DGEWorld 2.2 may utilise different types of 'guns' to initiate additional in-world interactions.)
Multiple users at the same time
LupsMON allows more than one user to exist within the virtual world at the same time.
Other users will perceive you as a humanoid character flying around the virtual world,
armed with an electric beam weapon. You will perceive them in the same manner.
Figure 4a:
Viewing another user in-world
|
Getting Help
The map shipped with LupsMON allows users to quickly reference the meaning of the different behaviours of entities. This is
done by flying into the 'help room'. When a user passes through the gateway, a user is transported into another area. This help room
has a number of 'road signs' explaining what each behaviour represents on the UPS units. This allows users to quickly determine
the meaning of the different behaviours that exist on each of the entities.
Figure 5a:
The gateway, when a user flies through the center,
they will be transported to the help room
|
Figure 5b:
Vewing a sign explaining the
different entity behaviours
|
