Playmaker Forum
Bug Reporting => PlayMaker Bug Reporting => Topic started by: Amimoller on January 22, 2014, 04:19:50 AM
-
Hi,
We have a serious issue with playmaker in our project.
After some time, playmaker seems to forget any further changes you make, I think its related to having been in play mode.
If I make a change to an action and switch to another FSM and back, that change will be forgotten. The only way to make it work is to restart Unity. It happens with Prefabs and Instances.
I have tried both the latest beta and normal 1.7.6 but it still happens.
Unfortunately i cant reproduce it in a simple test project, (our main project is gigabytes of data) so i was hoping someone else might have the same problem.
Cheers
Jonas
-
I noticed that i sometimes get this error:
ArgumentNullException: Argument cannot be null.
Parameter name: key
System.Collections.Generic.Dictionary`2[System.Type,HutongGames.PlayMakerEditor.ObjectPropertyDrawer].TryGetValue (System.Type key, HutongGames.PlayMakerEditor.ObjectPropertyDrawer& value) (at /Users/builduser/buildslave/monoAndRuntimeClassLibs/build/mcs/class/corlib/System.Collections.Generic/Dictionary.cs:588)
HutongGames.PlayMakerEditor.ObjectPropertyDrawers.GetObjectPropertyDrawer (System.Type objType)
HutongGames.PlayMakerEditor.FsmVariable.DoValueGUI (UnityEngine.GUIContent label, Boolean isAsset)
FsmComponentInspector.OnInspectorGUI () (at Assets/Packages/PlayMaker/Editor/FsmComponentInspector.cs:156)
UnityEditor.InspectorWindow.DrawEditors (Boolean isRepaintEvent, UnityEditor.Editor[] editors, Boolean eyeDropperDirty) (at C:/BuildAgent/work/d3d49558e4d408f4/Editor/Mono/Inspector/InspectorWindow.cs:850)
UnityEditor.DockArea:OnGUI()
Not sure if that could be related, we do have a couple of custom inspectors in the project.
-
Hi,
It will be difficult to debug. Do you notice some improvement if you turn them cusotm inspectors off?
bye,
Jean
-
Are you using the 1.7.7 RC6 Beta?
There is a bug in 1.7.6 with the editor losing changes with Lock enabled.
-
I'm getting the same problem. Can't keep variable changes in the FSM after playing. How can I download the latest RC? If bug remains I'll upload my small project as a bug report
-
Are you using Lock in the Graph View? The next update should be available very soon...
-
Not using the inspector lock function, no.
HOWEVER, I was messing around trying to find a workaround, and I got rid of the issue.
I don't know why, but after I deleted "Particle Playground" (Asset from store) from my plugins folder everything worked. Interesting.
-
Interesting. I'll download Particle Playground and see if I can repro the bug here...
-
I just tried with the lastest RC and its still a problem. Im also pretty sure it has something to do with having been in playmode.
I also still get that propertydrawer exception, I havent had a chance to remove our custom ones and see if it helps. Ill try if i can find some time for it.
-
We also seem to be having the exact same problem as Animoller.
We dont get any of the errors that Animoller gets though. We arent using any Locked FSMs and we are also on the latest Playmaker version (1.7.7.1), so it cant be that glitch either.
We do also have Particle Playground though just like Jbro so it could be that, we have deleted it from our project and will test out if Particle Playground is the culprit.
-
same thing here. started to happen right after particle playground installation..
side note - i think it happens mostly with hard-coded values. flipping to a variables and pressing save a few times helps. it's a bit erratic.
-
Yes, just confrimed that it is Particle Playground as Playmaker seems to run perfectly now that I have removed it from the project folder. I will contact the creator of Particle Playground and just inform him that his package causes conflict with Playmaker.
-
Just left the author of Particle Playground a message just inform him of the bug. Hopefully this can get fixed soon as we really need both plugins.
-
The author of Particle Playground says that he is in contact with Hutong Games and they are trying to sort out the problem.
Unfortunately he isnt able to reproduce the problem in a new clean project, so I will try and see if I can get a small project set up tomorrow that recreates the bug.
If anyone else is able to replicate the bug please send a project over to the author of Particle Playground (Unity username: save).
Im also starting to think it might be the custom inspectors as Animoller mentions he is getting the same glitches but he doesnt seem to be using Particle Playground and he is receiving errors showing conflicts between some custom inspectors as Playmaker and Mr. jeanfabre mentioned.
So I wonder if it could maybe be the custom inspectors in Particle Playground as they are quite intricate.
-
I am having sort of the same problem.. When changing a value in an action, as soon as it focus off of it the value returns to the previous value.. this happens with prefabs as well.. Only way I can get them to work is to shut down unity, restart and immediately change the value.
Also, having problem with sometimes the Actions and Global Variable windows not opening when pushed. To fix I also need to restart unity..
Using Playmaker v1.7.7.1
unity 4.3.4f1
Thanks hope this gets fixed soon.. its not a huge deal but sort of annoying. Heh
-
@dark3d: Just want to check you dont perhaps have Particle Playground installed into the project? As it seems that is a common source for most of us. Or perhaps are you maybe getting any errors?
-
Ive managed to reproduce the problem in a clean project containing just Playmaker, Particle Playground and the Playmaker Pathfinder custom actions (I dont even have any of the Standard Assets imported).
So it seems that there is some kind of conflict between Playmaker, Particle Playground and the Playmaker Pathfinding custom actions.
Hope the info helps any one in need or qurious about the problem.
I am sending the project over to the author of Particle Playground now so that he can check it out and maybe figure out what is going wrong.
-
Hi people!
Developer behind Particle Playground here. I'm currently looking into what could be the cause of this abnormal behavior, thanks to SkobbejakGames I've gotten a tremendous kickstart. I'll let you know as soon as I progress in the matter.
Sorry for all the inconvenience!
-
Hi,
Amazing asset Save. Keep us updated. Don't hesitate to Pm me if you need help on specific aspect of PlayMaker.
bye,
Jean
-
Hi,
Amazing asset Save. Keep us updated. Don't hesitate to Pm me if you need help on specific aspect of PlayMaker.
bye,
Jean
Hi!
Thank you Jean! I have to say the same about Playmaker. :-)
I've been able to reproduce the problem now thanks to SkobbejakGames and found a solution. The issue stemmed from the Unity editor's update delegate. Version 1.16 will play nice with Playmaker, it will be published in a couple of days. Thanks for your patience all Playmaker users!
-
Wow, thanks so much save! Glad that the problem wasn't too difficult to sort out. Looking forward to the upcoming update, then I can finally jump on Particle Playground and start creating some awesome effects.
Again huge thanks to save and jeanfabre for helping with the issue as well as all the other people in this forum post that added their details to help close in on the source of the problem.
-
Thought I should drop by with the good news. :-)
Version 1.16 of Particle Playground is available, addressing the PlayMaker issue. If you have any troubles regarding the Playground in your project, please hit me with a mail at support@polyfied.com. Thanks for all patience!