Page MenuHomeFeedback Tracker

BIS_fnc_UnitPlayFiring and BIS_fnc_UnitPlay
Closed, ResolvedPublic

Description

"BIS_fnc_UnitPlayFiring" works well for helicopters, but not for boats and ifrit/hunters when using the GMG_40 (or smoke screen). For the attack boat, it doesn't shoot at all, while for the hunter/ifrit, the turret does not point in the direction recorded (this is not recorded properly by the BIS_fnc_UnitCapture function probably).
Concerning "BIS_fnc_UnitPlay" I noticed that I don't hear the sound of the boats/cars when I replay what I recorded. {F19556}

Details

Legacy ID
2994043973
Severity
None
Resolution
Open
Reproducibility
Always
Category
Scripting
Steps To Reproduce

Record for instance a GMG Ifrit called "Ifrit", moving and firing using by using BIS_fnc_UnitCapture and make the AI replay all this with BIS_fnc_UnitPlayFiring and BIS_fnc_UnitPlay like in this tuto: http://www.youtube.com/watch?v=ovfKS1l5EQc
You should notice:

  1. No engine sound (in fact this can be fixed by starting the engine manually before starting to play the move)
  2. GMG_40 not firing in the right direction

In the attached example mission, when the Ifrit stops, it fires only in one spot, which is not what I did when recording. It does not launch a smoke screen either when leaving the area, while I did record that.

Additional Information

It would be also pretty awesome if those function would work for the infantry too :)

Event Timeline

super-truite edited Additional Information. (Show Details)
super-truite set Category to Scripting.
super-truite set Reproducibility to Always.
super-truite set Severity to None.
super-truite set Resolution to Open.
super-truite set Legacy ID to 2994043973.May 7 2016, 2:12 PM
super-truite added a subscriber: super-truite.

after further testing, there is no engine sound for every cars when you replay a recorded move

with the new helicopters (in the beta dev build), the firing information is recorded, but not played when executing "BIS_fnc_UnitPlayFiring".

MadDogX added a subscriber: MadDogX.May 7 2016, 2:12 PM

Mass closing ancient tickets with no activity for > 12 months; assume fixed or too trivial.

If this issue is still relevant in current dev build, please re-post.