>
> >
> > *quote snip*
> >
> > Here's an example, sorry I used 5 traces, it's just for a experiment, but as you can see, the second instance with the solids disabled still affects the trace: https://www.dropbox.com/s/0p6rkii91i8e4 ... .capx?dl=0
> >
>
> Well, I would like to look at your project, but you've got these other plugins in it.
> [quote:1u81lm8u]
> MagiCam
> Simulate key event
> Platform Plus
>
> While I doubt another plugin is causing a problem, it's still a good idea to keep other 3rd party plugins out of a .capx when you are reporting a bug. But most importantly, I'm lazy and don't want to hunt down and install these plugins <img src="{SMILIES_PATH}/icon_lol.gif" alt=":lol:" title="Laughing">
>
Sorry, forgot about those! Here's a cleaned version: https://www.dropbox.com/s/62rf3cy1y7ukn ... .capx?dl=0
As you see with the delayed function, the added instance causes the tracer to find the obstacles.
Well, the problem is clear as day! Remember what I said before?
If you are using the plugin in 'Solid' mode, it will ignore any instances where the 'Solid' behavior is disabled.
That only applies for 'Solid' obstacle mode. It doesn't work in 'Custom' obstacle mode.
Ahh, so is there a way of sorting it out so I can have a second instance of the tilemap (for backgrounds) with solids disabled and not trigger the trace?