setAperture: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
(add. ArmA2 classification) |
||
Line 38: | Line 38: | ||
[[Category:Scripting Commands OFP Elite |SETAPERTURE]] | [[Category:Scripting Commands OFP Elite |SETAPERTURE]] | ||
[[Category:Scripting Commands ArmA|SETAPERTURE]] | [[Category:Scripting Commands ArmA|SETAPERTURE]] | ||
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] |
Revision as of 17:18, 3 June 2009
Description
- Description:
- Sets custom camera aperture (-1 to do it automatically).
- Groups:
- Uncategorised
Syntax
Examples
- Example 1:
setAperture 0.3
Additional Information
- See also:
- See also needed
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
-
Maruk: It's up to the maker of the mission to decide if HDR effects are to be disabled and what aperture to be used. Of course, this static aperture setting will not work well after lighting conditions changed too much.
(forum discussion)
Namikaze: The aperture value to simulate typical daylight (outdoor) conditions is 50. The aperture value to simulate typical daylight (indoor) conditions is 30. Setting the value to less than 20 will result in a very bright scene, suitable for night conditions. The closer the number is to 0, the more light will be let into the lens, to carry on the aperture metaphor. Different lighting/weather conditions can change the actual indoor and outdoor aperture values. Experiment and test to be sure.