Best way to apply delay FX?

edited March 2012 in Help request
Say I have three orxOBJECTs. I want to apply the same FX to each of them when they are created, but I want to stagger it so the FX doesn't start on one until 0.5s after it has started on the previous one.

Last time I needed this, I solved it in code by using AddDelayedFX.

Is there any way to specify this in config instead?

Comments

  • edited March 2012
    Well I can only think of one way to do it entirely in "config", and it's not as pretty to me than using AddDelayedFX:

    using actually 3 FXs inheriting from a common parent instead of just one and shifting their start/end times accordingly.

    That being said, what would you say of having a Delay property in the FX itself? :)
  • edited March 2012
    Argl, the way FXs are added from the object module actually prevents this right now. Needs to think about it and find the best way to do that...
  • edited March 2012
    Would a FXDelayList in the object config do the trick for you?
  • edited March 2012
    Ah well, I got impatient so I added a FXDelayList property to the object config. :D

    Let me know if that works for you.
  • edited March 2012
    Argl, the way FXs are added from the object module actually prevents this right now. Needs to think about it and find the best way to do that...

    "Good", because I tried to do it just like that, by shifting the start and end times, and could not make it work. I was getting frustrated.
    Ah well, I got impatient so I added a FXDelayList property to the object config. :D

    Let me know if that works for you.

    That's great, thank you! Yes, I think that's the best option in config. I'll try it tonight and let you know how it goes.

    This will help a lot, because it's very common to create a big group of objects and need them to do almost the same thing, but "follow" each other.
  • edited March 2012
    acksys wrote:
    "Good", because I tried to do it just like that, by shifting the start and end times, and could not make it work. I was getting frustrated.

    Yep, the reason for that being that FXs, like sounds, shaders or textures, for example, are unique in memory, identified by their name. So as long as there's already one FX with that name in memory it will not get recreated, and thus your new config values won't get read.
  • edited March 2012


    Works great!
Sign In or Register to comment.