Changes between Initial Version and Version 5 of Ticket #1944


Ignore:
Timestamp:
Jun 21, 2013, 7:09:25 AM (11 years ago)
Author:
historic_bruno
Comment:

I tested the patch with the given example of a Roman ballista, it seems to work, but I have some questions, mostly for Pureon:

  • Would we need a new sound recorded that combines both the winding and firing actions in a single sound?
  • Would that be a pain to synchronize between the animation and the sound, as well as meaning if the catapult can fire faster for some gameplay reason, the sound still won't be synced? (I'm sure this is something we already deal with but maybe not this obvious an example)

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1944

    • Property Cc historic_bruno added; historic bruno removed
    • Property Component Music & Sound FXCore engine
    • Property Summary Add optional attribute to action element for beginning of sound playback[PATCH] Add optional attribute to action element for beginning of sound playback
    • Property Milestone BacklogAlpha 14
    • Property Keywords patch review added
  • Ticket #1944 – Description

    initial v5  
    88What we have now is:
    99
     10{{{
    1011<animation event="0.75" load="0.7" file="mechanical/rome_ballista_atttack.dae" name="Melee" speed="150"/>
     12}}}
    1113
    1214Which fires the sound and projectile at event="0.75" and the projectile appears on the Ballista at load="0.7"
     
    1416What we would like to have is something like this:
    1517
     18{{{
    1619<animation event="0.75" load="0.7" sound="0.1" file="mechanical/rome_ballista_atttack.dae" name="Melee" speed="150"/>
     20}}}
    1721
    1822Here the sound would start to play at sound="0.1" of the catapult cranking + firing animation.