By default, when you place victims in a location, they are set to be visible when that location is visited. By default, you can click/tap on the victim during a scenario to remove/hide the victim. Once a victim is hidden, you can double-click/tap on where the victim was, and the victim will reappear.
You can specify optionally not to show the victim until you double-click/tap on the victim. One use for this is to place victims in various locations, and depending on how you want to run the exercise, you can reveal/enable the set of victims you want. In the snapshot above, the ‘Visible to start’ property is set to NO, which means ‘do not show the victim until double-clicked/tapped on.’
If you are placing several victims in the same location, you may want to shrink the ‘Tap target scale’, which controls the area on which you have to tap/click to show/hide the victim. Otherwise, one selection/tap region for a victim may obscure the selection/tap region for another.
Here are a few possible scenarios you might want to link victim pictures:
- You have a victim in the window on your Side A location, and you also can see that victim (when present) from an A-B view. If you clear the victim from Side A, you also want to clear the victim picture from your A-B view, though they are separate locations.
- You have a location to represent Side A with incipient smoke conditions, and you have a different location to represent Side A with freeburn conditions. On Side A Incipient and on Side A Freeburn, you have placed a victim at the window. If the user clears the victim during the incipient condition, you do not want to show the victim if you switch to the freeburn condition.
- You want to make a victim move around the scenario over time. For example, the victim might show up at a window for a period of time, then withdraw into the room, then show up inside a room in a standing position, and finally, after some period of time, collapse on the floor in that room.
In each scenario, you must place different victim pictures in each location. In scenario #3, you would have two victim pictures in the interior room, one for a victim in a standing position, and the other in a collapsed position on the floor. By default, the pictures act independently, which means each picture is assigned a “variable” that keeps track of its visibility status, i.e., shown or not shown.
The synchronization variable (ManSync1) for the selected victim,
and all possible variables in the scenario (WomanSync1 and WomanSync2).
When you choose the ‘Sync variable’ property, seen above, you are shown by default the variable name for the selected victim, and in the dropdown menu, you can select any of the variables defined in the scenario so far.
If you want to link two pictures together so that clicking/tapping on a victim clears the victim in each picture, you must select a common sync variable. For example, from above, if I wanted to link the presence of the man with the presence of the victim associated with WomanSync1 or WomanSync2, I would select the appropriate sync variable. At this point, turning on or off either picture would be synchronized with the other picture.
With respect to the scenarios defined above, in Scenario #1, when you place each man victim, for example, SimsUshare automatically assigns one victim to ManSync1 and one to ManSync2. To link the victims, you would set the sync variable of the two pictures to the same value, perhaps ManSync1. Once the scenario is saved (automatically), SimsUshare cleans up any sync variables that are not attached to victims, so it will remove ManSync2, since it is not needed anymore.
Any number of victims can be synced with a sync variable, not merely two. Therefore, in Scenario #3 (above), when you link all the pictures to a common sync variable, if the user clears any of the victims, then all of the pictures will obey the proper visibility status (shown or hidden).