aboutsummaryrefslogtreecommitdiffstatshomepage
Commit message (Collapse)AuthorAgeFilesLines
...
* | limit number of prims on physical objects. Not all cases covered stillUbitUmarov2014-09-085-3/+78
| |
* | on drop send full update on root prim, terse on others ( as sl ). FixUbitUmarov2014-09-081-2/+5
| | | | | | | | count down of number of physicial prims on attach, if removing them
* | change attachment drop, to make object Phanton. THis is not as SL, butUbitUmarov2014-09-081-8/+12
| | | | | | | | | | rez position is automatic and object interpenetrations will happen including with the avatar, with the usual ugly effects.
* | *NEEDS more testing* on attachment drop: fix adding prims to physicsUbitUmarov2014-09-081-4/+31
|/ | | | | | | engine, remove disturbing phantom flag. On attach: fix removing prims from physics engine, delete any keyframeMotion, remove physical flag. This is executed in all attachs possible only need on attach from the scene (?), but its where original code removed only root part from physics engine
* do not send objectproprieties on sop.SetGroup(). I many cases this willUbitUmarov2014-09-051-2/+2
| | | | arrive before creating the object in viewer with respective full update
* near region check on tp needs to be a full current view check.UbitUmarov2014-09-051-6/+6
| | | | sp.KnownRegions is unreliable for this.
* reduce MIN_CALLBACK_MS guard time. A value too high introduces a extraUbitUmarov2014-09-021-1/+1
| | | | | throttle and makes more packets to be sent in bursts and not in steady state flow.
* void time change between gettime callsUbitUmarov2014-09-021-4/+3
|
* *needs testing, not that good* change throttles math using floats and notUbitUmarov2014-09-024-125/+112
| | | | | int64, etc. Limite brust bytes to the total rate client requested times a look ahead estimation time, Avoid queues starvation with updates waiting...
* make use of it in GetMeshModule, and meshs are Assets not Task itens,UbitUmarov2014-08-291-43/+4
| | | | reduce MeshModule impact on udp rate
* add method to get a category throttle rateUbitUmarov2014-08-296-38/+53
|
* reduce burstUbitUmarov2014-08-291-1/+1
|
* replace the tick() by a limit on the maximum number of tokens that can beUbitUmarov2014-08-292-15/+39
| | | | acumulated ( variable named BurtRate, not exactly a rate...)
* disable first dripUbitUmarov2014-08-291-1/+1
|
* try to reduce insane high data rate udp bursts. This needs testing on aUbitUmarov2014-08-282-1/+11
| | | | region with a lot of contents. Should not affect much average rates.
* remove misplaced commentUbitUmarov2014-08-281-1/+0
|
* try to make sense of throttle rate limitsUbitUmarov2014-08-282-4/+15
|
* add some functions for estimation of number of bytes that can be send in a ↵UbitUmarov2014-08-282-0/+13
| | | | category in specified time
* send all presences terseupdates in same batchUbitUmarov2014-08-281-3/+3
|
* if we send wearables with ThrottleOutPacketType.HighPriority, then weUbitUmarov2014-08-282-125/+18
| | | | should send other avatarinformation with same priority on same Task category ( plus cleanup )
* try to make child presence know its root region. Incomplete, some paths ↵UbitUmarov2014-08-282-43/+15
| | | | dont send the information.
* dont create a cadu that is not used. Add a root region global positionUbitUmarov2014-08-271-9/+27
|
* dont mess throotles values sent to child presences. Some cleanupUbitUmarov2014-08-271-53/+38
|
* Merge branch 'ubitworkmaster'Melanie Thielker2014-08-275-41/+95
|\
| * enqueue also if m_nextPackets[category] is not null. This is really theUbitUmarov2014-08-271-4/+8
| | | | | | | | | | top element of a category queue, equivalente to using a queue.peek() if avaiable
| * bug fix. Was not deleting attachments if on public parcelUbitUmarov2014-08-271-2/+6
| |
| * on TPs to nearby regions, only send kills if needed by parcel privacyUbitUmarov2014-08-272-13/+37
| |
| * dont append acks to a resend packetUbitUmarov2014-08-261-1/+1
| |
| * still testingUbitUmarov2014-08-261-28/+28
| |
| * even less kills on tpsUbitUmarov2014-08-261-1/+2
| |
| * *test* back to no sog kills, little retouch on attachment updates,UbitUmarov2014-08-252-5/+5
| | | | | | | | NameValue AttachItemID is a root part thing only
| * *test* cleanup the bugs nestUbitUmarov2014-08-251-6/+8
| |
| * change enconding of attachment updates NameValue and State fieldsUbitUmarov2014-08-251-0/+19
| |
* | Merge branch 'ubitworkmaster'Melanie Thielker2014-08-258-460/+571
|\ \ | |/
| * back to just killsUbitUmarov2014-08-251-1/+0
| |
| * *test* send kills and hackUbitUmarov2014-08-251-0/+3
| |
| * put back the kills on tp where they belongUbitUmarov2014-08-241-6/+1
| |
| * *test* move sending kills to before sending the update, this breaks tpUbitUmarov2014-08-241-1/+4
| | | | | | | | abort
| * clean sendKill a bit, remove a IsChild that is set too early in a callingUbitUmarov2014-08-242-24/+17
| | | | | | | | path
| * send avatar kills after attachments, send otherattachments before rest ofUbitUmarov2014-08-231-3/+4
| | | | | | | | sog ( updates will mess this again but well... )
| * on updates, send rotations using livomv Quaternion.toBytes() againUbitUmarov2014-08-231-4/+2
| |
| * Remove entities from updates queues on kill. Do it sync so enqueues afterUbitUmarov2014-08-232-0/+21
| | | | | | | | the kill work
| * back to sending attachment sog kills in place of the hack. This is theUbitUmarov2014-08-231-5/+8
| | | | | | | | official way of doing it
| * sop SendFullUpdate() goes by presence if it is a attachmentUbitUmarov2014-08-222-8/+39
| |
| * some cleanup ( well or not )UbitUmarov2014-08-225-81/+234
| |
| * Merge branch 'master' into ubitworkmasterUbitUmarov2014-08-221-0/+5
| |\
| * | revert the kills, they seem even worseUbitUmarov2014-08-221-8/+3
| | |
| * | silly...UbitUmarov2014-08-221-2/+2
| | |
| * | replace hack by sog kills on tp outUbitUmarov2014-08-211-1/+15
| | |
| * | make the hack more extensive. Forbid sog/sop updates if Intransit butUbitUmarov2014-08-211-8/+13
| | | | | | | | | | | | release it sooner