Proper documentation would be nice, easily overviewable and perhaps illustrated pdf form.
I'm at a loss here... given that the pack was rejected before for not having adequate help material, i was under the impression that the 5-6 page text file would have been enough.
Images in asset store are somewhat misleading with the models depicted, as they are not included. Not that I need them, but it sort of leads one to think here is a package with some substatial help scenes included which could aid learning.
I'll update the images to post a disclaimer. that said, always check the pack contents window on the asset store. you can get a preview of a lot of the things in the packages with that window.
Like I said I was mainly looking for a simple player and camera setup, but found the framework appearing to be too dense or integrated to just pick out single elements without studying the whole package and mindset behind it, before being able to extract what I need.
Can't really help with that... it is the way it is because i needed to incorporate a good amount of error catching and redundancy (mainly with the automatic collection of data such as player objects and other gameobject variables which it'd need to function correctly) so as to make this approachable from as many different levels of experience with PM as possible. as such, i had no other choice but to try and make it as compact as possible. if you pick it apart you can learn from it just make sure you have your own work backed up first because when the pack gets updated with adjustments if need be, updating it will overwrite your own data if you do not make the objects unique themselves. (basically, don't dissect the original pack objects, make clones, make them unique and then work on the unique prefabs. that's one of the tips i mentioned in the second help file as well as mentioned in the help file itself.)
Oh and I get a :
_player : Setup and Movement : Weapon Parenting : SetFsmGameObject : Could not find variable: _player
What is this?, I'm using PM 1.5.6 btw
Yeah, just updated to the most current Playmaker and it's also throwing that error as well for me. (Well, a warning, not an actual "error" error.)
Doing some troubleshooting right now to see why this error is cropping up. since it was not throwing this error with the older version of playmaker, i've got to figure out what differences there are between the two... i suspect it's only with the FSM get/set actions since those are the only ones throwing an error. as it is, however, those are only warnings at this point and as far as i can tell, it's still working... but i'll have to do a thorough check and re-check to see why this is happening (which might be tricky since i have to check it pre-update and post-update for PM.)
As far as i can tell, it seems that the differences is that the actions that are throwing the errors for some reason have changed the naming of the variables between PM installs... So, previous versions it's looking for the "_Player" variable but in the updated one, some of the values are looking for "_player" (the get/set actions are case sensitive... so, this one change is causing problems.)
I'll see about adjusting it... hopefully it can be resolved soon but I don't know how much of this i'll be disrupting with the changes (often simple issues tend to become larger issues given how closely knit a lot of the actions are.)