Playmaker Forum
PlayMaker Feedback => Action Requests => Topic started by: Dev_Sebas on November 21, 2011, 12:17:27 PM
-
I think playmaker should have a ray cast action more compatible with users
Because the normal ray cast action is very complex
Bye
-
What features would you want in this simplified raycast action? Something to just raycast forward maybe...?
-
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
-
What features would you want in this simplified raycast action? Something to just raycast forward maybe...?
Yes Alex and I would like PlayMaker have more videos free on You Tube
Bye
-
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
Yah the axis are a bit confusing
-
Ok,
I have made a new version of the raycast ( RayCastFromGameobject ) that has few mods:
1: It only takes a gameObject to shoot the ray from
2: The direction is in plain english ( Forward, Up, Down, etc etc), the tooltip indicates which axis it relates from in case you wanna know for sure.
3: The default value for repeat is 5. I think the main source of misusage is the fact that it's set to 0 by default and therefore fire only onces and done. I am sure that most users struggled with that one when first playing with the raycast action ( i did at least :) ), so I set it by default to 5, which means: it fires once every 5 frames. It's enough for most usage ( perf vs needs) and ensure that the actions works as is when you drop it on a state.
Hopefully this is enough to get a better experience using raycast inside Playmaker ( doesn't take away the fact that more example and screen cast is needed). If you feel that some other areas can be improved, let me know and I'll see what I can do.
[EDIT]
The script I attached to this post was faulty, I have created a proper post with a working version. The custom action is available on this thread: http://hutonggames.com/playmakerforum/index.php?topic=900.msg3685#msg3685 (http://hutonggames.com/playmakerforum/index.php?topic=900.msg3685#msg3685)
Bye,
Jean
-
Very thanks Jean I will try it
Thanks
Bye
-
I have been studying but I can make a bullet hole on my colliders
Have have this
Please help me
Cheers
-
Please help me
-
You need to set the position and rotation of the created object.
Use GetRaycastHitInfo:
https://hutonggames.fogbugz.com/default.asp?W491
And store the position and normal of the hit point in Vector3 variables. Then use those in Create Object.
-
I have put GetRaycastHitInfo in a state and Create Object in another state
Now I have this
Thanks for any help
-
Please help me
-
Make 2 variables: HitPoint and HitRotation.
Use HitPoint for the position and HitRotation for the rotation.
-
Variables?? it donĀ“t exist on PlayMaker
Do you min Vector3 I have put them but it continues not working
Thanks for any help
Bye
-
Hi,
Have a look at this post, it explains how raycast can be used with a step by step explanation.
http://hutonggames.com/playmakerforum/index.php?topic=725.msg3686#msg3686 (http://hutonggames.com/playmakerforum/index.php?topic=725.msg3686#msg3686)
Bye,
Jean
-
Thanks Jean
I will see :)
Bye