1. #1
    Core2TOM's Avatar Senior Member
    Join Date
    Mar 2014
    Location
    Germany
    Posts
    506

    Visibility Event question (reset in checkpoint restart)

    im working on a hidden ninja for my track, but i got a problem with the visibility event and atm no idea whats the easiest way to fix it:



    when i activate the ninja i make the bomb and landing light visible with the visibility event (visible) no reset in checkpoint restart. works...
    if you hit the barrel, it will explode, the landing light turns to invisible and should be visible again on checkpoint restart.

    whats confusing to me is that the visibility event (hidden) turns the landing light to invisible on checkpoint restart even without any impulses from the hit trigger.
    why?? and whats the easiest way to fix this?
    Share this post

  2. #2
    i actually think it might be because
    landing light starts invisible
    you start ninja->visible
    you reset->back invisible
    and the visible doesn't have checkpoint restart so it doesn't stay visible

    afaik the visible should have checkpoint restart
    might mess up the other part of the code
    but adding a set event to turn off reset at checkpoint restart for the visible event should do the trick to fix that if needed
    Share this post

  3. #3
    TeriXeri's Avatar Senior Member
    Join Date
    Mar 2014
    Posts
    1,163
    Bit of generic response here, because I think it applies to more then just visilbility events.

    If you have any event linked to an object with "reset on checkpoint restart" it will reset to the state at the start of track regardless if it's been triggered or not, I have noticed this multiple times when I use on and off events on sounds/lights/state to optimize performance.

    Even if you have an ON event with reset turned off, and then an OFF further in track with it on pointing to the same sound/light whatever object, it will prioritize the reset.

    I thought it was a bug at first but I guess this is how it's supposed to work.

    You can always use a 0/1 event to toggle the (object position)reset on restart somewhere, which I have done for a part of track that falls down in front of rider to form a driveline.

    So that it doesn't mess up halfway it's animation (OPE) or animate twice, it's either in it's pre-falling down state at the CP before the trigger, or already fell down on the checkpoint after the trigger.

    The description on the checkpoint restart option is slightly different when used in different places as well. When it says something like "reset this object to the state at track start" it will just do that every time it's toggled on regardless if it's been triggered somewhere before.
    Share this post

  4. #4
    Core2TOM's Avatar Senior Member
    Join Date
    Mar 2014
    Location
    Germany
    Posts
    506
    Originally Posted by sparkierjonesz Go to original post
    visible doesn't have checkpoint restart so it doesn't stay visible
    it does stay visible without checkpoint restart, its invisible by default.
    checkpoint restart (on any of the visibility events, triggered or not) = invisible at checkpoint restart
    touching the explosive = invisible at checkpoint restart

    the only way i found to fix it is to use every single checkpoint to trigger the visible event on checkpoint restart again... but there must be an easier way (?)

    activate ninja impulse


    set value 1 ►► variable datasource: 0


    generic filter: equal 1 ►► on true ►► visibility event: visible


    checkpoint: trigger on checkpoint restart
    Share this post

  5. #5
    does the R trigger have a reset on checkpoint restart function?or the hit trigger?

    its been a long time since i used the reset on checkpoint stuff to make a non resetting animation and it will be a few hours before i'm near my xbox

    i remember having issues getting the animation to work properly because stuff i thought wouldn't affect the reset thing like triggers etc
    Share this post

  6. #6
    Core2TOM's Avatar Senior Member
    Join Date
    Mar 2014
    Location
    Germany
    Posts
    506
    the hit trigger has a reset on checkpoint restart option, but that has nothing to do with the problem. try it out for yourself, maybe you get the idea then
    Share this post

  7. #7
    when i got home i could test this for a bit

    simplest solution i found is add a set event after R->visible
    that set event changes a variable datasource from 0->1(no reset)

    now add a interval trigger(1tick) with its enabled status tied to the datasource link that to the visibility event


    the idea is that the variable datasource tells you if the ninja version is triggered or not
    and if so the interval trigger will send 1 impulse on checkpoint restart to make everything visible again)
    Share this post

  8. #8
    TeriXeri's Avatar Senior Member
    Join Date
    Mar 2014
    Posts
    1,163
    Just looking at the video picture, you have the Hidden event pointing to the landing light, with reset on CP enabled.

    Which automaticly means (does not need any impulses) it overrides anything that changed.

    Because the reset on checkpoint on it really means "reset object to the state it's in at track start" it will go back to it's basic state before any triggers.

    So if it's invisible at start, that is the "state" it's defaulted to.

    So it will be invisible every time, regardless if it was made visible, unless you change the hidden trigger's "reset on restart" to 0 instead of 1.



    picture is a bit small, sorry, but the text reads :

    "Select if you want to reset the targets' state back to what it was in track start in checkpoint restart."
    Share this post