hint: Difference between revisions
Jump to navigation
Jump to search
m (template:command argument fix) |
Lou Montana (talk | contribs) (Page cleanup) |
||
Line 1: | Line 1: | ||
{{Command|= | {{Command|Comments= | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| ofp | | | ofp |Game name= | ||
|1.00| | |1.00|Game version= | ||
|eff= local | | |||
|eff= local |Effects in MP= | |||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| Outputs a | | Outputs a hint message to the right of the screen (left of the screen in {{ofp}}) with a sound (except in {{arma}}). Use [[hintSilent]] for soundless hint. To split message in multiple lines either use [[Structured Text]], [[endl]] or <tt>\n</tt> (in lower case). |DESCRIPTION= | ||
|DESCRIPTION= | |||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| | | [[hint]] message |SYNTAX= | ||
|p1= | |p1= message: [[String]] or [[Structured Text]] - the message to display. |PARAMETER1= | ||
| [[Nothing]] |RETURNVALUE= | | [[Nothing]] |RETURNVALUE= | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
|x1= < | |x1= <code>{{codecomment|// outputs the following: | ||
// Press W to move forward. | |||
// Press S to move backwards.}} | |||
[[hint]] "Press W to move forward.\nPress S to move backwards."</code> |EXAMPLE1= | |||
|x2= <code>[[hint]] [[format]] ["Hello, %1!", [[name]] [[player]]];</code> |Example2= | |||
< | |x3= <code>[[hint]] [[str]] [[count]] [[allPlayers]]; | ||
[[sleep]] 10; | |||
[[hintSilent]] ""; {{codecomment|// hides the previous hint display}}</code> |Example3= | |||
____________________________________________________________________________________________ | |||
|pr= {{GVI|ofp|1.00}} {{GVI|arma|1.00}} {{GVI|arma2|1.00}} Hint messages that exceed the screen may lead to crashes.<br> | |||
{{GVI|arma3|1.00}} The game would not crash but suffer FPS drop / temporary freezing. |Problem= | |||
| [[hintC]], [[hintCadet]], [[hintSilent]], [[diag_log]] |SEEALSO= | | [[hintC]], [[hintCadet]], [[hintSilent]], [[diag_log]] |SEEALSO= | ||
}} | }} | ||
<h3 style="display:none">Notes</h3> | <h3 style="display:none">Notes</h3> | ||
<dl class="command_description"> | <dl class="command_description"> | ||
<dd class="notedate">Posted on October 20, 2014 - 19:27 (UTC)</dd> | <dd class="notedate">Posted on October 20, 2014 - 19:27 (UTC)</dd> | ||
<dt class="note">[[User:DreadedEntity|DreadedEntity]]</dt> | <dt class="note">[[User:DreadedEntity|DreadedEntity]]</dt> | ||
<dd class="note"> | <dd class="note"> | ||
Be careful when using hints to visualize the effects of commands using the Debug Console. Hint can accept an undefined variable and neither the error nor the hint is shown, the command simply fails. Also notice how the hint command should be | Be careful when using hints to visualize the effects of commands using the Debug Console. Hint can accept an undefined variable and neither the error nor the hint is shown, the command simply fails. Also notice how the hint command should be {{Inline code|[[hint]] [[str]] _i;}}: | ||
<code>for "_i" from 0 to 50 do | <code>[[for]] "_i" [[from]] 0 [[to]] 50 [[do]] { | ||
{ | [[hint]] _i; | ||
};</code> | };</code> | ||
'''tested in A3 1.32.127785'''<br><br>In a script, an "undefined variable" error will be shown as expected. | '''tested in A3 1.32.127785'''<br> | ||
<br> | |||
In a script, an "undefined variable" error will be shown as expected. | |||
</dd> | </dd> | ||
<dd class="notedate">Posted on October 21, 2014 - 23:07 (UTC)</dd> | <dd class="notedate">Posted on October 21, 2014 - 23:07 (UTC)</dd> | ||
<dt class="note">[[User:DreadedEntity|DreadedEntity]]</dt> | <dt class="note">[[User:DreadedEntity|DreadedEntity]]</dt> | ||
<dd class="note"> | <dd class="note"> | ||
Contrary to | Contrary to previous games, Arma 3 will happily display hints that far exceed screen space.<br> | ||
''' | However, as hints get longer, FPS suffers tremendously.<br> | ||
<code>hint str (([[nearestObjects]] [player, ["BUILDING"], 100]) - [player]); [] spawn { sleep 5; systemChat str diag_fps;}; | '''tested in Debug Console, A3 1.32.127785 with the following:''' | ||
hint str (([[nearestObjects]] [player, ["BUILDING"], 1000]) - [player]); [] spawn { sleep 5; systemChat str diag_fps;};</code> | <code>[[hint]] [[str]] (([[nearestObjects]] <nowiki>[</nowiki>[[player]], ["BUILDING"], 100]) - <nowiki>[</nowiki>[[player]]]); [] [[spawn]] { [[sleep]] 5; [[systemChat]] [[str]] [[diag_fps]]; }; | ||
Results were: '''59.7015''' and '''5.17297''', respectively. Drawing a hint even longer than this, such as [[nearestObjects]] with a radius of 10,000 or 100,000 reduces your FPS so much Arma 3 '''appears''' to crash, though it doesn't. | [[sleep]] 10; | ||
<br><br> | [[hint]] [[str]] (([[nearestObjects]] <nowiki>[</nowiki>[[player]], ["BUILDING"], 1000]) - <nowiki>[</nowiki>[[player]]]); [] [[spawn]] { [[sleep]] 5; [[systemChat]] [[str]] [[diag_fps]]; };</code> | ||
Unrelated: Hints will stay on screen for 30 seconds, then fade away over the course of 5 seconds. Tested with: | Results were: '''59.7015''' and '''5.17297''', respectively. Drawing a hint even longer than this, such as [[nearestObjects]] with a radius of 10,000 or 100,000 reduces your FPS so much Arma 3 '''appears''' to crash, though it doesn't.<br> | ||
<br> | |||
Unrelated: Hints will stay on screen for 30 seconds, then fade away over the course of 5 seconds. '''Tested with: A3 1.32.127785''' | |||
</dd> | </dd> | ||
<dd class="notedate">Posted on February 17, 2015 - 23:14 (UTC)</dd> | <dd class="notedate">Posted on February 17, 2015 - 23:14 (UTC)</dd> | ||
<dt class="note">[[User:DreadedEntity|DreadedEntity]]</dt> | <dt class="note">[[User:DreadedEntity|DreadedEntity]]</dt> | ||
Line 110: | Line 72: | ||
'''(A3 1.38.128937)''' | '''(A3 1.38.128937)''' | ||
</dd> | </dd> | ||
<dd class="notedate">Posted on March 25, 2017 - 20:47 (UTC)</dd> | <dd class="notedate">Posted on March 25, 2017 - 20:47 (UTC)</dd> | ||
<dt class="note">[[User:Feint|Feint]]</dt> | <dt class="note">[[User:Feint|Feint]]</dt> | ||
<dd class="note"> | <dd class="note"> | ||
The [[hint]] sound is audible only when you have the music volume turned up above 0 in the audio settings. | |||
The [[hint]] sound is audible only when you have the music volume turned up above 0 in the audio settings. | Otherwise, it seems to act the same as [[hintSilent]].<br> | ||
<br> | |||
This is important because if you are running a [[hint]] that fires at 30 fps or more, the [[hint]] will slow down machines that have the music volume turned up but won't slow down machines that have the music volume turned off.<br> | This is important because if you are running a [[hint]] that fires at 30 fps or more, the [[hint]] will slow down machines that have the music volume turned up but won't slow down machines that have the music volume turned off.<br> | ||
<br> | <br> | ||
Best practice is to use [[hint]] for an alert to the player and use [[hintSilent]] for a makeshift display of data to the player that is updated fairly often. | Best practice is to use [[hint]] for an alert to the player and use [[hintSilent]] for a makeshift display of data to the player that is updated fairly often. | ||
</dd> | </dd> | ||
</dl> | </dl> | ||
< | |||
<h3 style="display:none">Bottom Section</h3> | |||
[[Category:Scripting Commands|{{uc:{{PAGENAME}}}}]] | |||
[[Category:Scripting Commands OFP 1.46|{{uc:{{PAGENAME}}}}]] | |||
[[Category:Scripting Commands OFP 1.96|{{uc:{{PAGENAME}}}}]] | |||
[[Category:Scripting Commands OFP 1.99|{{uc:{{PAGENAME}}}}]] | |||
[[Category:Scripting Commands ArmA|{{uc:{{PAGENAME}}}}]] | |||
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] | |||
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]] | |||
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]] | |||
[[Category:Command_Group:_Interaction|{{uc:{{PAGENAME}}}}]] |
Revision as of 00:03, 31 July 2019
Description
- Description:
- Outputs a hint message to the right of the screen (left of the screen in Operation Flashpoint) with a sound (except in Arma). Use hintSilent for soundless hint. To split message in multiple lines either use Structured Text, endl or \n (in lower case).
- Problems:
- 1.00 -wrong parameter ("Arma") defined!-1.00 1.00 Hint messages that exceed the screen may lead to crashes.
1.00 The game would not crash but suffer FPS drop / temporary freezing. - Groups:
- Uncategorised
Syntax
- Syntax:
- hint message
- Parameters:
- message: String or Structured Text - the message to display.
- Return Value:
- Nothing
Examples
- Example 1:
// outputs the following: // Press W to move forward. // Press S to move backwards. hint "Press W to move forward.\nPress S to move backwards."
- Example 2:
hint format ["Hello, %1!", name player];
- Example 3:
hint str count allPlayers; sleep 10; hintSilent ""; // hides the previous hint display
Additional Information
- See also:
- hintChintCadethintSilentdiag_log
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
- Posted on October 20, 2014 - 19:27 (UTC)
- DreadedEntity
-
Be careful when using hints to visualize the effects of commands using the Debug Console. Hint can accept an undefined variable and neither the error nor the hint is shown, the command simply fails. Also notice how the hint command should be
hint str _i;
:for "_i" from 0 to 50 do { hint _i; };
tested in A3 1.32.127785
In a script, an "undefined variable" error will be shown as expected. - Posted on October 21, 2014 - 23:07 (UTC)
- DreadedEntity
-
Contrary to previous games, Arma 3 will happily display hints that far exceed screen space.
However, as hints get longer, FPS suffers tremendously.
tested in Debug Console, A3 1.32.127785 with the following:hint str ((nearestObjects [player, ["BUILDING"], 100]) - [player]); [] spawn { sleep 5; systemChat str diag_fps; }; sleep 10; hint str ((nearestObjects [player, ["BUILDING"], 1000]) - [player]); [] spawn { sleep 5; systemChat str diag_fps; };
Results were: 59.7015 and 5.17297, respectively. Drawing a hint even longer than this, such as nearestObjects with a radius of 10,000 or 100,000 reduces your FPS so much Arma 3 appears to crash, though it doesn't.
Unrelated: Hints will stay on screen for 30 seconds, then fade away over the course of 5 seconds. Tested with: A3 1.32.127785 - Posted on February 17, 2015 - 23:14 (UTC)
- DreadedEntity
- An open dialog will pause the 30-second hint fade timer. (A3 1.38.128937)
- Posted on March 25, 2017 - 20:47 (UTC)
- Feint
-
The hint sound is audible only when you have the music volume turned up above 0 in the audio settings.
Otherwise, it seems to act the same as hintSilent.
This is important because if you are running a hint that fires at 30 fps or more, the hint will slow down machines that have the music volume turned up but won't slow down machines that have the music volume turned off.
Best practice is to use hint for an alert to the player and use hintSilent for a makeshift display of data to the player that is updated fairly often.
Bottom Section
Categories:
- Scripting Commands
- Introduced with Operation Flashpoint version 1.00
- Operation Flashpoint: New Scripting Commands
- Operation Flashpoint: Scripting Commands
- Command Group: Uncategorised
- Scripting Commands: Local Effect
- Scripting Commands OFP 1.46
- Scripting Commands OFP 1.96
- Scripting Commands OFP 1.99
- Scripting Commands ArmA
- Scripting Commands ArmA2
- Scripting Commands Take On Helicopters
- Scripting Commands Arma 3
- Command Group: Interaction