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.

Topics - GaTechGrad

Pages: [1]
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]