ctrlSetFade: Difference between revisions
Jump to navigation
Jump to search
Dr Eyeball (talk | contribs) m (see also) |
(framerate dependancy) |
||
| Line 54: | Line 54: | ||
_ctrl ctrlSetFade 0; // control is fully visible | _ctrl ctrlSetFade 0; // control is fully visible | ||
</code> | </code> | ||
</dd> | |||
</dl> | |||
<dl class="command_description"> | |||
<dd class="notedate">Posted on August 28, 2017 - 11:33 (UTC)</dd> | |||
<dt class="note">[[User:Demellion|Demellion]]</dt> | |||
<dd class="note"> | |||
The resulting fade speed seems like is not exactly what [[ctrlCommit]] commands it to be, as is dependant on your current framerate. Example: | |||
<code>_ctrl ctrlSetFade 0.5; | |||
_ctrl ctrlCommit 1; | |||
</code> | |||
Will actually result in: | |||
<code>'''[60 FPS and higher]''' = ~1.0 seconds | |||
'''[30 FPS and around]''' = ~1.2 seconds | |||
'''[10 FPS and anything lower]''' = ~5-10 seconds | |||
</code> | |||
This phenomenon probably occurs because of engine time simulation disruption caused by performance damage. | |||
</dd> | </dd> | ||
</dl> | </dl> | ||
<!-- DISCONTINUE Notes --> | <!-- DISCONTINUE Notes --> | ||
Revision as of 11:03, 28 August 2017
Description
- Description:
- Sets wanted transparency for control animation. Requires ctrlCommit to commit changes.
- Groups:
- Uncategorised
Syntax
- Syntax:
- controlName ctrlSetFade fade
- Parameters:
- controlName: Control
- fade: Number
- Return Value:
- Nothing
Examples
- Example 1:
_control ctrlSetFade 1; _control ctrlCommit 5;
Additional Information
- See also:
- ctrlFadecutFadeOutctrlCommit
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
Notes
Bottom Section
- Posted on March 10, 2015 - 02:02 (UTC)
- Feint
-
This command sets the amount of fade. For example:
_ctrl ctrlSetFade 1; // hides the control
_ctrl ctrlSetFade 0.5; // control is 50% visible
_ctrl ctrlSetFade 0; // control is fully visible
- Posted on August 28, 2017 - 11:33 (UTC)
- Demellion
-
The resulting fade speed seems like is not exactly what ctrlCommit commands it to be, as is dependant on your current framerate. Example:
_ctrl ctrlSetFade 0.5; _ctrl ctrlCommit 1;Will actually result in:[60 FPS and higher] = ~1.0 seconds [30 FPS and around] = ~1.2 seconds [10 FPS and anything lower] = ~5-10 secondsThis phenomenon probably occurs because of engine time simulation disruption caused by performance damage.