| Commit message (Collapse) | Author | Files | Lines |
|---|
|
you rez it on. Including multi prim groups and prim that have different X/Y/Z scales.
|
|
Melanie!
RE: 0001079: r4387. touch() event does not fire when touch script is in root prim and child prims are touched
|
|
* In the future this should be a config option... and, hopefully this tides the builders over for a little while.
|
|
I need them to be for attachments.
|
|
inventory
* Now, if you own an item in a prim, you should be able to successfully drag it back into your inventory
* Temporarily, users which are not owners of the item cannot copy it, even if 'everyone can copy' is set
* This is pending fixes/implementation of upstream permission implementation
|
|
avatar. Those dastardly objects stick to you.
|
|
* Causes the internal handling of attachments to put the prim group conceptually at the position of the avatar instead of 0,0,0
|
|
properties panel for a prim's contents working
* Temporarily hacked things to bring our protocol data flow to be pretty much completely identical to the Linden's for this - to absolutely no avail.
* Leaving commented code in as a springboard for some future attempt
|
|
animation.
|
|
|
|
While I didn't use the patch directly, I did use the following from the patch to convert the uint value into the byte: (byte)((m_attachmentPoint % 16) * 16 + (m_attachmentPoint / 16))
|
|
|
|
Please adjust your editors to not use hard tabs.
|
|
* Your friends can see your attachments now. People who appear in the sim after you've attached something can also see your attachments.
* You can position & rotate your attachments now. Positions do *not* save.
* You can detach attachments now the regular way.
* Attachments do not cross into other regions with you..(this isn't too far off)
* Updated ODE to not request terse updates on child prim.
|
|
|
|
the example economy module, implements llSetPayPrice(), money() and llGiveMoney() in scripts. Thanks Melanie!
* Moves module loading before the script engine so the script engine can pick up events from modules registering interfaces with scene.
|
|
* Currently if you apply that to only one or two axis you get unpredictable and sometimes explosive results.
* Three axis works well enough to play with it anyway. More work is needed here.
* Fixed an incorrectly named method in ODE.NET
|
|
|
|
|
|
(this took a while to run).
|
|
* All objects are not touchable by default now
* When a script listens for one of the touch events in the state, an object becomes touchable.
* All LSL scripts report which events they consume now
** This uses semi-complicated Regex to discover the events, stick them in a dictionary, and then write a method call into each script state's state_entry() event.
** Tedd may figure out a better way to do this in the future. For now, this works for LSL.
|
|
* Scripts in prims within linksets can now be properly edited using the 'edit linked parts' linden ui option
|
|
investigate mantis 854
|
|
0.25f; This allows proper positioning of prim based on the face you click. ( Yes, you can click the bottom face of a prim that's above you, and the new prim appears directly below it. )
( Remove ray caster Verbosity )
|
|
0.25f; This allows proper positioning of prim based on the face you click. ( Yes, you can click the bottom face of a prim that's above you, and the new prim appears directly below it. )
|
|
|
|
Framework.Data.Base
We REALLY need to get the db layer sorted soon...
|
|
* It doesn't generate at_target events, because they don't exist yet in the script engine.
* The Tau is different, however, compatible with scripts I tested.
* Not perfect... but pretty good.
|
|
|
|
correctly results in the point of collision.
|
|
* It's not perfect, but it's good enough. (rarely erroneously returns a backface collision)
* After updating to this revision, rez a prim on another prim and watch it appear where you'd expect it to appear.
|
|
|
|
it into planes and normals.
* No obvious functionality difference as the Ray-cast code is incomplete for OBB right now.
|
|
vector components of the scale have a difference of less then 4.5 meters.
* When a new prim is created and raytracing is called for, raytrace from the camera position to the ground in the direction of the Norm(RayEnd - RayStart).
* If we got a hit based on our camera, create the new prim at the edge of the prim we hit.
* Don't raytrace if the difference between any component of the vector exceeds 4.5meters.
|
|
|
|
|
|
Here's a diff of the changes I have made in support of the following LSL
script functions.
llSetScriptState
llGetScriptState
llCSV2List
llListRandomize
llList2ListStrided
llListFindList
llResetOtherScript
llGetScriptName
It was necessary to modify ExecutorBase in support of the ScriptState
implementations.
I also modified SceneObjectPart and SceneObjectPart.Inventory to
corrects a quoting mismatch in the commentary that through off live
parsing of the files.
I also simplified the State definition at the start of BuiltinCommands.
|
|
probably a lot more then it should? )
|
|
|
|
* Even very rapid linking/delinking should now behave normally. Terse updates still occur as before
* Hopefully this ends the recent linking problems - please let us know if there are more
|
|
* Currently, terse updates are back, and extremely rapid linking and delinking will only break occasionally
* More work to do here
|
|
* Normalized some UUID handling
* Compacted a few Contains/Add into Set
|
|
|
|
|
|
'disappear')
* Root cause was that if two updates occurred in the same second of time, the second one was never sent
* Linking/delinking appears to be okay now
|
|
thanks Grumly57.
|
|
* Added osSetPrimFloatOnWater(BOOL) to make Physical prim float at the water level.
* osSetPrimFloatOnWater(TRUE); or osSetPrimFloatOnWater(FALSE);
* By default, prim do not float at the water level.
* More work is needed on the floating, but it's a start.
|
|
* Added WaterLevel support to the ODEPlugin. More on this later.
|
|
with SceneObjectGroup.LocalId (and hence reduce confusion).
|
|
support for region move/split/merge. See ThirdParty/3Di/README.txt. Unless the new modules are used there should be no noticeable changes when running OpenSim.
|
