Reply To: Reusing pooled FSM allocates memory whereas BT doesn't

[Gavalakis]

Hello Jakko,

Thanks for performing the tests.
The “Standalone” versions of Script Control tasks will only work in iOS after you have created the AOTClasses.cs file through the Preferred Types Editor as explained at the top of the ReadMe file as well as in the documentation. This is not directly relevant to these tasks but rather required for the whole framework to work correctly in iOS (or other AOT platforms).

Regarding the tests, there is value boxing taking place in the return value of a method for ValueTypes such as Status is. This is not happening for parameters though.

If your custom Script Control task and your way of creating delegates can work with all methods/properties regardless of return/parameter types and number of those parameters, by all means I would be more than happy to learn how you do it and to improve the existing Script Control tasks with your own implementation! 🙂
Does your way of doing this, supports all return/parameter types, as well as most importantly, different number of parameters?

Let me know.
Thanks!

Join us on Discord: https://discord.gg/97q2Rjh