opensim-SC - My fork of OpenSim for IG and DG, called SledjChisl.

	Commit message (Collapse)	Author	Age	Files	Lines
*	a few changes on priority queues and their heap	UbitUmarov	2019-01-25	1	-36/+25
\|
*	changes to objects updates prioritizing getting dust on my disk. Schemes ↵	UbitUmarov	2018-11-07	1	-52/+95
\| \| \| \|	reduced to SimpleAngularDistance and BestAvatarResponsiveness
*	SimpleAngularDistance update prioritization scheme ameks no sense without ↵	UbitUmarov	2017-07-10	1	-0/+21
\| \| \| \|	ordered dequeue of the updates
*	Massive tab and trailing space cleanup	Melanie Thielker	2017-01-05	1	-12/+12
\|
*	several changes related to culling option	UbitUmarov	2016-08-07	1	-6/+6
\|
*	Remove entities from updates queues on kill. Do it sync so enqueues after	UbitUmarov	2014-08-23	1	-0/+15
\| \| \| \|	the kill work
*	reserve updates priority queue 2 for attachments, send them by it on	UbitUmarov	2014-08-20	1	-1/+3
\| \| \| \| \| \|	BestAvatarResp scheme. Attachments cannot be sent on imediate queues, since they will block everything. Changed distance to priority math, keeping identical result, shifted to start at queue 3.
*	fix priorityQueue to correctly use the fairness counts starting at 8 for	UbitUmarov	2012-09-26	1	-10/+10
\| \| \| \| \|	nonimediate queues. Imediate queues where not taken into account so it was unused.
*	Revert "Stop messing order of updates, destroing the defined order of the ↵	Melanie	2012-03-21	1	-8/+3
\| \| \| \| \| \|	selected priority (by distance being the one that makes sense(?). So called fairness serves no usefull purpose. If a region is lagged or user has bad comms, and far objects updates don't arrive, at least nearby thinks do have a chance to keep ticking. Just test on a big region and observe rez order on arrival. lower viewer bandwith helps seeing the diference. No use to put in core since cmic loves the priority scrambling code i comented out." This reverts commit 68981d01f024f8a46949127e1cc23c81282f5220.
*	Stop messing order of updates, destroing the defined order of the selected ↵	UbitUmarov	2012-03-21	1	-3/+8
\| \| \| \|	priority (by distance being the one that makes sense(?). So called fairness serves no usefull purpose. If a region is lagged or user has bad comms, and far objects updates don't arrive, at least nearby thinks do have a chance to keep ticking. Just test on a big region and observe rez order on arrival. lower viewer bandwith helps seeing the diference. No use to put in core since cmic loves the priority scrambling code i comented out.
*	minor: remove mono compiler warnings	Justin Clark-Casey (justincc)	2011-05-06	1	-1/+1
\|
*	Fix a bug looping through the priority queues. This should fix the problem	Mic Bowman	2011-04-23	1	-2/+3
\| \| \| \|	of not all prims being sent without reprioritization.
*	Added a second immediate queue to be used for the BestAvatar policy	Mic Bowman	2011-04-22	1	-17/+82
\| \| \| \| \| \|	and currently used for all of an avatars attachments by the other policies. Also changed the way items are pulled from the update queues to bias close objects even more.
*	Various clean ups. Removed some debugging code. Added a new "show pqueues"	Mic Bowman	2011-04-22	1	-4/+3
\| \| \| \| \| \|	command to look at the entity update priority queue. Added a "name" parameter to show queues, show pqueues and show throttles to look at data for a specific user.
*	Added an "immediate" queue to the priority queue. This is	Mic Bowman	2011-04-20	1	-0/+258
	per Melanie's very good suggestion. The immediate queue is serviced completely before all others, making it a very good place to put avatar updates & attachments. Moved the priority queue out of the LLUDP directory and into the framework. It is now a fairly general utility.