ctrlSetFade: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "\[\[Category:[ _]?Scripting[ _]Commands[ _]Arma[ _]2(\|.*)\]\]" to "{{GameCategory|arma2|Scripting Commands}}")
m (Text replacement - "\[\[Category:[ _]?Scripting[ _]Commands[ _]Take[ _]On[ _]Helicopters(\|.*)?\]\]" to "{{GameCategory|tkoh|Scripting Commands}}")
Line 42: Line 42:
{{GameCategory|arma2|Scripting Commands}}
{{GameCategory|arma2|Scripting Commands}}
{{GameCategory|arma3|Scripting Commands}}
{{GameCategory|arma3|Scripting Commands}}
[[Category:Scripting Commands Take On Helicopters|{{uc:{{PAGENAME}}}}]]
{{GameCategory|tkoh|Scripting Commands}}


<!-- CONTINUE Notes -->
<!-- CONTINUE Notes -->

Revision as of 22:23, 8 January 2021

Hover & click on the images for description

Description

Description:
Sets wanted transparency for control animation. Requires ctrlCommit to commit changes. To hide or show a control instantly, use ctrlShow.
Groups:
GUI Control

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 seconds This phenomenon probably occurs because of engine time simulation disruption caused by performance damage.