If by 64k you mean 64,000 then the maximum range you can teleport without graphical disruption is 4096 regions. To
prevent faulty teleports, OpenSim prevents teleports beyond this range, though the error message is not very good for
technical reasons. Hopefully this will be improved soon.
I know this check occurs on HG but I'm not sure exactly what happens on a non-hg configuration. However, I'm guessing
this is the same kind of problem.
On 21/06/11 06:39, Jeroen van Veen wrote:
Hey Justin,
When i try to tp to a region with one axis> 64k, the imprudence(1.4) viewer
returns:
"Could not teleport. The region you tried to teleport to doesn't exist
anymore".
Latest snowglobe has the same issue. There is no feedback from the simulator
or robust service besides the search-operation for the region in the map(which
is ok). It's not that i want to run a large amount of regions, rather i would
like to combine two map-layers; single os-region tiles with openstreetmap-
tiles, based on their shared grid locations at zoomlevel 17 or 18, which
require a gridaxis of 2^17. Like if i wanted to create a region on top of some
location in the netherlands, then it would require a grid-location which is
larger than 64k at each axis.
The tile-renderer thats part of hwios now, works for quite some time already.
It was tested succesfully on os-grid tiles some time ago. It works in
openlayers, kde marble and in viewer 2(using the mapservice uri, but without
the osm-layer), but if one can't tp to the regions> 64k in-world, then it
doesnt make much sense to try to mashup both osm and os.
I tried to avoid the error in the past, by introducing mapping offsets, but
that would complicate things alot. The use of this 1-1 mapping approach is
that you always know the rl osm tile thats linked to a region, so you can for
instance get the osm tile on a 256x256 prim and show where rl roads and
buildings are supposed to be in-world. If this feature would work, it would be
possible to introduce a mapping client like marble inside of a viewer, or use
geodjango on top of hwios for AR-related stuff.
kind regards,
Jeroen
On Tuesday 21 June 2011 01:09:52 Justin Clark-Casey wrote:
Hi Jeroen. You don't say what happens when you try running a grid with 132
x 132 regions. I'm guessing the main map doesn't display properly.
Running that many regions on a single simulator would be a problem in
itself. You may also want to try viewer 2 with the very latest code since
Diva recently implemented the viewer 2 map approach here and it works
differently from viewer 1.
On 16/06/11 08:10, Jeroen van Veen wrote:
Hello,
I've been wondering for a long time what prevented the use of really
large grid locations. My use-case is using the opensim map as an overlay
on openstreetmap with 17 zoomlevels, which is a 2^17(131.072x131.072)
grid-sized map. I've tried in the past, and it looks to me that it's a
viewer issue? Any idea if this is going to be an easy fix on the viewer
side, or whether opensim needs some changes as well?
kind regards,
Jeroen
_______________________________________________
Opensim-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-dev
_______________________________________________
Opensim-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-dev
--
Justin Clark-Casey (justincc)
http://justincc.org/blog
http://twitter.com/justincc
_______________________________________________
Opensim-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-dev
