The demo plays well - good job! Perhaps post a few screenshots of the FSMs. Nice clean, legible graphs re-assure potential customers that they can understand how the kit works so they can tweak it etc.
Also PM me if you want access to the Playmaker Beta - we encourage publishers making Playmaker starter packs to sign up for the beta to check for any problems with updates before we release them…
That’s a solid idea! I’ve got them all queued up. Doesn’t make much since to hoard them while I wait for the Asset Store acceptance email. I’ll gather them up and post them this evening.
Hey there! I’ve found a solution to the problem. Not the grandest solution, but from what I’ve been able to gather the globals assets needs to come from the same playmaker version or it gives me a “No Globals to Import” error.
That being said, the error you are getting is the FSM action on the camera can’t find the Game Object that is stored in the global variables. So! The solution is one of two ways.
You can download the unitypackage I’ve uploaded here. And use the Playmaker Import Globals in the Playmaker > Tools menu to import that Unity Package. Don’t just drag and drop this in. Won’t work that way.
You can double click the globals asset Unity package that is downloaded through the asset store to import the PM Globals Asset. This is the work around part. You then export that newly created item as a separate Unity Package. And then follow step 1 to import the Globals. Run the scene all should be peachy!
I’ll update the package on the Asset Store so this doesn’t happen with 1.8.2 and continue to look for a better solution for these variables.
thanks to your fast reply.
Unfortunately, can’t import PM global variables.
first ways…import by playmaker>tools> Import Globals
then occured popup No globals to import!
console log is
and second ways .
popup Import Unity Package message is
so… don’t solve this problem.
but… i’ll wait update your version.
thank you.
Double click the UnityPackage that is included in the download. This will create a PlaymakerGlobals_Exported file.
Click on this newly created file, and scroll to the bottom of the inspector.
If you use the import Globals button in this object, and choose the UnityPackage that created the PlaymakersGlobal_Export file. Playmaker will recognize the global variables and your errors should go away!
