Troubleshooting

You can increase the size of the usable area of SmartSpace Config by hiding the list of tabs on the left-hand side of the application.

To hide the tabs, click the SmartSpace icon at the top-left of the SmartSpace Config application window and choose Hide workflow.

You can display the tabs again by clicking the SmartSpace icon and choosing Show workflow.

Sometimes it is useful to see more than one workspace in SmartSpace Config at the same time, for example so you can move objects in the object viewer in OBJECT PLACEMENT and see resulting spatial property rows added in the object browser in TYPES / OBJECTS. To enable multiple windows, click the SmartSpace icon at the top-left of the SmartSpace Config application window and choose Floating windows. The current workspace immediately gains a title bar with a pin icon at the far right:

• Click the pin to unpin a docked window. (The pin is replaced with a cross: )

  You can now drag the window out of the SmartSpace Config window to position it elsewhere on your desktop and open additional windows.

• Click the cross on a floating window to return it to the application window.

SmartSpace displays error messages during cell configuration if cells break the following rules for cell hierarchies:

• All Geometry Cells are contained by the Site Cell

• A Location Cell is contained by a single Geometry Cell

• Location Cells do not overlap

If errors are identified, you can double-click on their descriptions to correct them. You may see one or more of the following messages:

• The site cell does not contain all the geometry cells
  Double-click this message and you will be asked if you want to Extend the site cell to contain all geometry cells? You can either choose Yes and allow SmartSpace to extend the site cell so that it contains all the geometry cells or choose No to edit the extent(s) of the geometry cell(s) yourself.
• The extent of location cell is not contained by the extent of geometry cell
  Double-click this message and you will be asked if you want to Change the extent of geometry cell to cover location cell? You can either choose Yes and allow SmartSpace to extend the geometry cell so that it contains the location cell or choose No to edit the extent of the location cell yourself.
• The extent of location cell overlaps location cell
  Double-click this message and you will be taken back to a dialog where you can edit the extent of the first location cell in the message.

It is possible for the site visualization to become quite complex with multiple layers of objects and representations. In this situation, trying to select a specific background representation using your mouse in order to remove it from the scene may not be straightforward.

To this end, it is important to understand that when you drop a background representation into the scene, SmartSpace actually creates a hidden system level object to which the representation gets attached. This means that although your background representations are not attached to any objects in your defined data model, there is in fact a hidden “background object” used to host the rep and place it in the scene.

It is therefore possible, like with all other type-to-rep and object-to-rep assignments that are discussed in Adding a representation to a type, to delete those assignments from the dataset. In deleting an assignment in this way, you are also completely removing it from the world model (if it has been placed there).

To delete a hard-to-reach background rep:

1. Go to the Model assignment workspace.
2. Select the “Representations Assigned to Types” dropdown list. Browse up the list to the Object Type called Background objects and select.
3. This will list all the “hidden” background objects. To delete one, select the row in the table and use the Delete key on your keyboard.

If you find that the default zoom on the maps in SmartSpace Config is further out than expected, this is likely to be because of a 2D rep you have scaled. When you are scaling a 2D rep, you must make sure you scale the z axis size to a similar scale to the x and y axes, otherwise the default zoom in the SmartSpace Config maps may be further out than expected. For example, if you have a rep with (Scale X, Scale Y, Scale Z) set to (0.05, 0.05, 1.0), you will find that the map default zoom gives a lot of space around the rep. This is automatically done correctly if you scale the image using reference points (described in Resizing a representation based on the distance between two points) or if you set the image's overall size. But if you directly set the scale, it is up to you to ensure that the relative scales are reasonable.

In the object browser, when one or more objects on the map are positioned outside of location cell extents, SmartSpace displays. an error message. If your map is complex, it may be difficult to identify which objects the error refers to. You can limit the displayed objects to those which are outside location cell extents by choosing <Objects outside cells> from the objects list.

From version 3.6, SmartSpace Config has been updated to OpenSceneGraph 3.6.5, giving some improvements to the appearance of the 3D map. OpenSceneGraph is built on OpenGL 1.2 to 4.6, and chooses features at runtime depending on what is available, so as a minimum requires OpenGL 1.2. This may not be fully supported by some graphics drivers, especially when running via remote desktop. If you encounter problems when using a task that displays a 3D visualization, use the solutions provided below.

1. If possible, don't use remote desktop—the Ubisense software architecture is specifically designed to run clients on different machines.

2. If you must use remote desktop, and the remote machine has a graphics card, try creating a batch file to start the application in the console session.

   Example batch file

   The batch file should contain commands similar to:

   for /f "tokens=3" %%g in ('quser') do set session=%%g
   echo "Starting SmartSpace Config in session " %session% " using physical console"
   tscon %session% /dest:console
   start "SSC" "C:\Program Files (x86)\Ubisense 3\bin\UbisenseApplicationUpdater" "SmartSpace Config"

   Note: You need to run the batch file as administrator for the tscon command to work.

3. For other problems with 3D maps (not involving remote desktop), try to identify any broken or overly-complex representation models, and don't use them if they prevent SmartSpace Config working correctly or at all.

4. If all else fails, you can download the opengl32.dlls from the Mesa 3D software rendering library maintained by Federico Dossena.

   Note: You will need to use 7-zip to unpack the downloaded files.

   1. Ensure you have the most recent version of Ubisense Application Manager installed.

   2. Create a directory in the Ubisense installation folder (normally C:\Program Files (x86)\Ubisense 3\bin) and name it opengl.

   3. Download and unzip the latest version of the 32-bit version of Mesa3D and copy opengl32.dll into the opengl directory.

   4. Create another directory in the Ubisense installation folder and name it opengl_64.

   5. Download and unzip the latest version of the 64-bit version of Mesa3D and copy opengl32.dll into the opengl_64 directory.

   6. The application updater will synchronize the DLLs with the working directories of your applications.

If you don’t see a representation for your object, you need to ensure that you have assigned a <default> representation for your object type. See Adding a representation to a type

When creating path points, the path point generation code places the path point object instances at exactly the same position on the z axis as their path. If the path point type has a 2D rep with a z offset of zero, then the point is exactly coplanar with the path section ribbon and this might lead to you seeing rendering artifacts.

It can also make it difficult to select a path point: sometimes clicking the point might pick it, or it might pick the path section instead.

To make path points easier to select, you can set a non-zero z origin offset (e.g. -0.5) on the representation used for Path Point (the base type used when generating path points). Any path point types you create will inherit this rep and its default offset.

For example, if you decide to use a rep called circle, a simple 2D circle, for your path points, when you import the image in MODEL IMPORT, in addition to any scaling you apply, also set the z origin:

Assign this rep to the Path Point type in MODEL ASSIGNMENT and then any path points generated using this rep, will "float" above the path:

This is the expected behavior.

Notifications are generated when you use the Notify action in the Business rules engine.

Notify accepts several different inputs:

• Named user
• Email address
• Group name

For the first two, notify generates a web map popup or an email notification respectively. It’s obvious what is being requested at the rules engine level because of the type of input.

Groups, however, could contain both users and email addresses, so you have to tell the system if you want one or both (maps notifications and emails) explicitly. Otherwise you run the risk of sending alert emails to everyone in an active directory group when all you wanted was popups on the web map.

• Check that you have a representation mode assigned
• Check that you have added a representation mode to the search
• Check that objects have a location
• Check that objects are within a location cell
• If there is a dropdown for you to choose parameters, ensure objects have one of the parameters assigned to them

Some care should be taken when adding labels to SVGs due to how SmartSpace handles their display on the web map.

When SVGs with labels are used as representations, SmartSpace attempts to keep the text the right way up when it displays objects using this rep on the web map. This may mean that the rep is rotated differently to the associated object. For example when an object with an SVG with a label is rotated by 180 degrees, the rep gets rotated by 360 degrees to prevent label text displaying upside down. This flipping of the rep's orientation may cause unexpected results with asymmetric reps.

If reps of this type are used as background maps, this behavior may be especially confusing for users as part of their frame of reference may suddenly rotate. Because of this, it is recommended not to add text labels in SVGs of background maps. Instead, if labels are required, create them as separate background objects relative to the background map.

See Adding a label to the representation of an object for information on adding labels to SVGs.

Sometimes as you zoom out in the web map, representations become too small to be easily seen. To prevent this you can limit the zoom size for a representation. In the definition of a search in the WEB SEARCHES workspace, you can check LIMIT ZOOM for the rep. This sets the minimum size of the rep to 10 px per meter. For example, if the rep is loaded with a width of 4 m, it will have a minimum width of 40 px in the map as the map zooms out.