Weird effect trigger glitch... | Forums

[stllbreathnbdy]

So I'm busting out my theme for a rattler extreme. In this track I have flames that turn on when you trigger a checkpoint. ALL the checkpoint flames are off by default, and turn on as expected during testing. However, when I take it into Xbox live multiplayer, different ones are already lit before I ever get to them, and my friends can see it too. Weird. Then I go back into the editor, load my track, test it, and the flame that was lit in multiplayer is lit on my track! Even though I had saved it beforehand with all of them off by default. WTF?

I'm just using the fire-heavy variant 1

Has anyone had this happen to them?

[xDEAD_EXITx]

Welcome to the club! Checkpoints just arent working like they use to.

[stllbreathnbdy]

very well then. I suppose an area trigger square at the checkpoint will work just the same

[stllbreathnbdy]

So...it doesn't work. I'm pretty confident the reset on checkpoint restart option is completely unsresponsive. You can change it from on and off all you want, use set values into VDS to change it, whatever, it doesn't work. It is always set to ON.

Has this already been talked about? Does redlynx know that a very basic, fundamental function is broken?

[rlmergeuser]

I think that i had the same problem sometimes. If you mean that you put some effects with state off, you test the track, turn them on during the game and when you come back to the editor it stay on state on... For example, in my last track, all the smoke that represent the tornado near the highway was off. And sometimes after some test, i found some of them on. I thought i made a mistake somewhere, but i'm pretty sure I had checked everything....

[sparkierjonesz]

testing could potentionly change some stats unwanted
so make sure to check before release

anyway the reset in checkpoint option is quiet complex
some reset functions can be found in events or so where you would think it would be somewhere else
make sure to change enough reset in checkpoint(some even when you think it would have no effect)

[xDEAD_EXITx]

Did you check my (The craziest bug thread)? Its a few threads under this one. Im on my phone so cant put the link. Im still having that issue on that 1 track. Its the most annoying thing ever.

[stllbreathnbdy]

testing could potentionly change some stats unwanted
so make sure to check before release

anyway the reset in checkpoint option is quiet complex
some reset functions can be found in events or so where you would think it would be somewhere else
make sure to change enough reset in checkpoint(some even when you think it would have no effect)

My settings are accurate. I'm 100% sure of it.

[sparkierjonesz]

you sure you don't have any stuff that could be canceled by some other code

[stllbreathnbdy]

you sure you don't have any stuff that could be canceled by some other code

Trigger(disable after first hit YES. Reset on checkpoint restart NO.)-> effect ON( reset on CP NO)-> sound event(reset on CP NO)-> sound event( reset on CP NO)

Despite these settings, every time I hit B, the sequence occurs. It should only go once, then never again.