| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Make the optimization with IEnumerable.Except() in Check4096 actually work by providing an appropriate equality definition for GridRegion objects.
|
| | |
|
| |
|
|
|
|
| |
This will cause visual params to be persisted along with worn items. With
this, alpha and tattoo laters will be saved. Multiple layers MAY work, but
not tested because I don't use Viewer 2.
|
| |
|
|
| |
client displays a blank error box.
|
| |
|
|
|
|
|
|
|
| |
It contains a major interface version bump and will NOT work with earlier grid
services. This is preliminary work that will lead to layers support.
Rest appearance services are commented out completely, they will have to be
adapted by someone who actually uses them. Remote admin is working, but has
no layers support. There is no layers support in the database. Login likely
won't work. You have been warned.
|
| |
|
|
|
|
|
| |
The attachment code appears to work correctly for 1.23 viewers so, in
spite of some big changes in the internal representation, there don't
appear to be regressions. That being said, I still can't get a viewer2
avatar to show correctly.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
AvatarService -- add two new methods, GetAppearance and SetAppearance
to get around the lossy encoding in AvatarData. Preseve the old
functions to avoid changing the behavior for ROBUST services.
AvatarAppearance -- major refactor, moved the various encoding
methods used by AgentCircuitData, ClientAgentUpdate and
ScenePresence into one location. Changed initialization.
AvatarAttachments -- added a class specifically to handle
attachments in preparation for additional functionality
that will be needed for viewer 2.
AvatarFactory -- removed a number of unused or methods duplicated
in other locations. Moved in all appearance event handling from
ScenePresence. Required a change to IClientAPI that propogated
throughout all the IClientAPI implementations.
|
| |
|
|
| |
client ip address to agent circuit data, so that it's always there.
|
| |
|
|
| |
flexible without changing current behavior
|
| |
|
|
| |
possible implementations. This doesn't change any behavior or any Robust code, but it simplifies the SimianGrid connector by using the standard OpenSim interface for setting last position now
|
| |
|
|
|
| |
This was a regression - the code to look up the correct type folder was no longer being called if items were added without a parent folder set
This may have been broken since commit bd49985a on 2010-05-02
|
| |
|
|
| |
untested. Committing to move to my other computer.
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
range.
Also add GetHyperlinks() to the grid service.
|
| |/
|
|
|
| |
in LM info. Maturity is NOT the parcel's setting, that is only for the
image and text. Parcel maturity is governed by region maturity.
|
| | |
|
| |
|
|
| |
* Bug fix in TPs across neighboring regions: bug was introduced when getting rid of crashed sessions.
|
| | |
|
| |
|
|
| |
detection from Robust connector. Fixed Simian to continue to send those location updates upon parcel crossing, without changing the interface.
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
will want to track position against sessionID instead of userID
* Updated SimianPresenceServiceConnector to use the new LoggedOut/SetHome/etc methods and only update session position on parcel crossing
|
| |/ |
|
| |
|
|
| |
making offline friendship offers fail in grids.
|
| | |
|
| |
|
|
| |
fields.
|
| |
|
|
|
|
| |
home and position info in the presence service. WARNING: I violated a taboo by deleting 2 migration files and simplifying the original table creation for Presence. This should not cause any problems to anyone, though. Things will work with the new simplified table, as well as with the previous contrived one. If there are any problems, solving them is as easy as dropping the presence table and deleting its row in the migrations table. The presence info only exists during a user's session anyway.
BTW, the Meshing files want to be committed too -- EOFs.
|
| |
|
|
|
|
| |
is left os to figure out what black magic turns AgentCircuitData into
AgentData and then copy that into the ScenePresence, where m_Viewer is
already added with this commit and waits for the data.
|
| |
|
|
|
|
| |
This requires a special XMLRPC call, which has to supply the credentials of
a god user (User level >= 200). Disabled by default. Also Adds a configuration
option to set the initial permitted login level.
|
| |
|
|
| |
work again
|
| | |
|
| |
|
|
|
|
|
| |
cache only
* Adds GetTextureModule that implements the "GetTexture" capability, aka HTTP texture fetching. This is a significantly optimized path that does not require any server-side JPEG2000 decoding, texture priority queue, or UDP file transfer
* Sanity check for null reference in LLClientView.RefreshGroupMembership()
|
| |
|
|
|
|
| |
IAssetService.Get() method
* Changing the SimianGrid asset service connector to match the corrected documentation
|
| |
|
|
|
|
|
| |
of a region and joining it to an existing estate or creating a new estate,
as well as creating an estate owner if in standalone, and assigning estate
owners. In Grid mode, existing users must be used. MySQL ONLY!!!! so far, as
I can't develop or test for either SQLite or MSSQL.
|
| |
|
|
| |
is no possibility of cascading requests when failures happen.
|
| |
|
|
|
|
| |
Adds MockUserAccountService and connects it up
Stops services being carried over between tests since this leads to hard to find bugs
Improves information and error reporting when loading plugins
|
| |
|
|
| |
for it. GridUserService makes more sense; it's the user of the grid, "grid user". I changed it everywhere.
|
| |
|
|
|
| |
this will initially store home location data instead of the presence service
compiles but not enough to actually test yet
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
InternalEndPoint.Port). This class is complex enough as it is
* Changed the failed to inform neighbor message from a warning to info, since this will fire for every empty neighbor space
* Made the EnableSimulator/EstablishAgentCommunication log message more verbose and more clear about what is happening
|
| | |
|
| |
|
|
| |
on the friends service
|
| | |
|
| | |
|
| |
|
|
|
| |
service, and never the twain shall meet. This finally opens up the path to
a working friends implementation
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
