Differences

This shows you the differences between two versions of the page.

--- visual3d:documentation:kinematics_and_kinetics:external_forces:force_structures [2025/09/12 18:59] – [Pipeline Command] wikisysop
+++ visual3d:documentation:kinematics_and_kinetics:external_forces:force_structures [2025/09/12 19:04] (current) – [Structure consisting of 2 force platforms and 1 surface] wikisysop
@@ Line 64: / Line 64: @@
 /USE_FORCES_FOR_KINETICS= are forces kinematics only?
 /COMBINE_INPUT_FORCES= combine all forces for each structure into a single force
-! /[[Visual3D:Documentation:Pipeline:File_Commands:Update_C3D_File|Update_C3D_File]]=FALSE
+! /Update_C3D_File=FALSE
 ;
 </code>
@@ Line 114: / Line 114: @@
 **COP_1**, **FORCE_1** and **FREEMOMENT_1**
 {{:ForceStructureDataTree.jpg}}
@@ Line 124: / Line 125: @@
 The following dialog creates a force structure that is comprised of 1 surface spanning 2 force platforms.
-{{:ForceStructureDig1x2.jpg}}
+{{:ForceStructureDlg1x2.jpg}}
 The user has the option to treat each force independently, which means that each force FP1 and FP2 could be assigned to the same segment.
@@ Line 145: / Line 146: @@
   * Transform these values back into the laboratory coordinate system
-If there are two force platforms, the resulting signal will appear in the data tree as
+If there are two force platforms, the resulting signal will appear in the data tree as:
 **FS1_1** and **FS1_2**
 This is interpreted as Force Structure 1 contribution from Force platform 1, and Force Structure 1contribution from force platform 2.
-\\
+If, for example, instead of FP1 and FP2, there was FP1 and FP3, the signals would be:
-If, for example, instead of FP1 and FP2, there was FP1 and FP3, the signals would be
 **FS1_1** and **FS1_3**
-\\
-if the option to combine all input forces is selected, there will be one resulting signal
+If the option to combine all input forces is selected, there will be one resulting signal:
 **FS1_1**