Feature #26940

New script command: moonphase

Added by ruebe about 3 years ago. Updated almost 2 years ago.

Status:Assigned Start date:12/08/2011
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:Scripting: New command
Target version:-
Affected ArmA II version:Please select... First affected ArmA II version:Please select...
Reproduced by another DH user:No Single / Multi Player?:
I am using some Mods:No BIForumURL:
I am using: NGUrl:
Reproducible for you:No WIKIurl:
Related to content of DLC:

Description

The problem: We all know by now that the ingame moonphase is screwed up (see [1]); i.e. the ingame moonphase does not correlate with the real world moonphase. That's why we're out of luck to port one of the known moonphase algorithms.

Use cases or why it's important: While there are many possible uses for this little command, I'll mention one example: customization of any missions startdate/-time: when do you wanna launch that assault? At night? What night? What equipment will be needed?

In conclusion: the moonphase is an important piece of strategic information to plan missions.

Btw. there is another ticket by Rommel (see [2]) for an editor moonphase indicator. While that would be nice too, I think such a scripting command would be enough already, while this should not take too much effort to implement (as compared to changing the editors UI).

Syntax: moonphase <date>,
where <date> is a `date`-array as returned by the command date or at least [year, month, day] (only date, without time).
There could be an alternative syntax without <date>-argument, defaulting to ingame-today, as returned by the date-command.

Returns: a value from 0 (new moon) to 0.5 (full moon) to 0.999* (new moon)

Alternative solution: Show us how to write a function that calculates the erroneous moonphase (or add such a function to the BIS_fnc collection). I'm afraid I don't understand what's mentioned at [1], and it's probably impossible anyway to recreate that exact same error with one of the "cheating" algorithms, that are only valid for the 20th and 21th century.

Final remark: Just fix it at some point. Why not for ArmA3? ;)

[1]: http://community.bistudio.com/wiki/Operation_Flashpoint:_FAQ:_Mission_Editing#Formulas_used_in_OFP_for_tide_levels_and_sun_and_moon_positions.
[2]: http://dev-heaven.net/issues/13924


Related issues

related to ARMA3 Community Issue Tracker - Feature #13924: Moon Phase Indicator New 09/24/2010
related to ARMA2 Community Issue Tracker - Feature #32153: ArmA2 Moon phases should be in sync with real world Moon ... Assigned 05/29/2012

History

Updated by Fireball about 3 years ago

  • Subject changed from new command: moonphase to New script command: moonphase
  • Status changed from New to Assigned

Updated by kju over 2 years ago

  • Category changed from Scripting: Problem to Scripting: New command

Also available in: Atom PDF