playMaker

Author Topic: Bug in FSM and PlayMaker Actions using [FIXED]  (Read 1040 times)

BiOs3008

  • Playmaker Newbie
  • *
  • Posts: 1
Bug in FSM and PlayMaker Actions using [FIXED]
« on: January 31, 2021, 01:56:37 PM »
Hi everyone,

Bug Report:
PlayMaker Actions > "Set Material Color"

Simple moves did I try many times and seems like it will not work:
 
I make in Unity a new Cube under Hierarchy, go in PlayMaker FSM and do a new one, then I move on PlayMaker Actions choose "Set Material Color". When I double click or try use that action in my FSM, will in game nothing happend. When I restart the Unity Softwar is the problem still there.

The Second Problem is when I play my Game. The cube is not change that color that I want. It seems the FSM is not working sometimes on the Objects.

Thank you,

Gregor
« Last Edit: February 07, 2021, 09:40:25 PM by Alex Chouls »

Alex Chouls

  • Administrator
  • Hero Member
  • *****
  • Posts: 4000
  • Official Playmaker Support
    • LinkedIn
Re: Bug in FSM and PlayMaker Actions using
« Reply #1 on: January 31, 2021, 02:07:14 PM »
Are you using the built-in renderer?

Material and Texture actions were designed for the built-in renderer. The new Scriptable Render Pipelines are still a bit of a moving target and we need to figure out the best way to support them.

We'll add a note to the tutorial videos about this.

EDIT: In URP you can change the named color from _Color to _BaseColor and it should work.
« Last Edit: January 31, 2021, 02:15:49 PM by Alex Chouls »

Alex Chouls

  • Administrator
  • Hero Member
  • *****
  • Posts: 4000
  • Official Playmaker Support
    • LinkedIn
Re: Bug in FSM and PlayMaker Actions using
« Reply #2 on: February 07, 2021, 09:40:11 PM »
1.9.1p3 now recognizes URP and HDRP.
Set Material Color will automatically use _BaseColor instead of _Color in those pipelines.

Christoph

  • Beta Group
  • Sr. Member
  • *
  • Posts: 254
Re: Bug in FSM and PlayMaker Actions using [FIXED]
« Reply #3 on: February 22, 2021, 06:31:54 PM »
Same issue here. I hoped it was fixed but it's happening now even more it seems. It's global variables with prefabs. A huge mess I would say.