| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| | |
repeated use of these commands will induce floating point accumulation errors. Please back up your region before using.
|
| |
| |
| |
| | |
This reverts commit 1842388bb4dcf5ecd57732ffa877b6ca1a3dec7b.
|
|\ \
| |/ |
|
| | |
|
| |\ |
|
| | | |
|
| | |
| | |
| | |
| | | |
to reduce mesh asset decoding failures
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
Conflicts:
OpenSim/Region/ClientStack/Linden/Caps/BunchOfCaps/BunchOfCaps.cs
OpenSim/Region/ClientStack/Linden/UDP/LLClientView.cs
OpenSim/Region/Framework/Scenes/ScenePresence.cs
|
| | |
| | |
| | |
| | | |
magic numbers
|
| | |
| | |
| | |
| | |
| | | |
Resolves http://opensimulator.org/mantis/view.php?id=6857
This prevents the inventory service complaining later about an attempt to change an invariant
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
x/y rot before sending agent updates, instead of before any agent update processing
It turns out that the x/y rot data in mouselook is needed to implement this and to push the avatar against the ground if walking in mouselook.
Doing this in the terse send so that we preserve mouselook rotation information
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Fixes http://opensimulator.org/mantis/view.php?id=3274
When not in mouselook, avatar only sends rotations around the Z plane (since that's the only way an avatar can rotate).
However, in mouselook it also sends X and Y information. But sending X and Y in terse updates causes issues with wrong camera movement in mouselook.
So strip out X and Y components for now. If this is an issue, then could strip out before sending avatar terse update, though this generates more cpu work.
Thanks to mirceakitsune for suggesting an initial fix
|
| |
| |
| |
| | |
for slow walk/run in 4cfe02a rather than the magic number
|
| |
| |
| |
| | |
only set true once and never reset
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
AGENT_CONTROL_STOP is specified to SP.HandleAgentUpdate if the user holds down the space bar on a viewer.
For a stopped avatar, this prevents fly or walk/run (though not rotate) until released.
For a walking/running avatar, this reduces movement to half speed.
For a flying avatar, this stops the avatar.
These are observed behaviours on the LL grid - there was no previous OpenSimulator implementation
This commit introduces an optional parameter to SP.AddNewMovement(), which means that it will no longer compile on .NET 3.5 or earlier versions of Mono than 2.8
Currently, this does not work for jumping, and if used whilst flying the avatar continues the fly animation even though it does not move
|
| |
| |
| |
| | |
rather than a byte
|
| |
| |
| |
| | |
Vector3.Zero
|
| | |
|
| | |
|
| |\ |
|
| | |
| | |
| | |
| | | |
This was due to the PhysicsActor no longer being recreated on stand from ground.
|
| | |
| | |
| | |
| | | |
sitting
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
not any specified avatar rotation as well.
Don't translate root prim position by avatar rotation.
|
| | |
| | |
| | |
| | | |
explicitly specified
|
| | |
| | |
| | |
| | |
| | |
| | | |
land_collision_end lsl events
Wrong number of parmeters now generates syntax error on compile, as seen on LL grid
|
| | |
| | |
| | |
| | |
| | |
| | | |
the RegionReady module to be warn so that the message will show up in the
log for simulators running in a more production mode (knowing when logins
are functional is useful).
|
| | |
| | |
| | |
| | | |
of rotation and center can be optionally overridden in the command line
|
| | |
| | |
| | |
| | | |
but not for foliage, don't know why. Also doesn't work on terrain. Successive use of this command will likely introduce floating point error accumulation. Back up your region before using it :)
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
.gitignore
OpenSim/Region/CoreModules/Scripting/HttpRequest/ScriptsHttpRequests.cs
OpenSim/Region/CoreModules/World/Land/LandManagementModule.cs
prebuild.xml
runprebuild.bat
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
to wrong position in third-person and mouselook"
Reverting to place on separate branch
This reverts commit ff4e7de7769b7eaa1b4fd3917e59f362b708226a.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Reverting to place on new branch
This reverts commit ed1029712a85206430fee1d4897d473517728dab.
|
| | |
| | |
| | |
| | |
| | |
| | | |
is Vector3.Zero"
This reverts commit 9bdd3dc7de46507b490a2eae5160123a28133d63.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
been specified as well."
Revert to place on separate branch for now
This reverts commit 70e651a8d1d0c2a48c4f26cd1c70bee098c11a57.
|
| | |
| | |
| | |
| | |
| | |
| | | |
targets."
This reverts commit 78649eb0999a5f97cc541c94ec98d1d06ed957cb.
|
| |/
| |
| |
| |
| |
| | |
Reverting for now to place on separate branch
This reverts commit 65304260af283211443a2872c46f6609d3e45649.
|
| |
| |
| |
| | |
Need to take into account rotation of linked prim now that we are always specifying sits wrt the root prim
|
| |
| |
| |
| | |
I forgot that m_post is being set inconsistently between non-explicit and explicit ragets
|
| |
| |
| |
| | |
specified as well.
|
| |
| |
| |
| | |
Original commit is ff4e7de7
|
| |
| |
| |
| |
| |
| | |
Vector3.Zero
As far as I can see it's valid to change the eye offset even if you aren't changing the at target.
|
| |
| |
| |
| |
| |
| | |
TestRepeatSameDrawContainingImageReusingTexture() and TestRepeatSameDrawContainingImage() if localhost has a webserver set up.
Use 0.0.0.0 instead of localhost
|
| |
| |
| |
| |
| |
| | |
position in third-person and mouselook
We now specify sits as offsets from the root prim, as the viewer expects.
|
| |
| |
| |
| |
| |
| | |
again as "non-shared"
Addresses http://opensimulator.org/mantis/view.php?id=6860
|
| |
| |
| |
| |
| |
| | |
syntax error
This was the case before any of the recent changes
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
take a single integer, generate a syntax error on LSL script compile rather than an exception later on.
This applies to events changed, collision, collision_start, collision_end, on_rez, run_time_permissions, sensor, touch, touch_start, touch_end
|
| |
| |
| |
| |
| |
| |
| | |
and timer LSL events generate a syntax error if inappropriately given arguments.
This matches behaviour seen on the LL grid and a previous change for state_entry.
These are all the events which should take no arguments
|