Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - kdsh7

Pages: [1]
Playmaker Announcements / Re: Unity 5.6 Beta Patch
« on: March 19, 2017, 12:13:09 PM »
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:

Code: [Select]
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)

Playmaker Announcements / Re: Unity 5.6 Beta Patch
« on: March 19, 2017, 04:29:31 AM »
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!

Playmaker Announcements / Re: Unity 5.6 Beta Patch
« on: February 27, 2017, 03:50:59 AM »
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.

Playmaker Announcements / Re: Unity 5.6 Beta Patch
« on: February 24, 2017, 02:48:02 AM »
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.

Playmaker Announcements / Re: Unity 5.6 Beta Patch
« on: February 21, 2017, 02:39:44 PM »
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..

Playmaker Bug Reporting / Re: Load Level action
« on: March 13, 2012, 05:17:10 AM »
aha! Just noticed there's a "Reset On Disable" toggle in the FSM settings. That fixes it. Hopefully this'll help somebody else.

Playmaker Bug Reporting / Re: Load Level action
« on: March 13, 2012, 04:57:13 AM »
I've been having this issue too - does this mean that having the FSM control level loading still isn't possible? Playmaker seems perfectly suited for organising levels and game flow so it'd be a real shame if we couldn't use it for that!

Pages: [1]