I recall it being something like that too where it is something like a 16bit integer and when the distance was over 4096 it overflowed and was truncated.
On Mon, Apr 29, 2013 at 2:33 PM, Teravus Ovares <[email protected]> wrote: > When I reported this on the linden Jira years ago.. I suspected it was > probably the viewer failing to compare numbers in scientific notation with > numbers that are not in scientific notation. Unfortunately, it was closed > and not fixed.. so here we are :). One thing to note is the 4096 number > seems to be when the meter count flips into scientific notation. > > Best Regards > > Teravus > > > On Mon, Apr 29, 2013 at 3:38 AM, Ai Austin <[email protected]> wrote: > >> Thanks Dahlia. The explicit limit was added by Diva to try to make lie >> easier for users/avatars getting stuck in limbo, but can be turned on and >> off with an OpenSim.ini parameter, default being that it is on. So it can >> clearly be removed. Now there is a distinct branch for some viewers like >> Firestorm, and that there are already improvements in Firestorm 4.4.0(OS) >> to improve the OpenSim experience, some critical issues like zthe rally >> panful and awkward to explain to new users 4096 jump issues just might now >> be on te cards to be fixed. >> >> I am sure if this were technically possible in commonly used LL viewers >> with an Openim specific branch then the OS server side default setting for >> the 4096 jump restriction could simply be set as OFF by default rather than >> ON by default? >> >> >> On 28 Apr 2013, at 20:59, Dahlia wrote: >> > There was a time when libomv based viewers could teleport beyond 4096 >> and >> > still function correctly, however since then someone added some code to >> > OpenSimulator to prevent *any* viewer from teleporting beyond 4096. >> While >> > this effectively prevented the viewing failures experienced with >> LL-based >> > viewers, it also prevented anyone from being able to fix the problem >> from >> > the viewer side. Given that libomv-based clients did not have the >> problem >> > suggests that it's likely entirely withing the LL codebase. >> _______________________________________________ >> Opensim-users mailing list >> [email protected] >> https://lists.berlios.de/mailman/listinfo/opensim-users >> > > > _______________________________________________ > Opensim-users mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/opensim-users > -- Michael Emory Cerquoni
_______________________________________________ Opensim-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-users
