| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
gone in.
|
| |\ |
|
| | | |
|
| |\ \
| |/
| |
| | |
inventory-connector
|
| | |
| |
| |
| | |
Handler - ref mantis #4010
|
| | | |
|
| | |
| |
| |
| | |
starting to get on my nerves.
|
| |/ |
|
| |
|
|
|
|
| |
Store and retrieve user profile url at runtime
Not yet persisted
Thanks Fly-Man
|
| |
|
|
| |
WARNING: PLEASE MAKE SURE TO USE THIS NEW bin/OpenSim.addin.xml
|
| |
|
|
| |
sizes. * Now, what's available of the terrain will show and it'll be truncated if it's larger on Linden Clients. Parcel minimum is 64 (256/4) for the client to accept it.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
crash in search.
Fixes Mantis #3952
|
| |
|
|
| |
exception reported there by WiLLuMPJuH Huisman pertaining to TeleportFailedPacket.
|
| | |
|
| |
|
|
|
|
| |
libomv-0.7.
|
| |
|
|
|
|
|
|
| |
* Uses mantis #3811 as a base (thanks jhuliman) with changes.
* E-mail regarding interface changes sent to the opensim-dev list
* Archive: https://lists.berlios.de/pipermail/opensim-dev/2009-July/007219.html
|
| |
|
|
| |
constraints. Ooops.
|
| |
|
|
|
|
|
|
|
| |
a raycast test safely.
* Test for prim obstructions between the avatar and camera. If there are obstructions, inform the client to move the camera closer. This makes it so that walls and objects don't obstruct your view while you're moving around. Try walking inside a hollowed tori. You'll see how much easier it is now because your camera automatically moves closer so you can still see.
* Created a way to know if the user's camera is alt + cammed or just following the avatar.
* Changes IClientAPI interface by adding SendCameraConstraint(Vector4 CameraConstraint)
|
| |
|
|
|
|
|
|
|
| |
linkset, made each of those prims rotate around its own centre rather than around the geometric centre of the selection like they should do (and like the client expects).
This involved adding a new OnUpdatePrimSingleRotationPosition event to IClientAPI so that we can get the changed position from the client.
Btw adding new events to IClientAPI is really tedious where you have to copy the change across to at least 5 or 6 other files.
[Note this doesn't fix the bug where any rotation changes to the root prim (but not the whole linkset) cause rotation errors on the child prims.]
|
| |
|
|
| |
event trigger rather than triggering the event once for every localid in the derez packet.
|
| |
|
|
|
|
|
|
|
| |
balancer plugin work again. Create a new method, GetClientEP, to retrieve
only the EndPoint for script usage. Marked the purpose of the method
in IClientAPI.cs with a warning. Also restored the corresponding SetClientInfo
functionality.
|
| |
|
|
|
|
|
| |
heavy usage and inline DebugPacket, so DebugPacket is run as a method, causing Packet
to be constantly pushed and popped uselessly, if you are not debugging packets. This showed some really big difference in a mock test, let's see how it behaves here.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change moves texture send processing out of the main
packet processing loop and moves it to a timer based
processing cycle.
Texture packets are sent to the client consistently over
time. The timer is discontinued whenever there are no
textures to transmit.
The behavior of the texture sending mechanism is controlled
by three variables in the LLCLient section of the config
file:
[1] TextureRequestRate (mS) determines how many times per second
texture send processing will occur. The default is 100mS.
[2] TextureSendLimit determines how many different textures
will be considered on each cycle. Textures are selected
by priority. The old mechanism specified a value of 10 for
this parameter and this is the default
[3] TextureDataLimit determines how many packets will be sent for
each of the selected textures. The old mechanism specified a
value of 5, so this is the default.
So the net effect is that TextureSendLimit*TextureDataLimit
packets will be sent every TextureRequestRate mS.
Once we have gotten a reasonable feeling for how these parameters
affect overall processing, it would be nice to autonmically manage
these values using information about the current status of the
region and network.
Note that this also resolves the pathologcal problem that
previously existed which was that a seated avatar generated very
few in-bound packets (theoretically) and would therefore be the
least able to retrieve the images being displayed by a
projector script.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Also reduce limit to 40 to allow for last logon dates and titles
|
| |
|
|
|
|
| |
without crashing
|
| |
|
|
|
|
| |
yet.
|
| |
|
|
|
|
| |
Fixes Mantis #3831
|
| | |
|
| |
|
|
|
|
| |
This patch ensures that the touch positions are set during touch_end
events (currently only working for touch_start and touch events).
|
| |
|
|
| |
lowers Land
|
| | |
|
| | |
|
| |
|
|
| |
LICENSE.txt.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We've encountered problems with textures never fully downloading and
objects not moving or being deleted (from the client's point of view)
even when the bandwidth settings on the client have been set very
low. This can happen over reasonably lossy links (eg you're on the
other side of the world from the server) as the server retries 3 times
and then gives up.
Whilst its possible to set ReliableIsImportant, this forces the server
to keep retrying no matter what which potentially could lead to
problems. This patch allows for the setting of MaxReliableResends
explicitly (is set to 3 normally) in OpenSim.ini so if you know you
will have clients connecting with poor connections you can set it a
bit higher (10-15 works quite well even for very poor connections).
|
| | |
|
| |
|
|
|
|
| |
This modifies IClientAPI.SendDialog slightly.
Fixes Mantis #3661.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
-- please see the example. Affects region servers only.
This may break a lot of things, but it needs to go in. It was tested in standalone and the UCI grid, but it needs a lot more testing.
Known problems:
* HG asset transfers are borked for now
* missing texture is missing
* 3 unit tests commented out for now
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
* User interface is ... primitive at best right now.
* Loads bans from bans.txt and region ban DB on startup, bans.txt is in the format of one per line. The following explains how they are read;
DNS bans are in the form "somewhere.com" will block ANY matching domain (including "betasomewhere.com", "beta.somewhere.com", "somewhere.com.beta") - make sure to be reasonably specific in DNS bans.
IP address bans match on first characters, so, "127.0.0.1" will ban only that address, "127.0.1" will ban "127.0.10.0" but "127.0.1." will ban only the "127.0.1.*" network
|
| |
|
|
|
|
| |
the session. Also allow multiple data blocks.
|
| |
|
|
|
|
| |
packet length check. More changes to come
|
