object_uuids
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| object_uuids [2026/01/02 06:11] – robyn | object_uuids [2026/01/02 06:34] (current) – robyn | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ==== The SL issue Duplicates ==== | ==== The SL issue Duplicates ==== | ||
| - | To touch or sit on, and object, the object needs to be identified. The object name is not unique. For instance, you rez out a chair, called " | + | To touch or sit on, an object, the object needs to be identified. The object name is not unique. For instance, you rez out a chair, called " |
| ==== The SL issue Linked Objects ==== | ==== The SL issue Linked Objects ==== | ||
| Line 12: | Line 12: | ||
| Every rezzed object has a UNIQUE UUID. 6 chairs will have 6 unique UUID identifiers. In linked objects, the Root object will have a unique UUID identifier and each child object will have a unique UUID identifier . \\ \\ | Every rezzed object has a UNIQUE UUID. 6 chairs will have 6 unique UUID identifiers. In linked objects, the Root object will have a unique UUID identifier and each child object will have a unique UUID identifier . \\ \\ | ||
| - | How does SL and OS handle object UUIDs? The Asset DataBase has 1 copy of a specific object with all the object details. Many people may have this Object in their Inventory, which is a list, with an item object pointing to the one item in the asset DataBase. Each item in your Inventory has a unique UUID , just for you. When you rez that item out into the world, a Copy is rezzed with its own unique UUID, different from the DataBase UUID and your inventory UUID. The rezzed copy, UUID wise, is unique. // // | + | How does SL and OS handle object UUIDs? The Asset DataBase has 1 copy of a specific object with all the object details. Many people may have this Object in their Inventory, which is a list, with an inventory |
| The solution is to work with UUIDs to be accurate and specific. | The solution is to work with UUIDs to be accurate and specific. | ||
| Line 21: | Line 21: | ||
| ---- | ---- | ||
| - | {{: | + | {{ : |
| - | + | ||
| - | < | + | |
| - | + | | |
| - | + | | |
| - | + | | |
| - | + | | |
| - | 1: Ensure General is selected. | + | \\ |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | 2: Click Copy Keys | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | In IM or Local: | + | |
| - | | + | |
| - | + | ||
| - | Example: | + | |
| - | + | ||
| - | The same goes for touch. | + | |
| - | | + | |
| - | + | ||
| - | + | ||
| - | </ | + | |
| ---- | ---- | ||
| - | {{ :: | + | {{ : |
| - | < | + | * 1: Right click and edit the dance pad. Note, with highlight on, 8 dance pads are highlighted.This is a linked object. |
| + | * 2: Tick "Edit Linked" | ||
| + | * 3: Left click on target object (Linked Dance Pad) | ||
| + | * 4: Copy Keys. | ||
| - | + | | |
| - | 1: Right click and edit the dance pad. | + | |
| - | | + | |
| - | 8 dance pads are highlighted. | + | |
| - | This is a linked object. | + | |
| - | + | ||
| - | 2: Tick "Edit Linked" | + | |
| - | + | ||
| - | 3: Left click on target object | + | |
| - | | + | |
| - | + | ||
| - | 4: Copy Keys. | + | |
| - | + | ||
| - | In IM or Local: | + | |
| - | | + | |
| - | | + | |
| - | Example: | + | * Example: Anne! sit 59de9e89-83a6-a6ad-8760-594bbf76d853 |
| - | Anne! sit 59de9e89-83a6-a6ad-8760-594bbf76d853 | + | |
| - | + | ||
| - | The same goes for touch. | + | |
| + | \\ | ||
| + | ---- | ||
| - | |||
| - | </ | ||
| - | ---- | ||
| For Script entries, simply "sit (UUID)" | For Script entries, simply "sit (UUID)" | ||
object_uuids.1767363118.txt.gz · Last modified: by robyn
