| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
real groups module can even be implemented.
|
| |
|
|
|
|
|
|
|
|
| |
Add rezzing time to objects. Add Object return and traffic fields to land
database. Add plumbing for auto return. Implement auto return.
Contains a migration. May contain nuts.
|
|
|
|
|
|
| |
* Hopefully this will resolve http://opensimulator.org/mantis/view.php?id=2383
|
|
|
|
|
|
|
| |
* I believe this is reasonable since code outside the Linden client stack shouldn't be aware of the packet format being used
* I would love to have made the method protected, but the LoadBalancerPlugin is still calling it and resolving that would require more work
|
| |
|
|
|
|
| |
there are some circumstances in which not finding a user is not an error
|
|
|
|
| |
LLClientView
|
|
|
|
| |
descriptive of its actual function
|
|
|
|
|
|
|
|
|
| |
when it moves
* This should fix a long standing issue where you often wouldn't see other people simply turn around without moving at all
* Arguably lastPhysRot (to mirror lastPhysPos) is not a good name, may change variable names later
|
| |
|
|
|
|
| |
descriptive of what it actually does
|
|
|
|
|
|
|
| |
* This may help http://opensimulator.org/mantis/view.php?id=2377 where large linksets do not always correctly delete - since a lost kill packet to the client could result in
the symptoms described
|
|
|
|
|
|
| |
Note: New file, run prebuild.
|
|
|
|
|
|
|
|
| |
* Add missing PARCEL_MEDIA_COMMAND_* constants
* Fix a copy/paste error in SendParcelMediaUpdate
llParcelMediaCommandList should work now
|
| |
|
|
|
|
| |
the new surface touch parameters in 1.21 viewers.
|
|
|
|
|
|
|
| |
for the new surface touch parameters in 1.21 viewers.
TODO: add the touch args to OnGrabObject and OnDeGrabObject.
|
| |
|
|
|
|
| |
related to regionflags and capacity. I'm sorry, the object capacity that you dialed is not valid.. please check the number and dial again.
|
|
|
|
|
|
|
|
|
| |
The average-value of modify.ModifyBlock.Height in LLClientView.cs:4170
seem to be incorrect or it isn't the average? Mhhh...
So the terrain build -> Flaten Sphere is unuseable.
I have put in a patch that contains a workaround while
the main problem is not solved.
|
|
|
|
|
|
|
| |
* Implmements llModifyLand() and a check for the "Allow others to terraform flag"
* Thanks tglion!
|
|
|
|
|
|
|
| |
* I believe this was the cause of the remaining packet_out_of_order messages in the Linden client logs
* There were race conditions where multiple clientstacks would overwrite each other's sequence numbers
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Implementation of llModifyLand() and There is a bug on
permission-check of land-terraforming: x an y-coordinates
are interchanged on function-call ExternalChecksCanTerraformLand.
Correct: x is west, and y is north. 2) Missing check of
"Other allow to terraform-flag" (Parcel.ParcelFlags.AllowTerraform)
|
| |
|
|
|
|
|
|
| |
* Initial implementation
* You'll only be able to seen green dots on regions on the map that have been updated.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Thise were client supplied untrusted values we never used anyway.
|
| |
|
|
|
|
|
|
| |
* refactoring
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
old way: each region module interested in chat from client had to
- subscribe to scene.EventManager.OnNewClient
- then in its OnNewClient delegate it would subscribe to
client.OnChatFromViewer to capture chat messages coming
new way: ChatModule is the only region module that uses the "old
way" approach but is now forwarding all client chat via
scene.EventManager.OnChatFromClient
- each region module interested in chat from client now only
subscribes to scene.EventManager.OnChatFromClient
this not only simplifies code, but also allows us to substitute
ChatModule with derived classes (ConciergeModule is going to be one
example).
Also, this changeset changes ChatFromViewer to ChatFromClient as it
doesn't necessarily have to be a viewer that is a chat source.
i've taken great care to only comment out those OnNewClient delegates
that were only used for getting at the client chat --- hope it's not
breaking anything.
|
| |
|
|
|
|
|
|
|
| |
Thank you, idb, for a patch to implement the packet and plumbing for
the material settings.
|
|
|
|
|
|
| |
- Removed MapBlockData.Flags; it isn't used anywhere (maybe MapBlockData.RegionFlags replaced it?)
|
|
|
|
|
|
| |
- Implemented llMapDestination.
|
| |
|
|
|
|
|
|
|
|
|
| |
Estate/ Manager Owner Uses the Region/Estate Menu Region TAB,
and uses "Teleport Home All Users..." (Action Button), the
action will complete but no one will be teleported and all
users still function in the region ok.
|
| |
|
| |
|
|
|
|
|
|
| |
* returns FAKEEVENT instead of the connection returning a 502. It doesn't like our 502's for some reason.. so, in leau of this.. send it a fake event.
* Once again, this is still 'really early' code, so please don't blame us if you have no more threads left.
|
|
|
|
|
|
|
|
|
| |
* Updates to libomv r2243,
* Remove lots of unnecessary typecasts
* Improves SendWindData()
Thanks jhurliman.
* Will update OpenSim-libs in 10 minutes..
|
| |
|
|
|
|
|
|
|
| |
* It seems kind of silly to be building a 256x256 array just to use two 16 float blocks.. but for now the layerdata routine requires it so we'll go along with that.
* We only fill a 32x16 area of the 256x256 float array with data.
* We use patches 0,0 and 0,1 for the first and second patch to determine the direction and magnitude of the wind.
|
|
|
|
|
|
|
|
|
|
| |
Check the client dialog box (from top menu) WORLD / REGION ESTATE
/ REGION tab. The client dialog box seems to have a hard limit of
about 32 characters per line available for displaying the region
version number. Our regions are sending a string which is greater
than the limit, causing the client to wrap the text and look ugly.
|
|
|
|
|
|
|
|
| |
* A little wind wouldn't hurt anyone, right? This is the 'slightly breezy' setting.. hopefully you won't notice 'much' of a difference.
* It turns out the terrain patch routine is similar enough to the wind version that it can be used to hack together a breeze generator with a few mods.
* Not much configuration.. yet. You only get breeze updates in the general vicinity of your camera now to keep bandwidth usage down.. and we're not talking about 'much' movement at the moment.
* initial version... could use improvement I'm sure.
|