Playmaker Forum
PlayMaker Updates & Downloads => Share New Actions => Topic started by: waveform on July 16, 2019, 07:07:57 PM
-
I done a complete integration of post processing v2, damn that`s a lot of work
all 52 actions:
(https://i.imgur.com/bb774LY.png)
sub parameter in every action
(https://i.imgur.com/xi6va0R.png)
How to use:
the actions is highly optimized and require "Toggle on" the check box above the parameter before get/set/active action
(https://i.imgur.com/XKpMvrh.png)
Let me know in comment below if you like it ;)
PS: you are also welcome if want add to ECO system
-
Hi,
woah, lots of work indeed!!
Few things however. in order to let the user define if a property should be set can be streamlined without the extra toggle.
the property should be set to be using a variable by default, making it show "none", and then that property is ignored.
let's say we have a FsmFloat property "red" for a color action, where you only want to set some colors defined by the user.
so in reset, you do this:
red = new FsmFloat {UseVariable=true};
then, during the execution of the action you do:
if (!red.IsNone)
{
_color.r = red.Value;
}
this way, you don't need an extra toggle. It makes actions take a lot less screen estate
I think it would be a great addition to the ecosystem, would you be ok to make this change? Meanwhile I'll give it a go as well to see how they works.
Bye,
Jean
-
Greate idea, i will use it to the "Get" actions, but this solution will not work well with "Set" actions, my Reset settings on "set" actions is based by a new post prosessing profile and some value shouldn`t be 0 by default
Hi,
woah, lots of work indeed!!
Few things however. in order to let the user define if a property should be set can be streamlined without the extra toggle.
the property should be set to be using a variable by default, making it show "none", and then that property is ignored.
let's say we have a FsmFloat property "red" for a color action, where you only want to set some colors defined by the user.
so in reset, you do this:
red = new FsmFloat {UseVariable=true};
then, during the execution of the action you do:
if (!red.IsNone)
{
_color.r = red.Value;
}
this way, you don't need an extra toggle. It makes actions take a lot less screen estate
I think it would be a great addition to the ecosystem, would you be ok to make this change? Meanwhile I'll give it a go as well to see how they works.
Bye,
Jean
-
Update these"get/active/get active"actions , but did not modify any changes in "set" actions,because my project need those reset settings, if you dont need those settings, you are welcome and modify it
-
Hi,
Cool, yeah, I'll modify them when I'll put them on the Ecosystem.
Thanks for your work !! we truly appreciate your contribution :)
Bye,
Jean
-
Cool, I'll try them out today. ;D
-
@waveform, Thanks! In your screenshot with actions list, I don't see any action related to anti-aliasing. Are there plans to add those actions?
-
basically anti-aliasing is a part of post processing layer component, this means you are able to do that with "Set Property" action, that´s also why i decided not make action for it
(https://i.imgur.com/ngcP9fy.png)
@waveform, Thanks! In your screenshot with actions list, I don't see any action related to anti-aliasing. Are there plans to add those actions?
-
Thanks a lot!
-
These make their way onto the Ecosystem yet? :D
-
Thanks, I was searching it a while, this should put on ecosystem to make people easier to find it
-
Hi,
they are now, there is a small bug in PlayMaker that prevent me from doing the mods I wanted, so let's put them like that for now.
Bye,
Jean