playMaker

Author Topic: huh? "Assertion failed on expression: '!go.TestHideFlag(Object::kNotEditable)'"  (Read 620 times)

gumbomasta

  • Playmaker Newbie
  • *
  • Posts: 13
    • View Profile
This error appears twice when building the game as a standalone application. I've only started to run the game and it seems nothing related to the FSMs are affected, and no errors appear in runtime.

What's going on here?  Guidance appreciated!

message:

Assertion failed on expression: '!go.TestHideFlag(Object::kNotEditable)'
UnityEngine.GameObject:AddComponent()


Assertion failed on expression: '!go.TestHideFlag(Object::kNotEditable)'
UnityEngine.GameObject:AddComponent()
PlayMakerFSM:GetEventHandlerComponent(GameObject) (at C:/Projects/Playmaker_1.9.0/Projects/Playmaker.source.unity/Assets/PlayMaker/PlayMakerFSM.cs:469)
PlayMakerFSM:AddEventHandlerComponent() (at C:/Projects/Playmaker_1.9.0/Projects/Playmaker.source.unity/Assets/PlayMaker/PlayMakerFSM.cs:447)
PlayMakerFSM:AddEventHandlerComponents() (at C:/Projects/Playmaker_1.9.0/Projects/Playmaker.source.unity/Assets/PlayMaker/PlayMakerFSM.cs:385)
PlayMakerFSM:Preprocess() (at C:/Projects/Playmaker_1.9.0/Projects/Playmaker.source.unity/Assets/PlayMaker/PlayMakerFSM.cs:225)
HutongGames.PlayMakerEditor.PlayMakerBuildCallbacks:OnPostprocessScene() (at Assets/PlayMaker/Editor/PlayMakerBuildCallbacks.cs:34)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

Unity version:

2018.3.0b6

Playmaker Version: 

1.9.0
« Last Edit: December 11, 2018, 01:10:33 PM by gumbomasta »

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 13857
  • Official Playmaker Support
    • View Profile
Hi,

check this: https://forum.unity.com/threads/bug-problem-with-indirectly-adding-components.544168/

apparently you are doing something that is now not allowed anymore.

 Bye,

 Jean

gumbomasta

  • Playmaker Newbie
  • *
  • Posts: 13
    • View Profile
So I get that this error is thrown when trying to add a component to a prefab.  In this case, this is error is thrown specifically when a build of the game takes place.  Never any other time.

The question I now have is... where does PlayMaker come into this, given all these PM messages are part of this error?

Could it be that the Prefab in question has a PM script attached? 

thanks!
« Last Edit: December 13, 2018, 07:01:35 AM by gumbomasta »

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 13857
  • Official Playmaker Support
    • View Profile
Hi,

 It's likely that you try to edit a prefab asset instead of the instance of it during runtime. I don't think this is PlayMaker by itself that provoke this.

so you need to go through your fsm and check that you are actually working with prefab instances, not the assets directly. It happened to me a lot, but I never had that issue per say, so you might do something to the prefab that I did not.


Bye,

 Jean



Gua

  • Full Member
  • ***
  • Posts: 142
    • View Profile
    • Andrii Vintsevych
Got same errors, when making a build of the game on 2018.3 and Playmaker 1.9. Have no idea how to solve it.


jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 13857
  • Official Playmaker Support
    • View Profile
Hi,

It would be great to explain the context of which this happens, do you edit a prefab, do you have other assets, what are the few things you did before it started popping up?

Bye,

 Jean

Gua

  • Full Member
  • ***
  • Posts: 142
    • View Profile
    • Andrii Vintsevych
I've made big progress on solving this issue. I had costume action called Play Random Sound Gua and it seems that disabled uses of this action were not properly upgraded. So I've found all those problematic instances of this action use and removed them from prefabs. This removed almost all of those errors. I think to remove few of those errors that remain, I need to solve those iTween actions issues.


Gua

  • Full Member
  • ***
  • Posts: 142
    • View Profile
    • Andrii Vintsevych
Hi,

It would be great to explain the context of which this happens, do you edit a prefab, do you have other assets, what are the few things you did before it started popping up?

Bye,

 Jean
So it's a huge project. That I've recently moved from Unity 5.6.6 to Unity 2018.3. I've also upgraded Playmaker. I see those errors when I make a build of the game. I previously mentioned how I was able to reduce number of those errors significantly. But something still generates 3 of those errors. Currently I can tell that those errors start to pop-up when I add Bellville_bbb_ccc.scene and hit build button.

Gua

  • Full Member
  • ***
  • Posts: 142
    • View Profile
    • Andrii Vintsevych
I guess I'll try deleting game objects from copy scene to try to track it down.

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 13857
  • Official Playmaker Support
    • View Profile
Hi,

 uhm... have you reported a bug for this? Maybe there is something we can fix on our end, the fact that action where disabled maybe affect the way things gets serialized.

 Bye,

 Jean

Gua

  • Full Member
  • ***
  • Posts: 142
    • View Profile
    • Andrii Vintsevych
I did managed to eventually fix/remove remaining errors. I've found couple missing scripts on my player character and when I removed those scripts and removed references from Playmaker to those missing scripts. !go.TestHideFlag errors disappeared.

I removed those actions.