PlayMaker Updates & Downloads > Pre-release Discussion

1.8 Cache Component Optimization Question

(1/1)

BigDog:
Hi Playmaker,

I want to understand more about the new optimization in 1.8 which cache component access for actions. My question is what action will benefit from this?

1) Does send event/get/set variable from FSM benefit from this?
2) Does get/set property of component benefit from this?

Thanks!
David

jeanfabre:
Hi,

1.8 doesn't have cache component optimization, it's the new Unity 5 that changes the underlying system which nows becomes more optimized for component access.

else, can you reference the thread you read about this 1.8 optimization?

event/get/set variables also require somewhere to cache the PlayMaker Fsm Component, so yes any optimization would be improving this.

as for get/set property, I am not sure.

 Bye,

 Jean

BigDog:
Hi Jean

It's mention here in 1.8's improvement, the fourth last point.

https://hutonggames.fogbugz.com/?W311

Thanks.

jeanfabre:
Hi,

 ok, yeah, it's the actions themselves. I don't think all actions are affected. I'll enquire with Alex to know more about a possible new technic to cache components. I am not aware of any other trick than the one I am using myself ( which is to store the component in a private variable).

 Bye,

 Jean

Navigation

[0] Message Index