---
title: "Addressed issues in Vicon Shogun 1.12"
canonical: "https://help.vicon.com/space/Shogun112/31234781/Addressed%20issues%20in%20Vicon%20Shogun%201.12"
format: markdown
---
Vicon Shogun 1.12 resolves a number of issues, including the selection listed here.

> Macro (scroll-only)
> 
> > Macro (toc)

## Issues addressed in Shogun Live 1.12

- Issues with the Windows Installer package have been resolved and running *Vicon_Shogun_Setup.exe* installs Shogun as expected.
- The FLIR and Vicon video camera settings are taken into account when compressing MOV files. This means gain and gamma are not ignored during compression.
- Drop-out issues during high CPU usage have been resolved so the camera calibrations remain in the stream and cameras do not disappear from the 3D view.
- Inconsistencies using a custom L-Frame to set the origin have been fixed. When you set the origin it will now match the VSK coordinates.
- Similar set origin inconsistencies have been fixed when creating a prop. If you select “Use For Camera Calibration”, the prop is placed at the origin of the volume with the correct orientation.
- The Graph view for large or long captures is quicker to load.

## Issues addressed in Shogun Post 1.12

- Retargeting root stiffness and joint covariance issues have been resolved. Smooth root motions in Shogun Live are also consistent in Shogun Post.
- After loading "calibration only" from an .mcp file the calibration imports successfully and the interface responds normally.
- Shogun Post now closes properly if there are two or more floating panels open.
- Issues with the option AlwaysCreateNew in the HSL script LoadFile have been resolved.
- Previously, the getFileLocation <span style="color: #1d1c1d">command previously failed to work if the path did not exist on disk. With this release, the issue has been resolved.</span>
- In **General** > **Preferences**, if you create a custom Prop Meshes directory, the file path to the directory is remembered when you close and re-open Shogun Post.
- When using AutoSkeleton, if you disable the **Pose Fingers** option, this now respected and the constraints on the fingers are not changed by AutoSkeleton