1. #1
    IImayneII's Avatar Senior Member
    Join Date
    Mar 2014
    Posts
    1,060

    Editor bug?!

    I'm having some troubles with the editor. I have several moving objects that lag on the first run trough the track, when I start at the cp however the objects act like they should be.

    specific problems:
    lagging moving object (keeps stationary at some point on the moving path)
    invisibility toggle doesn't work properly. The object dissapears immediatly when you see it.

    Like I said, everything works fine when I reset to the checkpoint. Is this just an editor bug? or will this bug stay when I share my track?
    Share this post

  2. #2
    dasraizer's Avatar Senior Member
    Join Date
    Apr 2014
    Location
    UK, Isle of Wight
    Posts
    1,195

    Re: Editor bug?!

    its sounds like your sending far too many impulses to the events, like toggle, easiest way to see if this is the case is to insert a Set Value Event into your impulse chain and increment a Variable Data Source, if its number is greater than 1 you know something not right, easiest way to see if this is the case is to switch the game type to skill game and use the counters to display the results.
    could be down to an Interval Trigger sending more than one impulse or a Hit trigger is not disabling after contact.
    Share this post

  3. #3
    IImayneII's Avatar Senior Member
    Join Date
    Mar 2014
    Posts
    1,060

    Re: Editor bug?!

    Sorry I was going to post a more specific detail of the problem

    I have an area trigger - delayed impulse - state event (on)
    - toggle invisibility
    -impulse trigger (with delay tick and end after 1 impulse) - toggle invisibility

    While trying your idea I removed the impusle trigger and that stopped the problem, I investigated it and the problem was that I had the state event linked to the impulse trigger with event target and event/filter so it got the impulse too fast.

    Thanks for the help and good idea to test future problems
    Share this post

  4. #4
    IImayneII's Avatar Senior Member
    Join Date
    Mar 2014
    Posts
    1,060

    Re: Editor bug?!

    I was a bit to fast, it seems not to work again lol (cp reset still works), even tough I checked the impulses (1 on trigger and 1 after 300 ticks) and the object still dissapeared too soon.

    Setup:
    area trigger - delayed impulse - state event (on)
    [event/filter] toggle visibility
    [event target] interval trigger (off) (interval 300/ start tick 300 / max impulse 1) - toggle visibility



    I am now trying with a different setup and this seems to work

    area trigger - delayed impulse - state event (on) - [event/filter] Impulse splitter
    - Impulse delay filter (300 ticks) - toggle visibility
    - toggle visibility


    I still have no idea why the first one won't work tough, I have almost the same object one checkpoint before with the exact same setup and that one works so might still be a bug
    Share this post

  5. #5

    Re: Editor bug?!

    Originally Posted by basslineux001
    I was a bit to fast, it seems not to work again lol (cp reset still works), even tough I checked the impulses (1 on trigger and 1 after 300 ticks) and the object still dissapeared too soon.

    Setup:
    area trigger - delayed impulse - state event (on)
    [event/filter] toggle visibility
    [event target] interval trigger (off) (interval 300/ start tick 300 / max impulse 1) - toggle visibility



    I am now trying with a different setup and this seems to work

    area trigger - delayed impulse - state event (on) - [event/filter] Impulse splitter
    - Impulse delay filter (300 ticks) - toggle visibility
    - toggle visibility


    I still have no idea why the first one won't work tough
    Surely the event target should be the event filter in the first setup?
    Share this post

  6. #6
    IImayneII's Avatar Senior Member
    Join Date
    Mar 2014
    Posts
    1,060

    Re: Editor bug?!

    Originally Posted by Barrybarfly
    Surely the event target should be the event filter in the first setup?
    Do you mean like this?
    [event target] toggle visibility
    [event/filter] interval trigger (off) (interval 300/ start tick 300 / max impulse 1) - toggle visibility

    I think my setup was good because it's the event target that turns on the interval, and the state event has to send an impulse (event/filter) to toggle the visibility


    I edited in previous post this: I have almost the same object one checkpoint before with the exact same setup and that one works so might still be a bug
    Share this post

  7. #7

    Re: Editor bug?!

    Originally Posted by basslineux001
    Originally Posted by Barrybarfly
    Surely the event target should be the event filter in the first setup?
    Do you mean like this?
    [event target] toggle visibility
    [event/filter] interval trigger (off) (interval 300/ start tick 300 / max impulse 1) - toggle visibility

    I think my setup was good because it's the event target that turns on the interval, and the state event has to send an impulse (event/filter) to toggle the visibility


    I edited in previous post this: I have almost the same object one checkpoint before with the exact same setup and that one works so might still be a bug
    Nvm. I was thinking it was the toggle visibility event target you were referring to!
    Share this post