Google Play - Accept Invitation - nothing happens

When I receive invitations and read them, i am listing them on the screen. That works.

I have a button to accept invitation by Invitation ID - when pressed, I'm executing Accept Invitation and passing the ID string.

I have tried doing Show Waiting room after this - nothing happens

I have tried doing On Room Created > show waiting room - Nothing Happens

I feel like I'm missing something here, but I don't know what it is - I don't want to open the Invitations UI (that defeats the purpose of a programmatically called "accept invitation".

How do I proceed after accepting the invitation? Shouldn't the match start if I send the Accept Invitation and ID?

can you post a small mfa and put a bug report for this to check your implementation.

i can do that - but even your example app does the same thing - Invitations show up - but clicking Accept invitation does nothing. I'll put something together and submit bug request... i just hoped i was doing something wrong...

The help file does explain the flow of what's needed to do a proper Accept Invitation.

I assume that from one device the invitation is sent - i can do a send via the Invitations UI -

I can READ invitations and loop through them - and add them to a list file

But when I accept the invitation - shouldn't the match start for both players? the match is never triggered.

Same situation here - were you missing something Tuna?
Or was there some issue with the GPG Multiplayer object?

Has this issue been sorted?


(I would be fine with the invitations UI, if not for the emulator,
which (due to bad resizing in portrait mode) refuses to show the "accept" button on invitations and I can't test the app :()

Did you update GPG object from clickstore?

====

sorry typo

Mmm good advice, I seem to remember I did some time ago, but maybe too much time ago XD

Going to check out and report back, thank you!

Awesome - that was it, now works like a charm X)

Thank you Fernando!

By the way, a question on the Multiplayer object,
i think an example would make my question clearer:

say I have 5 players,
2 or more players send a datastring in the same instant to all (other) players
(not an unlikely scenario in real time multiplayer)
so that each player receives 2 or more datastrings in the same frame cycle.

I can think of three scenarios:

1) are these packets stacked/buffered, so that you will receive all of them but with some delay (like 1 x frame)?

2) are the "overlapping" packets lost?

or

3) is the "on data received" event capable of handling more than one datastring x frame cycle? (how?)

you filter all data so this should not happens, you get an event for each one, since is pushedEvent, but "same time" is real life is not possible, at least with one loop of difference.

Thank you for the quick answer.

I was thinking this could happen in a "many players" scenario,
say I send movement updates each time some player modify its status
(i.e. moving/not OR directional change, a string like this: ID|angle|speed)

I have 8 players moving and turning around,
sure, very hardly all 7 could send the data at the exact same moment,
but maybe among the 7, with all them pushing keys and turning around quickly,
just a couple overlaps in timing could happen,
and my app running at 30 FPS (so making "only" 30 on data received calls x second) would make it a bit more likely

I seem to understand I would receive them as two different events in two different frame loops?

I think nothing that dramatic would happen... but looking at ways to optimize and avoid bottlenecks in the multiplayer architecture

what are ur player doing , if is position, any new message from a player override the position, BTW the message are order according the time they were received.

did you try the example named "Test MultiPlayers" try add 8 gamer and see how it work.

see that message are coded by you so they won't be mixed and loose them.

I've already set up the system and it works nicely,
(congrats for the great suite of GPG objects you provided us, btw! :D)

I'm just looking to understand the whole process to make sure I'm using the best possible way
to minimize lag and optimize gaming experience
(es. I'm already interpolating positions when predicted movement is off by a number of pixels etc.)

Of course I'm not sending raw x,y positions every frame cycle,
otherwise I would flood the communication with a huge data stream,
I'm sending direction and acceleraion changes,
(whenever a player starts/stops moving, whenever a player changes direction)
works quite nicely, minimum lag so far.
However, I'm only able to test on two devices, two players, currently.

So I was thinking at possible issues on additional players.

Another "extreme" example:

say I have an event (which I don't have XD, but just to explain)

always >>> send my X,Y position to all

each player would be always (30 times x second) sending a datastring like ID|X|Y
to all other players

so the "on data received" of each player,
polling the received data at the same frequency of 30 times x second,
even if there is a "push", that's anyway the max frequency the app can poll,
so it would easily receive something like this,
from all (or let's say "some" of the) other peers in the same frame cycle:

1|X|Y
2|X|Y
3|X|Y
4|X|Y
5|X|Y
6|X|Y
7|X|Y

in short, it would find a number >1 of datastrings when it polls for new data
...am I wrong?

then what would it output?
a random datastring among the ones received?
would buffer datastrings? (but how to buffer if the stream is constant?? some package has to be lost)


Again, my system obviously does not work like this, always sending data,
so this scenario is far less likely to happen,
but unless there's some logical flaw in my understanding of the process,
I can see as some overlap among received data (more than 1 message received at the same time) could occur
..and was wondering what would happen in such cases.

mm, don't know if I get your idea, hope I do, but this amount of data is not much really, hard is how you as dev handle this data, (your example is the best "always") guess that if you receive a message and stop everything to attend the position this will cause a problem, what is pain in real player is if one or two of the gamer have slow connection and that for the others user will delay their position or any information from them.


the way you are conceptualizing your game for movement, using somehow a vector and speed is a wise manner to handle this, and each game will certainly require a specific way to do it


here is something that I always said through all post, use "always" wisely.

I think I've failed to explain myself clearly X) - sorry.
But nevermind - there's high chance this can be considered nitpicking I guess.

I'm fine with what I'm having so far, if I ever get into the problems I was speculating above,
I will come back and try to explain myself better, and provide some real-use example/data.

Thank you very much for you time, informations and tips :)