Actually, I believe that osSetDynamicTextureData is only a thin wrapper around a .NET library function for drawing lines, text, etc. dynamically on a surface. So if one were to hunt that down in the .NET SDK documentation that might provide all the information that you need.

“Also, it would be great to get the osSetDynamicTextureData full function set documented on the Wiki, and the 2 examples in the distrtibution lined explicity to the Wiki page so all the xanmplesa are available to a wilki broswer.”

I understand that it’s difficult to ask for such things and to do so leans toward optimism, but ANY help in the area of documentation would greatly serve /everybody’s/ cause to date. Calling all units - rapid fire reporting needed on site! I tend to border on the insane though…

Filling out the functions I’m afraid I will have to leave to somebody else, since I have to prioritize my (always) limited time
You might be somewhat disturbed to know that while looking for the os functions page in the wiki, I came across another one at

http://opensimulator.org/wiki/LSL_osFunctions

This should really be amalgamated with

http://opensimulator.org/wiki/OSSL_Implemented

http://opensimulator.org/wiki/OSSL_TextureDrawing

Though te 3example is a C# one which I am not sure how to compile as I have DotNetEngione enabed.

I added the function list as a link in
http://opensimulator.org/wiki/OSSL_Implemented

The Opensim Wiki is difficult to fund one way round.

Can yo tell if the default for AllowOSFunctions is false as I suspect? If so we should get the opensim.ini.example file amended… it current states the default is true. Can you check and make that change to get everything in sync as a developper Justin?

Also, it would be great to get the osSetDynamicTextureData full function set documented on the Wiki, and the 2 examples in the distrtibution lined explicity to the Wiki page so all the xanmplesa are available to a wilki broswer.

From reading the code, it looks like a setting in OpenSim.ini in the [XEngine] or [ScriptEngine.DotNetEngine] sections such as

Allow_osTeleportAgent = true

would allow it for everybody no matter what threat level threshold was set (and as long as the general AllowOSFunctions switch is true).

On the other hand, it looks like one can also supply a list of UUIDs for users so that only scripts owned by that user can execute that function. For instance,

Allow_osTeleportAgent = 36bff189-1a29-41dd-aeaa-81139148ec08

would allow only scripts owned by the user denoted by uuid 36bff189-1a29-41dd-aeaa-81139148ec08 to execute osTeleportAgent().

If I want to say allow 3 specific osFunctions and no others, wehatever their threat level, how is that done?

As you pointed out to me by e-mail, this is a list of functions at http://opensimulator.org/wiki/OSSL_Implemented

can we get a l;ist of the built in functions on the OS Wiki? And the threat level for each alongide? Meanwhile, what is the required threat level setting in opensim.ini for the 2 above?