playMaker

Author Topic: IOS publishing notes  (Read 39801 times)

gecko

  • Junior Playmaker
  • **
  • Posts: 52
Re: IOS publishing notes
« Reply #15 on: October 24, 2013, 10:15:06 AM »
Thanks, I'll try that.

gecko

  • Junior Playmaker
  • **
  • Posts: 52
Re: IOS publishing notes
« Reply #16 on: October 29, 2013, 06:28:31 PM »
Quote
I set to 0 all acceleration on the component itself, so external acceleration and random acceleration are both 0,0,0

then I don't do anything in the "start low" state, I wait for 5 sec and then set big values and it works.

I finally tried this in a build, but no improvement. Now the flag is drooping (zero acceleration of any kind), and it never changes. No errors in the editor, nothing in xcode console. Here's the FSM:

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 15500
  • Official Playmaker Support
Re: IOS publishing notes
« Reply #17 on: October 30, 2013, 01:20:04 AM »
Hi,

 Can you create a new topic on this? this thread is actually about generic notes, thanks.

 Bye,

 Jean

thinias1900

  • Playmaker Newbie
  • *
  • Posts: 4
Re: IOS publishing notes
« Reply #18 on: January 15, 2014, 01:22:16 PM »
Hi.  Sorry to revive an old thread, but I am getting this same error when attempting to use the GetProperty method:

ExecutionEngineException: Attempting to JIT compile method '(wrapper delegate-invoke) System.Reflection.MonoProperty/Getter`2<Interaction, UnityEngine.GameObject>:invoke_GameObject__this___Interaction (Interaction)' while running with --aot-only.

  at System.Reflection.MonoProperty.GetterAdapterFrame[Interaction,GameObject] (System.Reflection.Getter`2 getter, System.Object obj) [0x00000] in <filename unknown>:0
  at System.Reflection.MonoProperty.GetValue (System.Object obj, System.Object[] index) [0x00000] in <filename unknown>:0
  at HutongGames.PlayMaker.ReflectionUtils.GetMemberValue (System.Reflection.MemberInfo member, System.Object target) [0x00000] in <filename unknown>:0
  at HutongGames.PlayMaker.ReflectionUtils.GetMemberValue (System.Reflection.MemberInfo[] memberInfo, System.Object target) [0x00000] in <filename unknown>:0
  at HutongGames.PlayMaker.FsmProperty.GetValue () [0x00000] in <filename unknown>:0
  at HutongGames.PlayMaker.Actions.GetProperty.OnUpdate () [0x00000] in <filename unknown>:0
  at HutongGames.PlayMaker.FsmState.OnUpdate () [0x00000] in <filename unknown>:0
  at HutongGames.PlayMaker.Fsm.UpdateState (HutongGames.PlayMaker.FsmState state) [0x00000] in <filename unknown>:0
  at HutongGames.PlayMaker.Fsm.Update () [0x00000] in <filename unknown>:0
  at PlayMakerFSM.Update () [0x00000] in <filename unknown>:0
 
(Filename:  Line: -1)


I have verified all of the properties mentioned, except for SymLink... which no longer exists.  Does this mean I can't use PlayMaker on iOS anymore?  Is there a new workaround?

Any assistance would be greatly appreciated!

thinias1900

  • Playmaker Newbie
  • *
  • Posts: 4
Re: IOS publishing notes
« Reply #19 on: January 15, 2014, 08:35:42 PM »
I was able to resolve the previously described issue with JIT reflection by setting my Api Compatibility level from .NET 2.0 to .NET 2.0 Subset.

memetic arts

  • Full Member
  • ***
  • Posts: 141
Re: IOS publishing notes
« Reply #20 on: March 30, 2016, 03:28:42 PM »
Hi all -

Bumping this thread as it has gone a bit stale, given that Unity, XCode and iOS have progressed . . . wondering if anyone knows of any build optimization tips that might be helpful.  I'm submitting an app in approx. two weeks, and any final optimization tweaks would be gladly welcomed.

Bonus points for tips on optimizing assetbundles in iOS.

Thanks very much!

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 15500
  • Official Playmaker Support
Re: IOS publishing notes
« Reply #21 on: March 01, 2017, 12:59:16 AM »
Hi,
 
What exactly in this thread is at stale? Publishing to IOS works well, if you have trouble don't hesitate to create a dedicated post with your issue and ping me after few days if you haven't got any replies :)

as for optimization tips, prefer using custom actions over actions such as "SetProperty", "GetProperty","InvokeMethod", etc they use reflection and could be a bottleneck if your game is already reaching limits in terms of graphics and shaders. Apart from that, refer to Unity own tips really, there isn't much within PlayMaker for optimizing, the real deal is to profile oftento detect perfs issues as soon as possible, else it's a nightmare... with or without PlayMaker :)

Bye,

 Jean