On Fri, 26 Jul 2013 20:50:04 +0200, Henri Beauchamp wrote:
> On Fri, 26 Jul 2013 13:45:26 -0400, Log Linden wrote:
>
> > Henri,
> >
> > For the increment capability, the name is "IncrementCOFVersion" instead of
> > "IncrementCofVersion". I transcribed it wrong when I handed the release
> > notes
On Fri, 26 Jul 2013 14:59:36 -0400, Log Linden wrote:
> On Fri, Jul 26, 2013 at 2:50 PM, Henri Beauchamp wrote:
>
> > What about UpdateAgentAppearance however ?...
> > There's still no trace of code using it in sunshine-external
> > (https://bitbucket.org/lindenlab/sunshine-external).
>
> Suppo
Supposed to be "UpdateAvatarAppearance".
On Fri, Jul 26, 2013 at 2:50 PM, Henri Beauchamp wrote:
> On Fri, 26 Jul 2013 13:45:26 -0400, Log Linden wrote:
>
> > Henri,
> >
> > For the increment capability, the name is "IncrementCOFVersion" instead
> of
> > "IncrementCofVersion". I transcribed it w
On Fri, 26 Jul 2013 13:45:26 -0400, Log Linden wrote:
> Henri,
>
> For the increment capability, the name is "IncrementCOFVersion" instead of
> "IncrementCofVersion". I transcribed it wrong when I handed the release
> notes off to Maestro.
>
> Sorry for the confusion,
> Log
Ah... Yes, much bett
The same amount of data has to be sent either way. Seems to me it would be
more beneficial to the servers to get requests out of the way faster to
free up the pipe for other requests. Dragging it out as long as possible is
only going to clog the pipe longer.
On Fri, Jul 26, 2013 at 10:47 AM, Argen
3000? thats double the amount i would have assumed it is capped at.
and yes, the Debug is obviously the preferences setting.
2013/7/26 Darien Caldwell
> There has to be some other throttle, because ThrottlebandwidthKBPS seems
> to correspond to what you set your bandwidth to in preferences (ma
On Jul 26, 2013 12:32 PM, "Darien Caldwell"
wrote:
> So basically while this system is probably beneficial to those with bad
internet connections, it's rather punitive to those who have excellent,
wide pipe connections. The only way to increase the bandwidth max is to
recompile the viewer.
One sh
Henri,
For the increment capability, the name is "IncrementCOFVersion" instead of
"IncrementCofVersion". I transcribed it wrong when I handed the release
notes off to Maestro.
Sorry for the confusion,
Log
On Thu, Jul 18, 2013 at 5:20 AM, Henri Beauchamp wrote:
> On Wed, 17 Jul 2013 15:52:37 -0
There has to be some other throttle, because ThrottlebandwidthKBPS seems to
correspond to what you set your bandwidth to in preferences (max 10,000
with LL's viewer).
However, This is being capped by the servers:
2013-07-26T16:46:00Z INFO: LLViewerThrottleGroup::sendToSim: Sending
throttle settin
My Viewer has:
ThrottleBandwidthKBPS
which also clearly says this:
Maximum allowable downstream bandwidth (kilo bits per second)
then theres also this:
XferThrottle
Maximum allowable downstream bandwidth for asset transfers (bits per second)
so i guess asset and everything else is also split, at
On Fri, 26 Jul 2013 13:58:47 +0200
Henri Beauchamp wrote:
> This setting is indeed only relevant to UDP traffic, or at least in
> LL's and most TPV viewers. IIRC, I saw attempts to account for this
> limit with HTTP texture fetching traffic in Singularity, but that
> would need to be checked for
On Fri, 26 Jul 2013 11:04:25 +0200, Lance Corrimal wrote:
> Hi all,
>
>
> I'm not quite clear about the ThrottleBandwidthKBPS debug setting... the
> sources suggest the value is understood as kilobit per second, but the name
> of
> the debug setting itself suggests kiloBYTE per second. Which
Hi all,
I'm not quite clear about the ThrottleBandwidthKBPS debug setting... the
sources suggest the value is understood as kilobit per second, but the name of
the debug setting itself suggests kiloBYTE per second. Which one is it?
...and is it even still relevant with most traffic being tcp/h
13 matches
Mail list logo
