| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Fixes mantis 771 - multiple uses of llListen cause duplicate events
Thanks Michael!
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
OpenSim.Framework.Communications.Limit
|
| |
|
| |
|
| |
|
|
|
|
| |
revision
|
|
|
|
|
|
|
|
|
|
|
| |
* This means that caps methods (editing scripts, poss map functions, etc) on non-home regions should now work with servers which are listening for http ports on a non default
(9000) port.
* If you are running a region server, this may only work properly once your grid server upgrades to this revision
* PLEASE NOTE: This shouldn't cause inter-region problems if one end of the connection hasn't upgraded to this revision. However if it does, the instability will persist until
the grid and region (and possibly all the region's neighbours) have upgraded to this revision.
* This revision also adds extra login related messages, both for success and failure conditions
|
| |
|
|
|
|
|
|
|
| |
box. (previously it crashed my simulator)
* Found and gracefully handled a few situations where null references occur. (m_rootPart again!)
|
|
|
|
|
|
| |
* It's not perfect, but it's good enough. (rarely erroneously returns a backface collision)
* After updating to this revision, rez a prim on another prim and watch it appear where you'd expect it to appear.
|
|
|
|
| |
llAddToLandBanList, llAddToLandPassList, llResetLandPassList, llResetLandBanList
|
| |
|
|
|
|
| |
Thanks daTwitch!
|
| |
|
| |
|
| |
|
|
|
|
| |
issue worth fixing.
|
|
|
|
| |
was trying to look up
|
|
|
|
| |
SceneCommunicationService.EnableChildAgents so we can see what hostname is failing
|
|
|
|
|
|
|
|
|
|
| |
'already dispatched' message completely temporarily
* I believe that if the Linden client has not started to receive a texture after 15 seconds, it re-requests it.
* My hypothesis is that the texture packets are often still in the texture queue (esp. if the client has just cleared its cache), so another load of packets get added...
* If this is the cause, resolution is going to be rather complicated.
|
|
|
|
|
|
|
|
| |
requests for missing textures
* Also minor logic change so that we actually do retry missing texture requests (we weren't before)
|
| |
|
|
|
|
|
|
|
|
| |
execute a deprecated one
* As per CharlieO's suggestion in #806. Thanks!
|
|
|
|
|
|
|
| |
it into planes and normals.
* No obvious functionality difference as the Ray-cast code is incomplete for OBB right now.
|
|
|
|
|
| |
This takes us down to 15 compiler warnings on a VS2005 C# build.
|
| |
|
| |
|
|
|
|
| |
when we start dropping requests
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
n=5), we now drop the subsequent requests
* This may improve region memory usage
* This is a short-term response to a problem whereby some clients keep requesting the same texture even after we've sent it
* This treats the symptom rather than the cause.
* n can be adjusted by changing the constant at the top of UserTextureDownloadService if necessary
|
| |
|
|
|
|
|
| |
an "Exception e" with e.ToString() to eliminate 2 warnings.
|
| |
|
|
|
|
| |
the information for the argument key, opposed to the object the script is in.
|
|
|
|
|
|
|
|
|
| |
vector components of the scale have a difference of less then 4.5 meters.
* When a new prim is created and raytracing is called for, raytrace from the camera position to the ground in the direction of the Norm(RayEnd - RayStart).
* If we got a hit based on our camera, create the new prim at the edge of the prim we hit.
* Don't raytrace if the difference between any component of the vector exceeds 4.5meters.
|
| |
|
| |
|
|
|
|
|
|
|
| |
* We should not be using ASCII anywhere except for legacy compatibility reasons.
* A large number of UTF8 Encoders are being used in places where we should be using Util.StringToField instead. These have been tagged with // ENCODING FAULT
* This should fix Mantis#799 - Japanese Profile Text does not work.
|
|
|
|
|
|
|
|
| |
script that works OK on SL
* Fix for #693: llSetRot malfunction in linked prims causing instance of invisible prim
|
|
|
|
|
|
|
|
|
|
|
|
| |
non-home regions
* Should work in multi-region standalone and grid modes
* This should also solve other non-home region caps issues (map requests, RC client inventory requests, etc)
* We now pass CAPS information on to the destination region on region crossing, and set up a CAPS object when an agent becomes a master
* Current limitation is that this will only work if your http_listener_port is 9000
* This is a very early code cut (lots of bad practice, hard coding and inefficiency). However, I wanted to get this out there for feedback and my own sanity. Next few patches will clean up the mess.
|
|
|
|
| |
packetpool, which somewhere through time got lost/reverted
|
|
|
|
| |
commented out) to find out what CAPS is doing
|
| |
|
|
|
|
|
|
|
| |
* This reveals that the problem with saving scripts in a non-home region in multi-region configurations is due to a CAPS setup issue
* For some reason the client is still using the CAPS on the region it just came from, causing the ScenePresence lookup to fail (since the presence is now, correctly, a child agent).
|