Some residents dont see what others can see

I have developed a game which has caused me some concern.
When the board rezzes the pieces before play begins some residents can't see the pieces while others and myself can see them clearly.
Now I don't think this is a scripting problem but what could cause it and which forum should I post this problem?

Are they using the same version of the viewer? Well, more to the point, are any of them using WindLight? And if so, at what altitude? (Yeah, I know that sounds insane, but the current WindLight viewer has a problem with forgetting to render some objects, some of the time, which happens more at higher altitude.)

The point being that if the invisibility problem is *only* in the WindLight viewer, I'd just ignore it and hope it goes away (possibly scanning the long list of outstanding WindLight bugs to make sure whatever's happening is already reported).

Thanks for the response. I suppose with optional viewer updates this is inevitable. I will have to ask the residents involved and then pursue the matter.
Thanks.

heyas;

how small are the pieces? some small prims don't render at some far distances at some graphics settings. that is, they only appear on your screen if you zoom in close to them. (lod and all that.)

While I agree the that size matters, these pieces are 0.120 meters in diameter and 0.03 thick. As other residents and I have no problems I can only assume that the problem is with the resident's viewer.

I have now found out that the resident who is unable to see the generated pieces is using the standard viewer 1.18.5 (3) so that can't be the cause.
Has anyone other ideas why?

Does he have high packet loss? The sim is constatly sending updates to his viewer. If those updates are getting lost, he won't see things. Ask him to TP away, and then back.

Try it in an area that is very simple. If the sim is full of objects of all sorts, he might not be seeing lots of things and not knowing it.

lee

And how high is his draw distance? Suggest that he at least temporarily decrease it to minimum (64) so that his client is only requesting what's in the immediate area.

I did try to ask him those sort of questions but I am not sure he understands. What criteria would you use to measure packet loss?

How do you change the draw distance?

Disregard my last I have found out how to do it

for those that don't know... the little red bar in the upper right corner of the viewer shows packet loss.... it maxes out at 3.5-3.8% packet loss, but if you stick the mouse pointer over it, it will show the actual percentage (I've seen 83% before a crash)

Someone's not running the latest client. =)

Also, it seems like things have been taking a lot longer to rez after login and teleport since they did that last asset server upgrade. Past week or so?

The "small prim effect" also seems exaggerated lately. I've had 4 cases the past 2 days where people couldn't see prims that I could because they were too far away for the client to bother rezzing for them.

Guilty as charged, I thought they'd already gotten that put back (it's a Jira issue) although technically I am running the latest client, I just have Nicholaz viewer on top of it =)

I believe it's also accessible from the ctrl+shft+1 menu, under network I think

I have been through the investigation with the user.
He is using Windows XP on a core duo processor fitted PC utilising NVidia 7600GT graphics with the latest drivers. He can see the pieces in my game if they are rezzed as a group while still linked but not when the are rezzed and link is broken by script. Other user present sees the pieces without any problem. User failing to see the pieces individually has packet Loss of 0.0% and uses a draw distance of 128. He was asked to change temporarily to draw distance of 64 with no change. He was asked to use camera view and zoom in on the location of the pieces and still could not see them.

I am at a loss what to try next, HELP PLEASE.

Please ignore my previous post.
I was lead to look at the Technical Issues forum by someone offline and the number of 7600 driver problems is astounding.
I have referred the user to this forum for him to check which of the many failing drivers he has loaded. What he does about it though is a problem.
Thanks for reading.