Third Party How to Synchronize an animation of a second Layer with Photon ?

Hi,
I'm making a TPS multiplayer with Photon but i'm stuck trying to synchronise all my animations over the network.
Animations in the Base Layer are corrected synchronized but I've got a throwing animation in a second Layer wich is not.

Please HELP !

 

Hi,

are you synchronizing the layer weights aswell? I always forget to check if the layer weight on the remote object is set properly and the animation just doesn't play if the weight is 0

 

HI Oliver,
I'm sorry but I'm nub, How should I do this ? Because I set the second layer to 1 and my problem still the same :
my animations works but I don't see the throwing animation of an other player in the network.

Thanks for trying helping me.

 

ManitoBart, thanks for the tweet, but sadly I've not used photon enough to be of any real help.

There are a few dedicated (and official?) threads on the forum by the photon folks. Try to find them and post there is one suggestion. Search for photon in either the search box in the header or google. :-/

Another is to join the photon forums and ask your photon questions there.

Sorry I can't be a specific help.

 

Ok,

I already tried to ask on Photon forums here :
http://forum.exitgames.com/viewtopic.php?f=17&t=5488&p=21294#p21294

But I do not have a solution yet,

if there is a way without photon I'll take it. I use photon because it seems to be more easy for me.

Thanks you all anyway,

 

Thanks Adam and Will!

In this case, @Oliver Eberlei is "the man".
He knows this specific feature better than me but is a bit slower to respond (maybe this nag helps).

 

I've got some kind of progress with the new PhotonAnimatorView but it is not working perfectly, my animation is now played half the time.

 

It's really tough to give any type of feedback based on the information you provide.

How are your animators setup?
What code are you using to trigger the animation? Locally and Remotely?
Did you check if the layer weights of remote objects are also set to 1? Open the animator view, select a remote object (one that another client controls, not the unity editor) and inspect the layer weights of this object. It shows up in the animatior automatically if you've selected the GameObject with the Animator component attached to it.

 

I found a solution but without photon.

Thank you anyway !

 

Hi, I don't know why there's no documentation on the PhotonAnimatorView class.

When is it going to exist?

Also, could you design the PhotonAnimatorView class to support children Animators instead of having to put a PhotonView and PhotonAnimatorView on the children?

 

@MidgardDev: We can at least take a look about children.
However, we get a lot of requests for features and in the end, we can't implement everything. There is the code of the PhotonAnimator. We give this out deliberately, so you can extend and modify it as you need to. Go and make use of that.

Did you find these pages?
http://doc.exitgames.com/en/pun/current/tutorials/rpg-movement
and
http://doc.exitgames.com/en/pun/current/tutorials/mecanim-demo

 

Thanks for the info, yeah I didn't find these pages!

And I also understand that you can't implement everything, it just seemed like PhotonAnimatorView wasn't yet completed and ready to use

No problem now. again thank's for the reply.

 

Don't get me wrong: I appreciate the input. We never thought about the child animators and we will check this out when Oliver has some time again.
I just can't promise anything at the moment.
Thanks for the nice reply

 

You don't need to add a PhotonAnimatorView AND a PhotonView to the children. Since the new version you can add multiple components to be observed by a single PhotonView. Just add a PhotonAnimatorView to each Animator you want synchronized and add those components to the observed list of the original PhotonView.

Adding child support to PhotonAnimatorView would make it very complex and difficult to read because in that case the PhotonAnimatorView and the Animator would be on different GameObjects. I feel like having the PhotonAnimatorView on the same GO as the Animator makes it easier to debug in case something goes wrong. It would also be very difficult to keep any references to child animators if you start moving them around in the objects hierarchy. By having them on the same GO this will never be an issue.