playMaker

Author Topic: Automation to substitute Get/Set Properties from Unity 4.x to 5.x  (Read 8217 times)

twiggyash

  • Playmaker Newbie
  • *
  • Posts: 13
Re: Automation to substitute Get/Set Properties from Unity 4.x to 5.x
« Reply #15 on: April 05, 2016, 08:07:31 PM »
Quote
many activate/deactivate render mesh actions doesn't work.
There are problems with particle systems too, none works.
I noticed problems too with skinned meshes;

Which actions are you using in these cases? Can you give me examples?
If you can fix the problems manually let me know how and maybe we can automate it. But I need specific examples...
Ok, for render mesh enable/disable I used Set property - Render - Enabled;
for system particles I used Set Property - System Particle - Emit;
for nested skinned mesh conflicts is difficult to explain, but in my case I have a character with a mesh for body (skinned mesh) and one separated mesh for hairs (other skinned mesh), I referenced a Get/Set action to hairs mesh and it turned into an action to the parent character. Do not know why.

Alex Chouls

  • Administrator
  • Hero Member
  • *****
  • Posts: 4000
  • Official Playmaker Support
    • LinkedIn
Re: Automation to substitute Get/Set Properties from Unity 4.x to 5.x
« Reply #16 on: April 05, 2016, 10:49:03 PM »
Hmmm, the update should fix Renderer and Particle System component references.
Any chance you could build me a scene in 4.x with just the actions that fail?

twiggyash

  • Playmaker Newbie
  • *
  • Posts: 13
Re: Automation to substitute Get/Set Properties from Unity 4.x to 5.x
« Reply #17 on: April 06, 2016, 11:12:20 AM »
Hmmm, the update should fix Renderer and Particle System component references.
Any chance you could build me a scene in 4.x with just the actions that fail?
Ok. Let me try do make a little scene with this two issues in Unity 4.7