I had a similar problem with check terrain too, is the check terrain assigned to a 'solid' tile? I recall reading that it sometimes doesn´t work if it´s assigned to falling wood or platforms.

With onscreen and variable I can´t help you much, only started using them a little while ago but for the moment I haven´t had problems with them.

Cheers!

Thanks for the response,

Originally posted by Ankon:

I had a similar problem with check terrain too, is the check terrain assigned to a 'solid' tile? I recall reading that it sometimes doesn´t work if it´s assigned to falling wood or platforms.

That would be my problem there. I'm using "hut scaffolding"

Variable Triggers depend on other triggers to work and I have never had any Variables directly fail on me. OnScreen triggers sometimes happen prematurely because the initial camera setup might pan passed it. A remedy for this is delaying their activation time. So they start deactivated and then they become activated after a few seconds from a trigger that occurs in the beginning of the level.

Originally posted by Soup Calhoun:

Variable Triggers depend on other triggers to work and I have never had any Variables directly fail on me. OnScreen triggers sometimes happen prematurely because the initial camera setup might pan passed it. A remedy for this is delaying their activation time. So they start deactivated and then they become activated after a few seconds from a trigger that occurs in the beginning of the level.

I think I'll make onscreen triggers have a forced waiting time (of about a half second or so)

Originally posted by raithza:

Originally posted by Soup Calhoun:

Variable Triggers depend on other triggers to work and I have never had any Variables directly fail on me. OnScreen triggers sometimes happen prematurely because the initial camera setup might pan passed it. A remedy for this is delaying their activation time. So they start deactivated and then they become activated after a few seconds from a trigger that occurs in the beginning of the level.

I think I'll make onscreen triggers have a forced waiting time (of about a half second or so)

Was this forced waiting time for 'OnScreen triggers that start enabled' implemented yet? I am too lazy to update my recent campaign that was plagued by this inconsistency. It happens about 20% of the time when it shouldn't.