rotorsForcesRTD: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "\| *((\[\[[a-zA-Z0-9_ |()]+\]\],? ?)+) * \}\}" to "|seealso= $1 }}") |
Lou Montana (talk | contribs) m (Text replacement - "<dl class="command_description"> <dd class="notedate">" to "<dl class="command_description"> <dt></dt> <dd class="notedate">") |
||
| Line 27: | Line 27: | ||
<!-- CONTINUE Notes --> | <!-- CONTINUE Notes --> | ||
<dl class="command_description"> | <dl class="command_description"> | ||
<dt></dt> | |||
<dd class="notedate">Posted on November 4, 2014 - 02:00 (UTC)</dd> | <dd class="notedate">Posted on November 4, 2014 - 02:00 (UTC)</dd> | ||
<dt class="note">[[User:Benargee|Benargee]]</dt> | <dt class="note">[[User:Benargee|Benargee]]</dt> | ||
Revision as of 13:38, 5 April 2021
Description
- Description:
- Description needed
- Groups:
- RTD
Syntax
- Syntax:
- Syntax needed
- Parameters:
- RTD_helicopter: Object
- Return Value:
- Return value needed
Examples
- Example 1:
_rotorForces = rotorsForcesRTD _taru// Returns [[-465.981,351.941,45960.5],[-469.079,397.451,46933.3]]
Additional Information
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note
- Posted on November 4, 2014 - 02:00 (UTC)
- Benargee
- There is no official information I can find on what these values mean. According to my testing on the Mi-290 Taru, here is what I have come up with:
[[rotor 1 roll +right/-left, rotor 1 pitch +down/-up, rotor 1 collective +up/-down], [rotor 2 roll +right/-left,rotor 2 pitch +down/-up,rotor 2 collective +up/-down]]When yawing left and right, rotor 1 and 2 collective differ from each other. This is normal behaviour with coaxial rotors. Yawing right increase rotor 1 collective and decreases rotor 2 collective. Yawing left does the opposite. Rotor 1 in this example seems to be the bottom rotor.