Update fnc_isNight

[rekterakathom]

When merged this pull request will: Utilise getLighting to check if it's night

1. Describe what this pull request will do

Utilise getLighting so the night check is based off of the amount of light instead of a soundcontroller. This might be an important distinction in cases where the night is really bright, due to midnight sun or the full moon.

~65 is the approximate light level where AI uses nightvision. Tested on Stratis (2035/07/06 YYYY/MM/DD) with vanilla AI.

2. Each change in a separate line

• Switch getEnvSoundController to getLighting

[nk3nny]

Hmm. Testing indicated that units on headless clients may have problems. HC reports different value for getLighting.

It is possible to use getLightingAt, but that is actually slower than getEnvSoundController .

https://community.bistudio.com/wiki/getLightingAt

[rekterakathom]

Hmm. Testing indicated that units on headless clients may have problems. HC reports different value for getLighting.

It is possible to use getLightingAt, but that is actually slower than getEnvSoundController .

https://community.bistudio.com/wiki/getLightingAt

Does it work on dedi servers? If it does, then this sounds like a HC bug

[nk3nny]

Tested on dedicated server environment. Both server and HC had units spawned on it.

I'll give it another test in a 'live' mission too.

[nk3nny]

Server reported correct values. Only HC struggled. Wonder if there is some silliness about the location of the HC too.

[diwako]

location about the hc unit should only affect update rates iirc. can always bother dedmen in the arma discord.

[jokoho48]

location about the hc unit should only affect update rates iirc. can always bother dedmen in the arma discord.

this is a "global" value getter not a local one. so I expect that there is some issue related to how HCs are handled. this should be reported to to BI/dedmen

[rekterakathom]

Feedback tracker ticket: https://feedback.bistudio.com/T178396