Please help PS3 graphic problems

[Rivienne]

@Rivienne

Offtopic: how do you get more than 1000 characters?

Type up your entire response, then create a placeholder post with 10 characters . Edit, and paste your whole text then save. The 1000 characters is only for the original post. Edits allow much bigger.

On topic: explain how this is client side...

Common problem for me: I'm standing in Revenant Toll, choco summoned, waiting for a FATE. Fate pops, I start running towards it. I have both my macro (server side) map and micro (client side) map up. On the macro map, I can see my choco following me. On my mini map, choco is still standing next to aetheryte munching greens. I go back to get my choco because I can't see him follow me on mini map and sure enough, there he is. So I run off again, no choco. But on the macro map he is following me. Screw it... I do the fate and strangely my choco is healing me. That's because he is there, I just can see him because server hasn't told client to update location. Client thinks it is still at the last place it got a location update.

Hit post to soon. Misunderstood question, rewriting an answer for you.

EDIT: I made the mistake(since it cut into my play time) of looking at your problem the way I would tackle solving an obscure infrastructure problem for a contract, and I just spent 2 hours working on a logic chart of the various branches of your situation, and what it implied, and which branches would mean server, and which client. I realized there is no way I am cleaning up and posting that thing in here, even assuming anyone wanted to read it. So.. I will summarize a few key points for you and hope I am coherent about it.

1) In an environment like this the server doesn't constantly push data to the client so much as the client pushes data to the server, and in return requests other data/updates, which the server sends back in reply. That is, if the server isn't returning something, it means either the client isn't requesting it, or the server isn't returning everything the client requests. There are lots of variables involved here, but suffice to say, if you are correct that the macro map is getting the choco position from server data, then we already know the server is returning the positional data when requested, meaning the fault is almost certainly on the client.

2) If you are wrong about that, then there is still only one rational case (apart from the chocobo issue being its own unique bug) that would put the blame partly on the server, instead of all on the client. You got me thinking however, and I will not discount the possibility. It would still be the same core problem however, of prioritization. It would just mean that the fault was the way the server prioritized objects to return to the client, rather than being just the way in which the client drew the objects the server returned. I.E. Server capped objects based on client request, didn't 100% make sure key objects got returned, client culls objects further when it can't cope with the full list returned.

Short of it: it probably isn't server, but if it is it is almost certainly still the same object prioritization issue I keep bringing up, it just might be partly server side object prioritization, instead of all client.