playMaker

Author Topic: Missing Reference for Playmaker FSMs with Perforce Source control.  (Read 1943 times)

fromfame

  • Junior Playmaker
  • **
  • Posts: 82
  • Sloppy PM Veteran
Greetings,

I am currently using perforce for source control and we are a team of two. my partner (programmer) never gets my Playmaker FSMs despite having strict prefabbing rules and constantly checking out & saving any thing we change in the depot.

he always sees a missing reference exception instead of the playmaker FSM component on the objects i manipulate via visual scripting.

he even tried saving the state machines as templates but still it leads to the same missing reference exception problem.

my question is, what is the correct workflow for using play maker under version control as we are both new to this, how do you save and share ur fsms and where should u save your templates?

Alex Chouls

  • Administrator
  • Hero Member
  • *****
  • Posts: 4254
  • Official Playmaker Support
    • LinkedIn
Re: Missing Reference for Playmaker FSMs with Perforce Source control.
« Reply #1 on: August 26, 2015, 10:30:10 PM »
A PlayMakerFSM is a regular MonoBehaviour, so there's shouldn't be any special workflow required.

Are you checking in .meta files when you make changes?
I assume Playmaker is part of the project - can you edit PlayMakerFSMs in your partner's project?
Are you both using the same version of Unity? What version? (There was one 5.x update that seemed to break a lot of references).