Avatar

Level 3

Thanks Nigel

Thats sounds great - I am really commited to trying to get this to work efficiently on AFCS.

You are right - I could send objects instead of Shared Properties per coordinate:

Just to give you an overview of my setup ( where SP = Shared Property :disappointed_face:

Player One: SP (y-coordinate)

Player Two: SP (y-coordinate)

Ball: SP(x-cordinate), SP(y-cordinate)

Scores: SP(Player One), SP(Player Two)

So I can see that I can reduce the ball to be one object. I can't see anywhere else to reduce the payload as the rest are independant.

- I am sending through 'Player One' and 'Player Two' y cordinates whenever the player moves there bat up or down.

- I am sending x,y cordinates for the ball whenever it moves.

- The height of my application is 300 pixels, the width is 600 pixels

So to me it seems quite possible that I could be sending through 10000 messages per game since each time the player moves their bat down the screen, 300 messages will be sent regardless. And the same with the ball, at least 600 messages will be sent each time it traverses the screen.

I could reduce the size of the playing field to half leaving perhaps 5000 messages per game. I could also increase the distance between sending coordinates to some level but this would create a 'less smooth' response.

Any suggestions are welcome - thanks.