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 - Alex Chouls

Pages: [1] 2 3 ... 230
With official actions, we try to wrap only the part that's missing in a define, so the action is still present even if it doesn't work.

For example, Unity 2019.3 makes MovieTexture obsolete, so the next Playmaker update will wrap MovieTexture actions like this:

Code: [Select]
// (c) Copyright HutongGames, LLC 2010-2020. All rights reserved.

#if UNITY_2018_2_OR_NEWER
#pragma warning disable CS0618 


using System;
using UnityEngine;

namespace HutongGames.PlayMaker.Actions
#if UNITY_2019_3_OR_NEWER
    // Mark Obsolete but keep parameters
    // so user can convert them to new actions.
    [Obsolete("Use VideoPlayer actions instead.")]
[Tooltip("Plays a Movie Texture. Use the Movie Texture in a Material, or in the GUI.")]
public class PlayMovieTexture : FsmStateAction
#if !UNITY_2019_3_OR_NEWER
public FsmObject movieTexture;

public FsmBool loop;

public override void Reset()
movieTexture = null;
loop = false;

public override void OnEnter()
#if !UNITY_2019_3_OR_NEWER
var movie = movieTexture.Value as MovieTexture;

if (movie != null)
movie.loop = loop.Value;

#if UNITY_2019_3_OR_NEWER
        public override string ErrorCheck()
            return "MovieTexture is Obsolete. Use VideoPlayer actions instead.";


The action is still there with Obsolete warnings. But you can still see the parameters to see what the action was doing and convert it to a VideoPlayer action.

The key is to wrap only the unsupported parts, not the whole action.

Hi, that doesn't sound good! What versions of Playmaker and Unity are you using? Are you able to share a project where this happens? If so can you PM me a download link?


General Discussion / Re: PlayMaker Error
« on: January 09, 2020, 12:18:21 PM »
Are you installing from the Asset Store?
You may be running into the Asset Store bug where it imports the wrong version for the current version of Unity. More info and solution here:

I didn't even know about that video, thanks ToxicFrog!

You should be able to use PlayMaker > Tools > Export/Import Globals to merge globals from another project. Export Globals in the old project and use Import Globals in the new project to merge with existing Globals.

Let me know if you run into problems with this and I'll take a look...

PlayMaker Announcements / Re: Hutong Games is hiring!
« on: January 07, 2020, 03:13:35 PM »
Yes, it would be making the kind of composite screenshots that are on our Showcase page. It would be advantageous to know PlayMaker since you often need to re-create FSMs to take higher-res/nicer screenshots - so we thought we'd reach out on the forums :)

PlayMaker Announcements / Hutong Games is hiring!
« on: January 07, 2020, 12:19:35 AM »
We’re looking for an artist/graphic designer who knows Playmaker and can work remotely. Contract position only, please send enquiries with your cv/work samples to, subject line - ArtMaker 

What version of Unity and Playmaker?
You can find out the full Playmaker version info in PlayMaker > Help > About
Can you also report a bug using PlayMaker > Tools > Submit Bug Report.
That will give us more info to track down the issue.

User Showcase / Re: Legendary Assassin KAL - free to play mobile game
« on: December 29, 2019, 09:46:29 AM »
Great art style and looks fun - I'll check it out! :)

PlayMaker Bug Reporting / Re: Can't Install Playmaker on 2019.2.9f1
« on: December 09, 2019, 04:18:35 PM »
Also, check this Troubleshooting page:

And the installation guide:

If none of that helps, please post any errors you're seeing in the Unity Console.

Can anyone still seeing this post the full Playmaker and Unity version info found in the About windows. Also if you can submit a bug report it will give us more system info to help us track down the issue. Thanks!

What versions of PlayMaker and Unity are you using?

FSM xxx: yyy: zzz should give you the GameObject : FSM : State path to help you find the error.

You can also try opening PlayMaker > Editor Windows > Editor Log.
The log entries in that window should be clickable so you can go straight to the error.

Can you copy/paste the first error in the list of errors you get when selecting one of those states? The full error in the console should have more info to let us figure out what's going on...

PlayMaker Help / Re: Playmaker window is not appearing in Unity
« on: August 27, 2019, 06:23:34 AM »
There shouldn't be a problem with scripting runtime 4.x.
What's the full Playmaker version in PlayMaker > Help > About.
Also the full Unity version (it may be an issue with a specific version of Unity).

PlayMaker Help / Re: Constantly updating the Actions window
« on: August 24, 2019, 09:21:06 AM »
Does it happen in other projects?
Are you able to share the project?
If so, please PM me...

PlayMaker Help / Re: Constantly updating the Actions window
« on: August 24, 2019, 08:39:00 AM »
Strange. I haven't seen this before.
Does it stop if you re-boot Unity?

Can you open PlayMaker Editor > Preferences > Experimental
and check that Error Check Timeslice is 100 and Action Usage Timeslice is 50.

You could try raising these numbers. E.g., make Action Usage Timeslice 200.

If that doesn't work, you could turn off "Auto Refresh Action Usage" in the Action Browser settings (the small gear in the top right corner).

In the next update, the progress bar is on the same line as the search field, to avoid the list jumping up and down when updating. But I'd still like to figure out why this is happening...

Pages: [1] 2 3 ... 230