Page MenuHomeFeedback Tracker

checkVisibility command argument order improvements.
New, WishlistPublic

Description

The new checVisibility command is great, but since it essentially functions in a very similar fashion to the existing intersection commands I'd like to suggest that its arguments order be made similar as well, as the current implementation is slightly confusing.

Current: [ignoreObj, lod] checkVisibility [startPosASL, endPosASL];

Suggested: checkVisibility [startPosASL, endPosASL, lod, ignoreObj1, ignoreObj2];

Adding a second ignored object would be extremely helpful and fall in line with existing commands. Since usually commands like these are checking between to known objects, checkVisibility only being able to ignore one means that sometimes using getPosASL on the object or eyePos will return 0 visibility due to the check point being INSIDE one of the objects.

Details

Legacy ID
3018303775
Severity
None
Resolution
Open
Reproducibility
Have Not Tried
Category
Scripting
Steps To Reproduce

N/A

Additional Information

Standardizing calling conventions amongst similar commands goes a long ways in improving readability and understanding of SQF codebases.

Event Timeline

Nou edited Steps To Reproduce. (Show Details)Oct 4 2015, 7:27 AM
Nou edited Additional Information. (Show Details)
Nou set Category to Scripting.
Nou set Reproducibility to Have Not Tried.
Nou set Severity to None.
Nou set Resolution to Open.
Nou set Legacy ID to 3018303775.May 8 2016, 12:53 PM