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 ... 208
Sorry, there's no way to do this right now. But I've added a foldout button to collapse the info box in the next update. PM me if you want access to the beta.

Playmaker Help / Re: Playmaker broken with unity 2018.1+
« on: March 11, 2018, 12:13:50 PM »
To work with the 2018.1 beta please delete the Assets\Playmaker\Actions\ProceduralMaterial folder.

Unity removed built-in support for Substance materials in the 2018.1 beta, and Allegorithmic has yet to release their plugins, so these actions are not currently supported in 2018.1.

Note we can't always guarantee that Playmaker will work with Unity beta versions. But we appreciate you letting us know when stuff breaks!

I've been playing around with a Math Expression action that uses the Mathos Parser:

The parser was pretty easy to setup as a Playmaker action (attached), but I haven't done a lot of testing yet - consider it alpha software!! Please post bugs/feedback and we'll see if it might be a viable solution to release...

Also, the parser is very extensible - we can easily add custom functions and variables e.g., to access things like Time.deltaTime in the expression.

I think it's worth exploring other options as well to compare performance, usability etc.

Playmaker Help / Re: Playmaker 1.8.4
« on: March 04, 2018, 09:18:36 PM »
Hi, you can use your original download link to get the latest version. I might have missed your mail, if you need your download link resent please email again, or PM me here.

Playmaker Help / Re: Playmaker 1.8.5 doesn't work in Unity 5.6.1[SOLVED]
« on: February 27, 2018, 03:53:27 PM »
Weird. What version of Playmaker were you downloading?

It could be an asset store bug in that version of Unity.
If you have another version installed, you could try downloading in that version (e.g., Unity 5.4)

Unity has confirmed this is an issue with the current Asset Store. Unfortunately, it seems they don't have plans to fix it anytime soon given their response:

It was marked as "Wont fix" for now and will be touched once revamping the whole Asset Store in the next couple of years. We are sorry for inconvenience.

Playmaker Help / Re: Purchased, errors on a fresh new project ?
« on: February 27, 2018, 03:40:09 PM »
From the error it looks like it's because of this Asset Store bug:

Please re-download Playmaker in the version of Unity you want to use to get the correct package. Use the Asset Store download manager to manually download the asset.

If that doesn't fix the issue let us know!

Try adding and removing an action from the FSM. Can you think of anything that makes this FSM different? Are you able to share the project (e.g., to send me a private download link)?

Try loading those FSMs in the editor, make a small change (e.g., move a state), then save.

So you don't get the "FSM updated..." message when loading the scene in the editor? Whenever you see "FSM updated...", at runtime or in the editor, it means the loading code had to do more work to update the FSM data. Try running: Tools\Update All FSMs in Build.

You get "FSM updated please re-save the scene/project" if any actions have changed since the FSM was last saved (or if the data needs to be resaved for some other reason, e.g., the data layout changed in an update).

It's a good idea to re-save when you see this message since old data has to go through slower loading paths to recover parameters and update the data. You should definitely re-save before shipping anything.

It's a good idea to use the Linker Wizard on any platform that strips "unused" classes/methods/properties from the build. It may look like everything is working, then you hit that one Set Property action that rarely gets called and it breaks your game because the property was stripped. Better safe than sorry!

Got this from Unity:

Thanks for the report.
This issue is already fixed, by cause of il2cpp and Timeline in 2017.3.0p3.

You can track original case's status here:

Strange. I can repro in 2017.3, but it builds fine in other versions, including the 2018.1 beta. So there's something broken in 2017.3. Unfortunately, the error is not that helpful, and I can't repro in the source code project to get any leads. But I've submitted a bug to Unity and pinged a contact I have on the il2cpp team, so maybe they can help.

Have you tried any of the patch versions for 2017.3?

Hi, try replacing the line with:
Code: [Select]
var behavior = (PlayMakerGUI)component;
Not sure why it would fail on PS4, but the code is a little messy. I'll clean it up for the next update.

This is a bug in 1.8.8 when updating FSMs made in a much older version of playMaker. Fix is tested and should be up soon. Sorry for the inconvenience!

Ok, the new version is up. Please re-download. Sorry for the inconvenience!

Pages: [1] 2 3 ... 208