lsl new functions

[SatguruS1488312156]

I recently found out , by accident while googling, that linden had added, this year, a new function called llTextbox.

Now whenever linden introduces a new function do they publish that information somewhere ?

 

 

[Fleth Robonaught]

The simplest way to look for new functions is the function index in the Second Life wiki:

http://wiki.secondlife.com/wiki/Category:LSL_Functions

[SatguruS1488312156]

I see that they mark the new functions as "NEW".

I wonder how long do they leave those as marked new.

It would be helpful if, like other scripting or non -scripting languages, lsl had release or  version numbers. This way one could check the release notes to find information about any new functions, features etc.

Another thing which would help too would be if the description of each function in the wiki showed the date on which that function was introduced.

 

[Innula Zenovka]

New LSL functions are described in the release notes for the server version in which they are introduced: https://wiki.secondlife.com/wiki/Category:Server_Release_Notes 

I normally keep an eye on the Second Life Server forum, where a thread giving details of the present week's releases is pinned to the top.

[Rolig Loon]

Generally speaking, the documentation about LSL is not produced by LL.  The wiki is maintained by scripters like you and me.  Beyond very basic descriptions of syntax, LSL is offered essentially as a black box.  Users figure out how its functions behave and share what they learn about its quirks.

[SatguruS1488312156]

Thanks for pointing out those links.

They have been duly bookmarked into my favorite list

I see a discussion going on in the Second Life Server forum about a new function called llSetKeyframedMotion

 

[SatguruS1488312156]

I did not realize that lsl portal was a volunteer effort.

I randomly checked  few  of the lsl wiki history pages and did not see any linden name.

One volunteer which I saw quite  often was Strife Onizuka

Well kudos to the volunteers.

They have done an excellent work.

 

 

[Void Singer]

I believe currently we've been leaving the "new" tag on any function that wasn't originally included as of ~MONO rollout.

the function list is however.... touchy.

you'll notice the pretty list on top, and the standard category list below.... the category list is a bit flaky and doesn't like synching up (occasionally misplacing items in the wrong sort bin), the pretty list however has to be done manually, and is on a separate template. we've bee getting a bit more Linden participation recently, where they'll outline the basics of a new function and mark it "pre-release" and then whowever happens to notice it being released will remove the pre-release flag and add it to the pretty list.

[Rolig Loon]

While we're vaguely on the subject..... I went looking for the function wiki page for llSetVelocity the other day and had a heck of a time finding it.  It is at http://wiki.secondlife.com/wiki/LlSetVelocity, but the function is not included in the master list at http://wiki.secondlife.com/wiki/Category:LSL_Functions .  I have never figured out how to mess with that template, so I don't know how to add it.  Do you, Void?

[Void Singer]

it's actually the "LSL ALL Functions/Name" template you want, the format is just a plain list so you can just copy paste a line and edit the targets (just make sure you get the alphabetical order right)

ETA:
I went ahead and added that one... there's probably more that need to be added.

[Miranda Umino]

llSetVelocity looks to be an useless function .

It looks to do exactly the same thing that an alias for llApplyImpulse(llGetMass() * force, boolean )

 

Have i missed something about it ?

[Void Singer]

same idea, different way to approach it.

[Rolig Loon]

... which may explain why it was missing from the list.  I wasn't even aware of the function until someone posted a question here a little while ago, asking how it worked.

[conrad Evanier]

TYPICAL lol just when i have made a cool little float text script that can start new lines from chat,  textbox dose that all for you lol handy function though, im hoping that llTeleportAgent dosent have land owner perms if it comes out  Mahaahhahahaha would put that to good use  

[Digit Ditko]

I went ahead and added several new functions that have been added over the last few months

llGetMassMKS

llGetMemoryLimit

llSetAnnularVelocity

llSetContentType

llSetKeyframedmotion

llSetLinkCamera

llSetMemoryLimit

[Void Singer]

Thanks Digit

[Rolig Loon]

Thank you, Digit.  I somehow missed  seeing a couple of those as they were introduced.  Time to start playing and see what they can do.

BTW, llGetMassMKS doesn't show up yet for me.  I wonder about that one, though.  It's never been clear to me what unit LSL uses for mass, but I have assumed that it was kilos. No?  If not, and they had to introduce a whole new function just to apply a constant factor, what unit were they using before?

[Void Singer]

IIRC grams... and prims have the density of water =X

[Rolig Loon]

Ah, OK .... So llGetMassMKS == llGetMass / 1000.0 ?   Seems like kind of a useless function to me.

[Void Singer]

seemed odd to me too... but then I realized that in grams, the new prim sizes exceed max integer for 32bits. even with MKS you can still exceed it for a large enough object.... so that may have had something to do with it.

[Rolig Loon]

That makes sense.  It sort of begs another question, though....  I can't think of a reason you might need to know the mass of an object unless it were physical, and you can't (or shouldn't) make a physical object large enough to hit the new upper limit for prims ..... so again, why bother with llGetMassMKS ?

[Void Singer]

(64 *100)^3 = 262,144,000,000.0

so that's the old function... a 64m cube, breaks the maxInt cap

new function, 262,144,000.0 doesn't break the cap for 10 of those.

not that the cap REALLY matters since it'll be in a float, but it mans more likelyhood of easy translation.

although tbh, I don't see much use in llGetMass* anyways

[Miranda Umino]

llGetMass and llGetMassMKS return a 32 bit float not a 32 bit integer . 

You can  have some floats superior to 2^32.

 

I ve done a quick test with a cube 64 * 64 *64 with the max density ( max density is actually at 22587.000 kg / m3 .

llGetMass  returns 59210464.000000 and  llGetMassMKS 5921046528.000000

 

I ve done a second test with a cube 64 * 64 *64 with a density not mutiple of kg/m3 .

For instance , for density = 1.235 , the theoric value is 323747,84

llGetMass  returns 3237.478271 and  llGetMassMKS   323747.843750

 

Well , the both are wrong ...

 

Now , do a shear of 0.5 on X  ;

if you remember your geometry courses, the number of m3 doesn t change : llGetMass  returns 3 3237.480225   and  llGetMassMKS   323748.031250

It s bugged ..

 

[Void Singer]

I'm using that supposition that in many cases the float will be converted to integer... but that only gets to happen if the float range doesn't exceed the integer range.

as for your results... precision for floats of 32bits is only 24bits, or just over seven significant digits of absolute accuracy. one of the other may be using 64bits behind the scenes to better approximate the float giving slightly different results past the 7th digit (or they may be using different rounding models), so not so much bug, as inconsistency.