playMaker

Author Topic: General Unity Exporting  (Read 2870 times)

mweyna

  • Full Member
  • ***
  • Posts: 242
General Unity Exporting
« on: March 08, 2014, 07:45:52 PM »
So when I hit PLAY in Unity, everything works fine no issue. The window resolution is set to 1024x768 and all my UI elements line up fine. However, when I export the project to either Web or a standalone exe with the exact same resolution, the window scale seems seems off and about half my playmaker scripts (that all worked fine when run through Unity) do no work. Any idea the cause of this?

mweyna

  • Full Member
  • ***
  • Posts: 242
Re: General Unity Exporting
« Reply #1 on: March 08, 2014, 09:08:45 PM »

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 15500
  • Official Playmaker Support
Re: General Unity Exporting
« Reply #2 on: March 11, 2014, 07:46:59 AM »
Hi,

Can you paste the console text in clear? I can't really read anything from that screenshot unfortunatly.

bye,

 Jean

mweyna

  • Full Member
  • ***
  • Posts: 242
Re: General Unity Exporting
« Reply #3 on: March 13, 2014, 03:32:41 AM »
So the common ones I get -

HutongGames.PlayMaker.FsmState.OnEnter ()
HutongGames.PlayMaker.FsmState.ActivateActions (Int32 startIndex)
HutongGames.PlayMaker.Fsm.UpdateStateChanges ()
HutongGames.PlayMaker.Fsm.Update ()
NullReferenceException: Object reference not set to an instance of an object
NullReferenceException: No AstarPath object found in the scene. Make sure there is one or do not create paths in Awake

Again when run through Unity via the Play button no problems, just whenever I build it.

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 15500
  • Official Playmaker Support
Re: General Unity Exporting
« Reply #4 on: March 13, 2014, 03:48:40 AM »
Hi,

Your problem begins earlier on with AstartPath not found, this is the root of your problem. Likely a setup that is different when running published than in editor. You should contact the author of your aStar solution to get more insight on this.

bye,

 Jean

mweyna

  • Full Member
  • ***
  • Posts: 242
Re: General Unity Exporting
« Reply #5 on: March 13, 2014, 11:23:01 AM »
So all the playmaker errors are a result of the the Astar problem?

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 15500
  • Official Playmaker Support
Re: General Unity Exporting
« Reply #6 on: March 14, 2014, 12:51:23 AM »
Hi,

 not necessarly a fault within it but at least the log says:

No AstarPath object found in the scene

so this is where you need to start debugging, what is this object, why it's not there and how to create it.

Typically, you should first try to see if you can reproduce this error in Unity editor, if you can, then it's going to be easier than if it only happens when published.


bye,

 Jean

mweyna

  • Full Member
  • ***
  • Posts: 242
Re: General Unity Exporting
« Reply #7 on: March 14, 2014, 04:01:19 PM »
So I'm a bit stumped. Looking at the Editor, it appears everything works fine. Only when I export does my A* totally seem to fail to exist (as if it's not being exported at all). Since the playmaker actions don't totally support the new version of A* it's become a bit of a blocker. How exactly would I go about debugging why my existing A* is or isn't being exported?

mweyna

  • Full Member
  • ***
  • Posts: 242
Re: General Unity Exporting
« Reply #8 on: March 17, 2014, 04:20:46 PM »
So I fixed it by just copying and using the A* setup object from the pathfinding scene, seemed to resolve all my problems. Not sure why, but solved.