Hi,
The problem with raycast is that it's quite an intensive task and therefore requires a very careful set up to keep your frame rate ok. Simplifying means having to compromise on this one way or the other. the distance is very important, the repeat option is equally just as important, and so is the layer set up... difficult to find a way to simplify this...
uhm, unless we could tag actions as "performance hit" and playmaker would alert somehow in its interface that some actions are not necessarly the ideal way to get the best performance. Because user would certainly face one day a performance problem if using simplified features and could blame playmaker for it.
The other issue would be the way the playmaker interface for the action is defined. It's "fixed" and can not be changed based on the user input. Let's say we would put an "expert" check box in the raycast action and if the user click check it we show the full set of feature, else we show a cut down version with a warning "not optimized" or something.
Maybe have a plain english description for the direction "forward" "up" "right", "backward", "down", "left", and have in the tooltip the relation between each description and their axis (x,, -x etc etc). This is maybe where the confusion comes from.
Bye,
Jean
