improve troubleshot section for ofs integration

Author: arch

docs/app/docs/user-guide/ofs-integration.md

@@ -44,3 +44,7 @@ In some cases OFS does not set the path to the video file within the lua script
 If a tacker does not find the selected feature in the next frame, the tracking process stops. If more than 120 frames have already been tracked, a window appears to select the minimum and maximum value in which the reason for the abort is displayed with e.g. `Info: Tracker Woman Lost`.
 
 If less than 120 frames have been processed, a message box should pop up with the message `Tracking time insufficient`. In this case, no output is generated because there is not enough data for the algorithm to work with.
+
+### Tracking stops very often
+
+The selection of the tracking feature is tricky and requires some practice and experience. For a good tracking result, unique features in the video should be selected near the desired tacking position.

docs/app/site/index.html

@@ -204,5 +204,5 @@ <h4 class="modal-title" id="keyboardModalLabel">Keyboard Shortcuts</h4>
 
 <!--
 MkDocs version : 1.1.2
-Build Date UTC : 2021-06-27 07:58:17.009150+00:00
+Build Date UTC : 2021-06-27 08:31:10.353033+00:00
 -->

docs/app/site/search/search_index.json

@@ -143,8 +143,10 @@ <h3 id="noting-happens-when-i-press-the-shortcut-for-the-funscript-generator">No
 <h3 id="when-calling-the-generator-only-a-message-box-is-displayed-with-the-message-video-file-was-not-specified">When calling the generator, only a message box is displayed with the message: "Video file was not specified!"</h3>
 <p>In some cases OFS does not set the path to the video file within the lua script correctly (the variable <code>VideoFilePath</code> is empty). Mostly it helps to save the current project and/or create a new project. Then the variable should be set by OFS and the generator should work.</p>
 <h3 id="tracking-stops-automatically">Tracking stops automatically</h3>
-<p>If a tacker does not find the selected feature in the next frame, the tracing process stops. If more than 120 frames have already been tracked, a window appears to select the minimum and maximum value in which the reason for the abort is displayed with e.g. <code>Info: Tracker Woman Lost</code>.</p>
-<p>If less than 120 frames have been processed, a message box should pop up with the message <code>Tracking time insufficient</code>. In this case, no output is generated because there is not enough data for the algorithm to work with.</p></div>
+<p>If a tacker does not find the selected feature in the next frame, the tracking process stops. If more than 120 frames have already been tracked, a window appears to select the minimum and maximum value in which the reason for the abort is displayed with e.g. <code>Info: Tracker Woman Lost</code>.</p>
+<p>If less than 120 frames have been processed, a message box should pop up with the message <code>Tracking time insufficient</code>. In this case, no output is generated because there is not enough data for the algorithm to work with.</p>
+<h3 id="tracking-stops-very-often">Tracking stops very often</h3>
+<p>The selection of the tracking feature is tricky and requires some practice and experience. For a good tracking result, unique features in the video should be selected near the desired tacking position.</p></div>
             </div>
         </div>