---
title: "Known issues in Vicon Shogun Live"
canonical: "https://help.vicon.com/space/ShogunLive115/276039878/Known%20issues%20in%20Vicon%20Shogun%20Live"
format: markdown
---
The following issues are known to exist in Vicon Shogun Live 1.15: 

> Macro (scroll-tablelayout)

| **Description** | **Workaround** |
| --- | --- |
| If you disconnect a Teledyne FLIR Blackfly S camera and then reconnect it, the camera does not reconnect to Shogun. The same issue occurs if you reboot the cameras. | To reconnect (or reboot) the cameras, make sure all the cameras are reconnected and then restart the software. |
| Joint centers in the foot are sometimes inaccurately positioned during subject calibration. | Auto-Skeleton guarantees more accurately positioned feet and can be used to quickly generate a new skeleton, which can then be used in Shogun Live - [Video tutorial on YouTube](https://www.youtube.com/watch?v=j1-_MGfP_zE). |
| Objects that have the property **Track With Object Tracker** enabled do not generate markers in the DataStream. | None at present. To be addressed. |
| The viewport can be slow to respond, for example, if a video camera is unplugged. | Change the processing level and the viewport will reboot. |
| RSS Processors and RSS Queues maximum values can be set too high. | The maximum number of RSS Processors and RSS Queues needs to be set 8. (8 used to be the maximum however the latest network cards can go considerably higher.) |
| In systems with large numbers of cameras, a high number of dropped frames occurs. | Do one of the following:<br>- Use Shogun's multi-machine feature (see [Run Shogun processing on multiple machines](https://vicon-help.atlassian.net/wiki/spaces/ShogunLive115/pages/276041886) in *Getting more from Vicon Shogun Live*).
- Use the **Process in Realtime** option in Shogun Live (on the **System** tab, select the required camera(s) and in the **Capture** properties below, clear the **Process in Realtime** option). You can use this option to exclude cameras from reconstruction, while keeping them in the captured X2D and 2D workspace.  
  
**Important:** Remember that if you use this feature to exclude cameras, their data will not be present in the resulting MCP file. To include the data from excluded cameras, instead reprocess from the X2D file. |