Playmaker Forum
PlayMaker News => PlayMaker Announcements => Topic started by: Alex Chouls on January 07, 2017, 02:36:50 PM
-
NOTE: THIS IS NOT LONGER NEEDED WITH LATEST VERSION OF PLAYMAKER
Please import the attached package to fix issues with the Unity 5.6 beta.
NOTE: Sometimes beta versions of Unity break things. Please report any problems you run into with the Unity betas so we can fix them as quickly as possible.
-
;D ;D ;D ;D ;D ;D ;D ;D ;D :D :D :D :D :D :D 8) 8) 8) 8) 8)
-
Just as a quick question, has anyone had any crazy issues with the Unity 5.6 beta as far as Playmaker goes?
Reeeallly been eye-balling that navmesh recalculation... thinking about upgrading now? :D
-craigz
-
would this help the new beta 5.6b8's issues? the newest beta breaks the FSM components. thanks!
-
Having some serious issues with Unity5.6b9 which we're being forced to use because of the Daydream support.
Our playmaker globals aren't loading, the inspector when on the resources/playmakerglobals asset has 'The associated script can not be loaded'. Have tried the attached package which doesn't help.
Any tips on what we can do to fix this? Readding all our globals is going to take a while..
-
me too, hopefully we hear something soon!
-
Having some serious issues with Unity5.6b9 which we're being forced to use because of the Daydream support.
Our playmaker globals aren't loading, the inspector when on the resources/playmakerglobals asset has 'The associated script can not be loaded'. Have tried the attached package which doesn't help.
Any tips on what we can do to fix this? Readding all our globals is going to take a while..
I have the same issue too in 5.6b9, I hope it can be solved soon....
-
ok, I'm working my way through a fix - I'll let you guys know where I am in case you're like me and you have tight deadlines to meet.
Make a copy of your playmaker globals file (Assets/Playmaker/Resources) - preferably from GIT pre 5.6 update.
So go to your playmaker globals file, and click on the 'playmakerglobals' (Assets/Playmaker/Resources) script in the inspector. It should show you which script the globals object is using in your project window. In my case it was pointing to the Playmaker.dll in Plugins/Playmaker/WP8 - obviously the wrong one! Set it to the right one in Plugins/Playmaker.
Then finally, if your globals object hasn't updated, open the asset in a text editor like sublimetext, open your backed up copy, and copy/paste all the variables at the end of it into the current file.
-
Hi,
I tried this but cannot see any info on assigning the proper dll when I select the globals object. I see a spot for health manager...
" It should show you which script the globals object is using in your project window. "
maybe I don't understand where to source the globals file from, I copied it from a pre 5.6 project. opening this file just shows binary numbers... maybe im out of my league here hehe
-
Headtrip, you need to click on the panel menu (that little 3 line burger icon next to the padlock on the inspector) and choose 'debug' rather than 'normal' right at the top.
Then it will show you what script that object is using, and you can swap it out.
But far more pressing, is the fact that the new update breaks all FSMs. So even if you can restore globals all your logic breaks. Which renders this a bit of a moot exercise. Do we have any idea when a fix might be forthcoming, a fix that can successfully upgrade our FSMs? As you can imagine this is pretty serious for any projects for which 5.6 will become mandatory.
-
any official updates? thanks
-
Same here, I've lost all FSM connection after upgrading to 5.6 Beta. Is there any solution?!?!
-
It has been few days since last post with answer regarding fixing the broken links to FSM scripts ?
-
Hi,
It's currently being worked on.
Bye,
Jean
-
As far as I can tell this is a Unity bug that they're aware of. I'm hoping the fix will be in the next Unity beta.
-
thank you for the updates! I see there's a new beta out today :)
-
Yes, new beta here 5.6.0f1 - Release Candidate 1 March 17, 2017
https://unity3d.com/unity/beta/archive
-
tried it, no luck. Same result, but odd... I opened a scene from the samples and it was fine. http://www.hutonggames.com/samples.php
-
strange :o :o :o :o
-
Similar results on my side. Project is still reading the DLL from the WP8 folder.
What's more is that older versions of Unity now refuse to load in the updated project (hard crash with no bug reporter) so rolling back is harder than it should be.
I'm just checking with another project (it has several GBs of textures so is taking a while to import) and I'm going to see if I can manually reassign the playmakerFSM script to use the default DLL while still keeping the same values. If it can then I guess I'll be doing that over the next few hours. If not expect more cursing!
-
I also updated yesterday to 5.6 seeing that it was the first non beta release, and I really need this new runtime navmesh creation.
I understand that this is a complicated issue, and I know you guys are doing your best to solve it. However, I'd like to know if you could tell us in how much time (roughly of course) you think this issue will be solved?
-
Ok. so project has finally updated but it's still broken and manually reassigning the proper script from the right DLL results in a corrupt/empty FSM.
It did throw this error on opening the scene so adding it here in case it helps debug this:
NullReferenceException: Object reference not set to an instance of an object
HutongGames.PlayMaker.FsmState.GetTransition (Int32 transitionIndex) (at c:/Users/Alex/Documents/Unity/Playmaker/Projects/Playmaker.source.unity/Assets/PlayMaker/Classes/FsmState.cs:594)
HutongGames.PlayMakerEditor.FsmSelection.set_ActiveFsm (HutongGames.PlayMaker.Fsm value) (at c:/Users/Alex/Documents/Unity/Playmaker/Projects/Playmaker.source.unity/Assets/PlayMaker/Editor/Classes/FsmSelection.cs:123)
HutongGames.PlayMakerEditor.FsmSelection..ctor (HutongGames.PlayMaker.Fsm fsm) (at c:/Users/Alex/Documents/Unity/Playmaker/Projects/Playmaker.source.unity/Assets/PlayMaker/Editor/Classes/FsmSelection.cs:259)
HutongGames.PlayMakerEditor.FsmSelectionHistory.GetSelection (HutongGames.PlayMaker.Fsm fsm) (at c:/Users/Alex/Documents/Unity/Playmaker/Projects/Playmaker.source.unity/Assets/PlayMaker/Editor/Classes/FsmSelectionHistory.cs:296)
HutongGames.PlayMakerEditor.FsmSelectionHistory.SelectFsm (HutongGames.PlayMaker.Fsm fsm) (at c:/Users/Alex/Documents/Unity/Playmaker/Projects/Playmaker.source.unity/Assets/PlayMaker/Editor/Classes/FsmSelectionHistory.cs:174)
HutongGam
-
Any update for 5.6?
I got many these errors:
PlayerSettings Validation: Requested build target group (27) doesn't exist; #define symbols for scripting won't be added.
UnityEditor.PlayerSettings:SetScriptingDefineSymbolsForGroup(BuildTargetGroup, String)
HutongGames.PlayMakerEditor.PlayMakerDefines:AddScriptingDefineSymbolToAllTargets(String) (at Assets/PlayMaker/Editor/PlayMakerDefines.cs:42)
HutongGames.PlayMakerEditor.PlayMakerDefines:.cctor() (at Assets/PlayMaker/Editor/PlayMakerDefines.cs:23)
UnityEditor.EditorAssemblies:ProcessInitializeOnLoadAttributes()
-
Hi,
I don't get this,
- Which version of PlayMaker are you using?
- What platform are you targeting in Unity?
Bye,
Jean
-
Hi Jean,
PM: 1.8.3
Android
-
Hi,
ok, can you fill up a bug report ( via Playmaker/Tools menu), this needs addressing indeed.
Bye,
Jean
-
Thank you for the patch. Will we be getting a full 5.6 compatible version of playmaker at some point ? I am about to start a new project in 5.6 RC1 and using a patched version playmaker does not give me full confidence (even though I am sure it is fine)
-
Hi,
You should wait for the next PlayMaker update, it's coming soon and will provide support for 5.6. however since 5.6 is still in beta further releases of 5.6 could break things here and there, this is the problem while in beta.
Bye,
Jean
-
that's great news! thank you!!
-
I just tried 5.6.f3 and it seems to work fine with the current playmaker version!
-
Quick update: We released Playmaker 1.8.4 for Unity 5.6 compatibility. Also the final 5.6 release fixed the 5.6 beta bug with missing scripts when updating projects.
-
Thanks but i have 2 Errors after Import the new version
http://prntscr.com/erbnko
-
I have these warnings (Unity 5.6.0f3 / Playmaker 1.8.4).
Both have gone when I playing
Assets/PlayMaker/Actions/Editor/LookAtActionEditor.cs(70,25): warning CS0618: `UnityEditor.Handles.ConeCap(int, UnityEngine.Vector3, UnityEngine.Quaternion, float)' is obsolete: `Use ConeHandleCap instead'
Assets/PlayMaker/Actions/Editor/MoveTowardsActionEditor.cs(64,21): warning CS0618: `UnityEditor.Handles.ConeCap(int, UnityEngine.Vector3, UnityEngine.Quaternion, float)' is obsolete: `Use ConeHandleCap instead'
-
After upgrading the plugin with Unity 5.6.0f3, I´m getting these errors:
Assets/PlayMaker/Actions/SceneManager/Editor/LoadSceneCustomEditor.cs(17,24): error CS0030: Cannot convert type `HutongGames.PlayMaker.FsmStateAction' to `LoadScene'
Assets/PlayMaker/Actions/SceneManager/Editor/LoadSceneCustomEditor.cs(21,15): error CS1061: Type `LoadScene' does not contain a definition for `sceneReference' and no extension method `sceneReference' of type `LoadScene' could be found. Are you missing an assembly reference?
-
Hi,
yes, PlayMaker was updated on the 31st to comply with 5.6 and also the latest version of 5.6 fixed a problem on its own too, so know we should be good for a great 5.6 cycle and looking forward to the new Unity numbering convention :)
Bye,
Jean
-
After I updated today I get this error, not sure why.
PlayerSettings Validation: Requested build target group (27) doesn't exist; #define symbols for scripting won't be added.
UnityEditor.PlayerSettings:SetScriptingDefineSymbolsForGroup(BuildTargetGroup, String)
HutongGames.PlayMakerEditor.PlayMakerDefines:AddScriptingDefineSymbolToAllTargets(String) (at Assets/PlayMaker/Editor/PlayMakerDefines.cs:42)
HutongGames.PlayMakerEditor.PlayMakerDefines:.cctor() (at Assets/PlayMaker/Editor/PlayMakerDefines.cs:23)
UnityEditor.EditorAssemblies:ProcessInitializeOnLoadAttributes()
-
Hi,
this is likely because you need to install the latest version of PlayMaker, the patch is now featured in the official update from the Asset store.
Bye,
Jean
-
this is likely because you need to install the latest version of PlayMaker, the patch is now featured in the official update from the Asset store.
Thank you for the answer. I did update playmaker yesterday as well, took the latest version from the asset store.
-
Hi,
ok, so what target are you publishing for?
Bye,
Jean
-
Windows
-
Hi,
That's odd. Can you try on a new fresh project and import just PlayMaker?
Bye,
Jean
-
Sorry Jean, my mistake. I must have done something wrong while updating, I checked another project and reimported it in my project, now it works.
-
Hi,
good, no worries, the two step update of PlayMaker is sometimes tricky to get right but a necessary evil unfortunatly.
Bye,
Jean
-
Hi, I just recently installed Unity 5 and Playmaker (both latest version). However I keep getting these messages.
Assets/PlayMaker/Actions/Editor/LookAtActionEditor.cs(70,25): warning CS0618: `UnityEditor.Handles.ConeCap(int, UnityEngine.Vector3, UnityEngine.Quaternion, float)' is obsolete: `Use ConeHandleCap instead'
Assets/PlayMaker/Actions/Editor/MoveTowardsActionEditor.cs(64,21): warning CS0618: `UnityEditor.Handles.ConeCap(int, UnityEngine.Vector3, UnityEngine.Quaternion, float)' is obsolete: `Use ConeHandleCap instead'
Judging by previous posts, it seems people who updated experience this issue. But I freshly installed Unity and Playmaker and still get this message. Is there anyway to fix it? I tried to open visual studio and edit but the editor doesn't recognise ConeHandleCap.
Replacing ConeCap to ConeHandleCap seems not working. Is there some solution for it?
Best.
-
Hi,
Which version of 5.6 exactly? I don't get these.
And don't worry to much about obsolete warnings, they won't affect your game at all.
Bye,
Jean
-
Hi,
Which version of 5.6 exactly? I don't get these.
And don't worry to much about obsolete warnings, they won't affect your game at all.
Bye,
Jean
It's 5.6.0f3
I reinstalled Unity several times.
Although it doesn't affect the game but it's annoying to see this message after I launch Unity. I'm just worrying lookat function and movetowards function are not going to work due to error.
Can you send me your LookAtActionEditor.cs and MoveTowardsActionEditor.cs?
Best.
-
Same problem with my Unity 5.6 / Playmaker 1.8.4
-
Hi,
ok, I can repro, I'll fix this and it will be in the next update. I'll put a patch on the forum too.
Bye,
Jean
-
Hi,
ok, Action editors obsolete warning patch is here: http://hutonggames.com/playmakerforum/index.php?topic=14973.0
Thanks for reporting!
Bye,
Jean
-
Thank you for update! It's working now.
-
Hi,
ok, Action editors obsolete warning patch is here: http://hutonggames.com/playmakerforum/index.php?topic=14973.0
Thanks for reporting!
Bye,
Jean
Thanks!
-
Hi!
I just installed the new Unity 5.6.0.f3 (Win10). Download and import the Playmaker (latest version).
I got 2 errors:
Cannot convert type 'HutongGames.PlayMaker.FsmStateAction' to 'LoadScene' ... \PlayMaker\Actions\SceneManager\Editor\LoadSceneCustomEditor.cs 17
and...
'LoadScene' does not contain a definition for 'sceneReference' and no extension method 'sceneReference' accepting a first argument of type 'LoadScene' could be found (are you missing a using directive or an assembly reference?) ... \PlayMaker\Actions\SceneManager\Editor\LoadSceneCustomEditor.cs 21 Active
Any idea?
-
Hi,
The Api Updater from Unity likely did not trigger.
Can you reimport all from the Unity "Assets" menu?
Bye,
Jean
-
I downloaded the new 5.6.1 patch and playmaker auto updated and moved the dlls somewhere else. Now all actions give an error that its missing an assembly reference and I get FileNotFoundException: Could not load file or assembly 'PlayMaker, Version=1.6.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies.
Also TypeLoadException: Could not load type 'HutongGames.PlayMakerEditor.ActionReportWindow' from assembly 'PlayMakerEditor, Version=1.6.0.0, Culture=neutral, PublicKeyToken=null'.
System.MonoCustomAttrs.GetCustomAttributesBase (ICustomAttributeProvider obj, System.Type attributeType) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System/MonoCustomAttrs.cs:108)
System.MonoCustomAttrs.GetCustomAttributes (ICustomAttributeProvider obj, System.Type attributeType, Boolean inherit) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System/MonoCustomAttrs.cs:151)
System.MonoType.GetCustomAttributes (System.Type attributeType, Boolean inherit) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System/MonoType.cs:595)
UnityEngine.AttributeHelperEngine.CheckIsEditorScript (System.Type klass) (at C:/buildslave/unity/build/Runtime/Export/AttributeHelperEngine.cs:131)
-
I deleted and re-downloaded playmaker and it works now... Be careful when auto updating your playmaker project after you update 5.6.1!