A bit Late, where waiting for new version.
I have done the test with 1926de5a0599051c27c065fb06da3dc536e6784a :
[r/19477] now.
and sofar i can fly safe around the 4 regions and simsquare metaverse
astro and astro sea appear fine to.
I have btw now compiled opensim myself, seems to work much better.
On 2012-06-09 03:33, Justin Clark-Casey wrote:
Interesting, I visited those regions on OSGrid and saw exactly this
problem. However, I tried to reproduce this on my local network with
two different machines (one running 4 regions and the other 2) and
could not - the necessary regions reappear correctly as the avatar
moves around.
However, this was with latest dev code. So if you can, I would
suggest waiting to see if the next osgrid distro improves the
situation since there have been some small changes, though these
shouldn't really impact this stuff. Also, if this has been happening
since the 05-20 version then that was before the recent agent transfer
changes.
When the avatar comes back into the regions neighbouring astro and
astrosea, you should see message in their consoles about child agents
being established, and a "show users full" command on the console
should show child agents for that avatar in those regions (as they
would when you initially teleport to the neighbouring region).
If this is still happening with the next osgrid distro I would suggest
filing a mantis with the relevant log sections from both simulators as
the avatar moves around the regions.
On 08/06/12 15:40, R.Gunther wrote:
Small correction, i run the latest osgrid 06-02 version.
But have seen same problems with 05-20 version.
On 2012-06-08 13:44, R.Gunther wrote:
On 2012-06-08 05:38, Justin Clark-Casey wrote:
>How are these regions laid out spatially?
The region layout is as follow,
4 3
2 1
Below nr. 2 is simsquare metaverse astro sea.
Below nr. 1 is simsquare metaverse astro
Further are around it other regions not from me. above 4 & 3 looks
like dead sims or not responding.
I have also tried a slow simborder crossing with a long delay. (a
minute or so.
after crossing from 4 to 2 i saw astro & astro sea appear, but the
viewer still kicked me out.
>Are these regions running the latest osgrid distribution?
Right now i run osgrid.opensim-06022012.v0.7.4.729d901 but it
happend with the latest osgrid 06-20 version to.
When i have time i need to upgrade again.
>Did this happen immediately after you updated? What happens if you
go back to a previous distribution?
Hard to say, i switched the last time a few times between linux &
windows.
But i remember me something that i crashed more in the past in that
corner.
>Are you in a position to try the latest git master, which has some
changes to client mgmt though in theory nothing
that should affect this?
Sorry justin. running windows, still need todo my first opensim
compieling in that. For now i cannot run latest version.
Hope you have some usefull information.
On 07/06/12 13:44, R.Gunther wrote:
I see since yesterday a weird problem. and possible before to.
when i fly around a few sims. in this case simsquare metaverse
1,3,4,2 (in that order)
then when am in simsquare metaverse 2, i dont see anymore
simsquare metaverse astro & astrosea.
If am waiting long enough on simsquare metaverse 2 i crash in the
viewer !
when i teleport quick to the other sim at the other side, named
simsquare metaverse orion.
then simsquare metaverse astro & astro sea are still gone. also
when i fly to neighborn sim.
Now the intressting part, sometimes it works to teleport to plaza
and back.
But in this case the teleport to wright plaza failed and got aborted.
After the aborted teleport, simsquare metaverse astro & astrosea
came automatic back.
I get the feeling that somewhere after simborder crossings a
mention is not established or cant get established.
And idea if am overlooking something ? or am flying into some bug ?
Someone else test the same and when she entered simsquare
metraverse 4 she crashed to after a while,
can create bad neigborn simns this problem to ?
I use singularity as viewer, but have seen the same problem with
old imprudence 1.4b2
_______________________________________________
Opensim-dev mailing list
Opensim-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/opensim-dev
_______________________________________________
Opensim-dev mailing list
Opensim-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/opensim-dev
_______________________________________________
Opensim-dev mailing list
Opensim-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/opensim-dev
_______________________________________________
Opensim-dev mailing list
Opensim-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/opensim-dev
