You can add a separate distance and angle comparison check to bypass those restrictions.

Thanks for the reply!

Do you mean a separate check to see if the object is in range and should be visible that bypasses Construct's Line of Sight check? How would I prevent this angle and distance check from returning objects that should be obstructed by obstacles?

The only solution I could think of was to do away with Construct's LOS system all together and use a series of of "for" loops to check for any obstacles in a ring around the player, but I was hoping there was a better way.

Hello all!

I seem to have run into a wall with the Line-of-Sight behavior.

It seems that any objects that obstruct line of sight also obstruct themselves. This means that any objects such as walls or trees that might be used to hide objects behind them are themselves invisible to the LOS behavior.

Is there any way around this little problem or alternative solutions/plugins that others have had success with?

If this is just a limitation of Construct's line of sight behavior, it's a damn pity as it greatly limits the behavior's potential.

Thanks very much in advance.

Hello all, sorry for bumping this.

I seem to have resolved my problem. As usual, it was even stupider than I thought.

I was simply spawning these objects off screen and not realizing it.

Hello all,

I come to you today with an issue I have repeatedly run into on my current project.

Mainly, that objects created in some of my triggered events, while reflected in the object count, don't seem to display until triggered a second time. I am not certain if I am failing to grasp something fundamental about the way events propagate in C2, or if this is a bug of some sort.

In the event pictured below, the circled action is triggered successfully by the loop and the objects created (according to the objectCount expression) however none of these objects will become visible until this same event is triggered a second time.

Has anyone run into this issue in the past?

In some cases a work around is possible by using a global triggering variable that triggers the action in a separate function, but in this particular instance that solution would be cumbersome. Any advice would be greatly appreciated.