OsSetTerrainTextures
From OpenSimulator
(Difference between revisions)
Line 5: | Line 5: | ||
* a set of texture keys for legacy viewers and map | * a set of texture keys for legacy viewers and map | ||
* a set of texture or pbr material keys for new viewers.<br> | * a set of texture or pbr material keys for new viewers.<br> | ||
− | so this function | + | so this function allows the change of: |
* textures for legacy viewers and map if <b>types</b> == 0 or 2 | * textures for legacy viewers and map if <b>types</b> == 0 or 2 | ||
* textures for new viewers if <b>types</b> == 1 or 2 | * textures for new viewers if <b>types</b> == 1 or 2 | ||
* PBR materials for new viewers if <b>types</b> == 1<br> | * PBR materials for new viewers if <b>types</b> == 1<br> | ||
The list <b>textureKeys</b> must contain keys or names of 4 textures or 4 pbr materials. They must be of the same type due to viewers restrictions.<br> | The list <b>textureKeys</b> must contain keys or names of 4 textures or 4 pbr materials. They must be of the same type due to viewers restrictions.<br> | ||
− | This | + | This defines the textures or materials the viewer will use to draw the terrain texture<br> |
They are ordered from low to high terrain height level, as on viewers World -> Region Details -> Terrain menu tab.<br> | They are ordered from low to high terrain height level, as on viewers World -> Region Details -> Terrain menu tab.<br> | ||
If a entry is a name, then the material or texture must be present on the prim inventory.<br> | If a entry is a name, then the material or texture must be present on the prim inventory.<br> |
Revision as of 18:53, 5 May 2025
osSetTerrainTextures(list textureKeys, integer types)
| |
Opensimulator regions store two sets of textures or materials keys:
so this function allows the change of:
The list textureKeys must contain keys or names of 4 textures or 4 pbr materials. They must be of the same type due to viewers restrictions. | |
Threat Level | High |
Permissions | ESTATE_MANAGER,ESTATE_OWNER |
Extra Delay | 0 seconds |
Notes | |
This function was added in 0.9.3.1 |