Page MenuHomeFeedback Tracker

Artillery support missing in SCUBA showcase mission [Alpha Dev v0.67.106210]
Closed, ResolvedPublic

Description

For me it appears that in the SCUBA showcase mission that artillery support is missing from the radio menu thus its imposable to call an artillery strike as before when playing the mission using v0.67.106210

(no missions, mods or other files in use)
{F19431} {F19432}

Details

Legacy ID
4090057443
Severity
None
Resolution
Fixed
Reproducibility
Always
Category
Gameplay

Event Timeline

b101uk edited Steps To Reproduce. (Show Details)May 14 2013, 6:11 PM
b101uk edited Additional Information. (Show Details)
b101uk set Category to Gameplay.
b101uk set Reproducibility to Always.
b101uk set Severity to None.
b101uk set Resolution to Fixed.
b101uk set Legacy ID to 4090057443.May 7 2016, 2:07 PM
b101uk added a subscriber: b101uk.
NOTE: Its version 0.57.105210

Perhaps you also need to make a better "5" font so it won’t look like a "6" when scaled down!

Taken at 1600x900
http://webspace.ssesurf.co.uk/~m.todd/images/arma3_5or6.jpg

Could you please check it again? Should be fixed. Thanks

It is still broken, though the mortar now appears in the supports menu with an icon on the left/top of the screen signifying availability, however it is ultimately broken at the point you would select the number of rounds to fire (1 or 2)

If you press “0” > “8” (supports) > ”1” (artillery strike) > “1” (mk8 mortar [8 echo]) >

You get on on screen error/script message

“Error in expression <omm_burst" + format [", ETA %1s", round getArtilleryETA [vehicle _provider, _sup> Error position: <getArtilleryETA [vehicle _provider, _sup> Error format: Undefined variable in expression: getartilleryeta”

Taken from: arma3_2013-05-23_09-55-22.rpt & arma3_2013-05-23_10-32-26.rpt

edit: FYI: one .rpt was with "r3f_armes.pbo" (mod) loaded, the other .rpt was with it off thus mod free, also the mortar inc the AI man with it is in place on the map, as I also ran to its position.

As of the v0.59.105634 build that came out today 23rd May, the problem seems to be fixed.

You can disregard my early post (0028645) above from today, as that was the prior v0.59.105592 build.

Closing as fixed. Thanks for feedback.