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 - GaTechGrad

Pages: [1]
PlayMaker Help / Re: Playmaker broken with unity 2018.1+ [SOLVED]
« on: May 08, 2018, 03:55:42 AM »
All of my PlayMaker projects appeared to be broken after updating Unity to 2018.1.0f2 (release version).  I also tried making a blank Unity project, imported PlayMaker from the asset store, and still received errors.

Using the suggestion to delete Assets\Playmaker\Actions\ProceduralMaterial seemed to make the errors go away for one of my projects, and got things back to a somewhat workable state.  I had to pull PlayMakerGlobals.asset from my source code repository and put in it Assets\PlayMaker\Resources to get the globals working again.  A couple of the parameters in the PlayMaker GUI had to be redone, but it wasn't too big of a problem.

On other project, I just had to delete the ProceduralMaterial folder and it was working again.

PlayMaker Help / Re: On Collision Enter Does not work!
« on: October 29, 2017, 11:55:55 PM »
In the past I have seen the internal Tags asset get corrupted... try adding another Tag to refresh it.

I had an old Unity project from two years ago using Playmaker that I was trying to recompile tonight.  The game would play fine in the Unity editor, but collisions didn't work anymore after building for Windows.  After spending a few hours trying to figure out the problem, I found this thread.  When I opened the tag editor, there were missing tags, which showed up as "Removed Tag".  I added and assigned all new tags, and now collisions are working after building for Windows.

Share New Actions / Re: Axis Event extended: 8 ways direction support
« on: June 09, 2016, 12:04:35 AM »
The Axis Event Extended action with the Discrete Event option enabled was exactly what I needed to handle gamepad input for my latest puzzle game.  The only problem I had was that if I pressed in one direction multiple times, then the event would only fire once.
I looked at the source code for the action, and I noticed that the currentDirection value is only set when OnEnter is called.  Since the state only changed in my FSM when the joystick axis was moved in a direction, the OnEnter method was not getting called again when the same direction was pressed multiple times in the same direction.  This is because the currentDirection variable in the action did not change after the joystick moved back to the neutral position.  With Discrete Events enabled, the direction event only gets fired if the currentDirection variable is different from the direction being pressed.
To fix this, I created an event (I called it doNoDirection) which I set to the No Direction dropdown for the action, and I made a transition that loops back to its own state.
Now, for instance, if I press right twice on the game pad, the right event fires, then the no direction event fires (looping back to the state which invokes OnEnter, resetting the currentDirection variable), then the right direction fires again (since the current direction is set to no direction, which is different from right).
I hope that makes sense, and I just wanted to share in case anyone else was having the same problem.

Windows Store Apps Help / Windows Store errors with Unity 5 on Windows 10
« on: September 06, 2015, 01:09:21 AM »
I am having issues on Windows 10 with Unity 5 and Playmaker.

I can compile a new plain Unity 5 project without Playmaker for Windows Store with no problems and publish it to the Windows Store.

When I import Playmaker ( from the Asset Store, I can build a "Windows Standalone" (Target Platform: Windows, Architecture: x86) with no problems.

However, if I switch platforms to "Windows Store" (SDK: 8.1, Unity C# Projects: checked, Development Build: unchecked) with Playmaker imported, it will start to compile and hang on "Compiling Scripts", and then return with 999+ errors.  In the Console output, I see many errors such as:

Code: [Select]
Assets\PlayMaker\Actions\ActivateGameObject.cs(9,36): error CS0246: The type or namespace name 'FsmStateAction' could not be found (are you missing a using directive or an assembly reference?)
Again, this is a new plain Unity project with only Playmaker imported.  I tried using both 64-bit and 32-bit versions of Unity 5 (5.1.3f1).  Building the exact same project with Playmaker for Web Player or PC Standalone there are no errors and the executable runs with no problems.

I am using Visual Studio 2015 Community to build the .appxupload package for Windows Store, which works fine for the Unity Windows Store build without Playmaker imported.  With Playmaker imported, it doesn't even get to the point where it generates the files to be opened with Visual Studio.

After looking at some of the other threads, it looks like I may need a limited beta to publish to Windows Store.  Is that correct?


Update: I installed Unity 4.6.8, and it would compile my project with Playmaker, but there were still errors.  It did generate the files for Visual Studio, but Visual Studio returned errors when I tried generating the .appxupload file.  At this point, the only thing I haven't tried is downgrading my OS to Windows 8.1.

Pages: [1]