playMaker

Author Topic: MORE update troubles  (Read 2303 times)

markfrancombe

  • Sr. Member
  • ****
  • Posts: 338
MORE update troubles
« on: June 23, 2013, 02:50:21 PM »
Why do I have so much trouble EVERY time I update PlayMaker?

So now I have all these... (See image)

What can I do? I dont understand ONE THING here...

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 15500
  • Official Playmaker Support
Re: MORE update troubles
« Reply #1 on: June 24, 2013, 02:51:04 AM »
Hi,

From what I can see you have a versionning problem with photon. It looks to me you have downloaded Photon asset package on its own and it's now obsolete in some part.

Delete the photon Unity networking folder all together and reimport playmaker.

bye,

 Jean

markfrancombe

  • Sr. Member
  • ****
  • Posts: 338
Re: MORE update troubles
« Reply #2 on: June 24, 2013, 05:49:53 AM »
Hi,

OK, Great.. but just to clarify, do you think that my old projects that used this old version of Photon will continue to work, after doing what you describe? Or do I need to start again from scratch?

Mark

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 15500
  • Official Playmaker Support
Re: MORE update troubles
« Reply #3 on: June 24, 2013, 06:19:06 AM »
Hi,

 no no, here in your case, it's simply a mix up of version ( I am guessing, but this is typical given the errors you have).

 if you stick to PlayMaker release, then photon will update as it should. Importing manually the photon network system is not needed here ( and is prone to such merging issues). The photon networking system it evolving very quickly so it's safer if you stick to the version that is supported by PlayMaker.

here is how I do it ( when I do it :) )

1: back up your project as a zip and store it ( if you rely on svn or rep, you don't need this if you can come back to a previous milestone or commit)
2: duplicate your project and test everything in that duplicate
3: if 2: works fine, implement it in your working project

Point number 2 is easier cause you don't mess any rep or svn, so you don't pollute your working project until you are certain it all updates fine.

bye,

 Jean

bye,

 Jean

bye,

 Jean