playMaker

Author Topic: Common Problems & Solutions repository?  (Read 2174 times)

Lane

  • Administrator
  • Hero Member
  • *****
  • Posts: 2484
  • Yup.
    • View Profile
    • Cleverous
Common Problems & Solutions repository?
« on: February 19, 2014, 01:52:19 PM »
Should we create a section on the Wiki for Common Problems and their solutions? There is currently a Troubleshooting section but it seems geared more towards errors, crashes, build fails, stuff like that.

Often there are problems posted on the forum repeatedly and sometimes we forget that it has been resolved before or where exactly the answer was located.

When we start making more tutorials this list might help drive that repository as we could get a good idea of what kind of issues need to be covered or clarified.

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 12342
  • Official Playmaker Support
    • View Profile
Re: Common Problems & Solutions repository?
« Reply #1 on: February 24, 2014, 06:34:24 AM »
Hi,

 Yep. this would be great. I have tons of custom samples, that I would like to properly list, if they could be linked to common problems that would be good.

the issue, everytime I wanted to start such section is the wording. It's tricky, cause "common problems" known to people can be expressed in many different ways by the person who is facing this problem, because of lack of vocabulary or else, so very tricky situation for proper and clear referencing.

bye,

 Jean

Lane

  • Administrator
  • Hero Member
  • *****
  • Posts: 2484
  • Yup.
    • View Profile
    • Cleverous
Re: Common Problems & Solutions repository?
« Reply #2 on: February 24, 2014, 06:45:12 AM »
That's true.

I was thinking about that when labeling the new tutorial and how to approach the next ones. Should it be "How to do xyz" or "How to use action xyz" or even "How to approach designing xyz"?... They all could be the same thing, but every person would be looking for a different answer, some might want to know how to use an action, while others want to know how to do 'something', but not know that the same action would be the answer.

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 12342
  • Official Playmaker Support
    • View Profile
Re: Common Problems & Solutions repository?
« Reply #3 on: February 24, 2014, 06:50:26 AM »
Yep...

 that's why the community is important here.

I think the starting point would be to properly extract the various samples and provide them as clean, well documented sources on the wiki, and then in each post reference them as opposed to attach them, which is good for a certain level of usage but the forum is growing exponentially and so things needs to be done in a different way now.

So, what about a Custom samples section we would put on steroids. I have 100's of samples in a project dedicated to playmaker support, they should go on the wiki really. Actually, they should go in a rep so that one day we can pull them with a custom editor right from within Playmaker! Same with custom actions...


bye,

 Jean

Lane

  • Administrator
  • Hero Member
  • *****
  • Posts: 2484
  • Yup.
    • View Profile
    • Cleverous
Re: Common Problems & Solutions repository?
« Reply #4 on: February 24, 2014, 07:05:43 AM »
That seems like it would be a good step forward. If you've got all these examples then it makes sense to store them somewhere with documentation so users can access them and being able to fetch them from within Unity would definitely be the most convenient way for them to do it!

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 12342
  • Official Playmaker Support
    • View Profile
Re: Common Problems & Solutions repository?
« Reply #5 on: February 24, 2014, 10:58:14 AM »
Hi,

 Yep :)  :'( not enough time during the day....

 Ok, so on my side, I will create a rep and start uploading all my custom actions and custom samples, then we can take them when needed, prettify/document them with their wiki page counter part. And the key would be to add the new wording or approach angle that lead to that example for one reason or another.

Like I did on the coming soon GameAnalytics playmaker support, all Fsm wiki pages have references to each actions use and each events, and so you can find all fsm using a particular action easily.

The big plan for this Unity editor integration would be that the wiki page content is programmatically defined so that all cross referencing is done automatically, meaning in turn that if you download a custom sample, you would also download each individual custom actions needs. Something like that in theory.

bye,

 Jean