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 ... 211
Playmaker Bug Reporting / Re: Itween bug in 1.9.0.p4
« on: July 23, 2018, 12:21:53 PM »
You need to import iTween separately from the Asset Store. If you import iTween from PlayMaker > Welcome Window > Add-ons you should get a popup dialog telling you to do this. But I assume you found the unitypackage and imported it directly? I'll add a readme to that directory for people who skip the Add-on manager. Thanks for reporting this.

Playmaker Bug Reporting / Re: Improved prefabs
« on: July 23, 2018, 12:17:08 PM »
I'm still on 5.6.5, I'm see a problem with prefab and callmethod. the callmethod keeps breaking whenever I edit. Is this a known issue with prefab?

I'm not aware of an issue with prefabs and CallMethod in other versions of Unity. Check that you have the latest version of Playmaker. If you're having this issue with the latest version please start a new thread (since it's not related to the new unity prefab workflow) and we'll figure out what's going on... thanks!

Sorry to hear that :(
Have you tried updating to 1.9.0?

Playmaker Bug Reporting / Re: Problem in 2018.2.0x Improved Prefabs
« on: July 18, 2018, 09:22:43 AM »
Thanks for trying this out. Are you in the PlayMaker Beta Group? PM me if you would like access... we should be working through this in a beta soon...

Playmaker Help / Re: Return value from FSM templates
« on: July 16, 2018, 11:07:04 AM »
We're adding Output variables to templates in the next update.

PM me if you're interested in joining the beta group.

Playmaker Bug Reporting / Re: ActionHelpers.cs Build Error
« on: July 13, 2018, 11:55:03 AM »
Have you updated to 1.9.0.p4? That patch should fix .net building for HoloLens.
Note: Remember to import and then install the update. Check the version in Main Menu > PlayMaker > Help > About PlayMaker

Pre-release Discussion / Re: Math Expression action
« on: July 12, 2018, 06:05:46 AM »
Yes, I'll send you a PM.

From the error, it looks like it could be a problem with the Get Property action and stripping.

Take a look at this thread to see how to fix issues with build stripping:

Playmaker Bug Reporting / Re: ActionHelpers.cs Build Error
« on: July 04, 2018, 10:38:30 AM »
Thanks for the update! I'll get a fix for .net into the next update - sorry about that! I think Player Settings defaults to il2cpp now, so I didn't catch it...

Playmaker Bug Reporting / Re: ActoinHelpers.cs Build Error
« on: July 03, 2018, 06:24:05 AM »
Are you able to build for Hololens without Playmaker imported? Just a new Unity project, maybe with a standard asset to test.

Playmaker Bug Reporting / Re: ActoinHelpers.cs Build Error
« on: July 02, 2018, 11:45:57 AM »
I haven't built to hololens yet, I'll need to investigate and setup the tools etc.
Are you able to build an empty project for hololens? Installed all the correct sdks etc.?

EDIT: Just made a build for hololens here without a problem.

Playmaker Bug Reporting / Re: ActoinHelpers.cs Build Error
« on: July 02, 2018, 07:57:16 AM »
What platform are you building for?

Hi, can you confirm what version of Playmaker you're using?

Are you using the Run FSM action? It should say Show instead of Edit when the game is running...

Playmaker Help / Re: Reserved names for states?
« on: June 21, 2018, 10:16:17 AM »
Hi, there are no special state names. Not sure why you're seeing that behavior - I just tried here and was not able to repro. Are you using any global transitions, Goto State actions, custom actions, scripts that could be causing those state transitions...?

Action Requests / Re: Get Property, Set Property, Send Message etc.
« on: June 20, 2018, 04:10:13 PM »
Some guidelines:

- If there is a custom action that does the same thing, use that instead.
- If you are getting/setting a property once (not every frame) it's probably fine.
- If you are doing it every frame, it might still be okay, but it's more likely to affect performance.
- Test on the target device as early and often as possible.
- Profile on the target device to find the bottlenecks and fix those.
- Don't optimize prematurely - but also don't leave it to the end!

It's a balance between getting stuff done and optimizing. My personal philosophy: The biggest risk with any game is that it's not fun! Use every tool you have to figure that out first. You don't want to waste time optimizing systems you will later scrap or rework.

EDIT: We also have some ideas to optimize these actions, but that's still a little bit down the line...

Pages: [1] 2 3 ... 211