Hi Karl,
When this stops working, can you check the xengine status in the console?
I see the results you have included here, but is this before or after
the communication stops?
We had a similar issue back in December on 3rd Rock Grid and when things
stopped working, checking the xengine
This dump is after the issue presents itself and it's not showing any
scripts waiting for load. That's what is really strange. They
all work perfectly for an underterminate amount of time then, a random
subset of them just stop.
I will point out that when I adjusted
the max_listens_per_script
Hi Karl,
I think since your xengine status results show you are only using 2
threads.. I'm not sure it would do you any good to increase max threads.
~Butch
On 6/1/2015 12:53 PM, Karl Dreyer wrote:
This dump is after the issue presents itself and it's not showing any
scripts waiting for
Do you know whether it's the listener or the sender which is failing? Also,
I've heard there are problems with llSleep() so if any of the scripts are
using that it might be contributing to the problem.
On Mon, Jun 1, 2015 at 10:06 AM, BoneZ bo...@dogzhouse.com wrote:
Hi Karl,
I think since
Actually, it is definitely the listener that is failing. The reason why I say
that is because when the failure occurs; it doesn’t only effect the
“server/client” prims.. but any script using a listener on the sim.. such as
MLP’s .. the menu comes up but the script never “hears” the reply.
It’s difficult to say… I would think the ending behavior would be the same
either way. What I do know is when run on a different sim with zero or less
scripts; the behavior is as expected. I will have him check to see if he is
using the llSleep command in his scripts.
From:
