Skip to main content

Receptor Objects

Learn how to set up and manage objects in Second Life that can receive actions from your HUD Web Creator.

[Suggested Image: Object in Second Life with CaveTech_obj_Config script showing the connection to the web dashboard]


What are Receptor Objects?

Receptor Objects are items in Second Life that have been configured to receive and respond to actions from your HUD Web Creator. These objects act as the "targets" for your button configurations.

Key Characteristics

  • Script-enabled: Must contain the CaveTech_obj_Config script
  • Network-connected: Communicate with the web dashboard in real-time
  • Action-responsive: Execute commands sent from HUD buttons
  • Multi-link capable: Support complex linked objects with multiple parts

[Suggested Image: Diagram showing the communication flow between HUD, web dashboard, and receptor objects]


Setting Up Receptor Objects

Step 1: Add the Configuration Script

  1. Open Object Inventory: Right-click your object and select "Edit"
  2. Go to Contents Tab: Click the "Contents" tab in the edit window
  3. Add Script: Drag the CaveTech_obj_Config script into the object's inventory
  4. Wait for Activation: The script will automatically initialize

📝 Important: Always reset the object after adding the script to ensure proper functionality.

[Suggested Image: Second Life edit window showing the Contents tab with CaveTech_obj_Config script]

Step 2: Verify Script Installation

After adding the script, you should see:

  • Green Text: Confirmation message in local chat
  • Script Running: Script shows as "Running" in object contents
  • Network Connection: Object registers with the CaveTech system

Step 3: Connect to Your HUD Session

  1. Get Session ID: Copy the session ID from your HUD dashboard
  2. Proximity Required: Ensure the receptor object is within range of your HUD
  3. Automatic Detection: The system will automatically detect and link the objects

[Suggested Image: Session ID being copied from dashboard and proximity detection in Second Life]


Object Detection and Registration

Automatic Discovery

When properly configured, receptor objects are automatically discovered by the system:

Detection Process

  1. Script Initialization: Object runs CaveTech_obj_Config script
  2. Network Registration: Object registers with CaveTech servers
  3. Proximity Check: System detects objects near active HUDs
  4. Dashboard Display: Objects appear in the "Receptor Objects" section

Detection Requirements

  • ✅ Object must have CaveTech_obj_Config script
  • ✅ Script must be running (not paused)
  • ✅ Object must be within detection range
  • ✅ HUD must be active and connected

[Suggested Image: Receptor objects section in dashboard showing detected objects with their details]


Object Information Display

Dashboard Information

For each detected receptor object, the dashboard displays:

Basic Information

  • Object Name: The name of the object as shown in Second Life
  • Object Key: Unique identifier (UUID) of the object
  • License Key: CaveTech license associated with the object
  • Last Seen: When the object was last detected online
  • Total Links: Number of linked parts in the object
  • Link Details: Information about each individual link
  • Link Names: Custom names assigned to links (if available)
  • Texture Faces: Number of texture faces per link

[Suggested Image: Detailed object information panel showing all metadata and link structure]

Each link in a receptor object provides:

PropertyDescriptionExample
Link NumberSecond Life link number1, 2, 3, etc.
Link NameCustom name (if set)"Door", "Handle", "Frame"
Prim NameSecond Life prim name"Object"
Texture FacesNumber of faces6 (for a cube)

Object Management

Naming Convention

Object Names

  • Descriptive Names: Use clear, descriptive names for your objects
  • Consistent Naming: Follow a naming pattern across related objects
  • Version Control: Include version numbers for updated objects

Examples:

  • ✅ "Store Display Board v2.1"
  • ✅ "Avatar Customization Terminal"
  • ✅ "Product Showcase - Clothing"
  • ❌ "Object"
  • ❌ "Untitled"
  • Functional Names: Name links based on their function
  • Clear Identification: Use names that make targeting easy
  • Avoid Duplicates: Each link should have a unique identifier

Examples:

  • ✅ "Main Panel", "Side Panel", "Top Edge"
  • ✅ "Red Section", "Blue Section", "Logo Area"
  • ✅ "Display Screen", "Control Interface", "Base Stand"

[Suggested Image: Object with properly named links showing in the dashboard interface]

Object Organization

  • Location-based: Group objects by their physical location
  • Function-based: Group by what they do or control
  • Permission-based: Group by who can modify them

Range Management

  • Detection Range: Keep objects within reasonable range of HUDs
  • Performance: Too many objects can impact performance
  • Organization: Spread objects across different sessions if needed

Object States and Status

Connection Status

🟢 Connected

  • Online: Object is currently active and responding
  • Recent Activity: Last seen within the past few minutes
  • Ready for Actions: Can receive and execute button commands

🟡 Disconnected

  • Offline: Object hasn't been seen recently
  • May be out of range: Check proximity to HUD
  • Possible script issues: Verify script is running

🔴 Error State

  • Script Problems: CaveTech script may have errors
  • Permission Issues: License or permission problems
  • Network Problems: Connection to CaveTech servers failed

[Suggested Image: Status indicators showing different connection states with troubleshooting hints]

Troubleshooting Object Issues

Object Not Detected

  1. Check Script: Verify CaveTech_obj_Config is present and running
  2. Reset Object: Right-click object → More → Reset Scripts
  3. Check Range: Move object closer to your HUD
  4. Verify License: Ensure you have a valid CaveTech license

Object Shows as Disconnected

  1. Check Object Status: Is the object still rezzed in-world?
  2. Script Status: Look for script errors in object
  3. Network Issues: Check your Second Life connection
  4. Range Issues: Verify object is within detection range

Actions Not Working

  1. Verify Configuration: Check button configurations are correct
  2. Test Simple Actions: Try basic actions like color changes first
  3. Check Targets: Ensure link and face selections are valid
  4. Script Restart: Reset the receptor object scripts

[Suggested Image: Troubleshooting flowchart showing common issues and solutions]


Advanced Object Configuration

  • Link 1: Root prim (main object)
  • Links 2+: Child prims (linked parts)
  • Link Numbers: Assigned automatically by Second Life
  • Maximum Links: 256 links per linkset

Working with Complex Objects

  • Individual Control: Target specific links for precise control
  • Group Control: Use "All Links" for uniform changes
  • Face Targeting: Control specific faces on specific links

[Suggested Image: Complex multi-link object with numbered links and face highlighting]

Permission Management

Object Permissions

  • Modify Rights: Required to add/remove scripts
  • Copy Rights: Useful for backup and distribution
  • Transfer Rights: Needed for sharing configured objects

Script Permissions

  • Run Scripts: Must be enabled for receptor objects
  • Script Access: CaveTech scripts need network access
  • Auto-Return: Consider land settings that might return objects

Object Performance Optimization

Best Practices

Object Complexity

  • Minimize Scripts: Use only necessary scripts in receptor objects
  • Optimize Textures: Use appropriate resolution textures
  • Efficient Geometry: Keep polygon count reasonable

Network Efficiency

  • Reasonable Range: Don't spread objects too far apart
  • Active Management: Remove or archive unused objects
  • Session Organization: Group related objects in same sessions

Resource Management

  • Memory Usage: Monitor script memory usage
  • Update Frequency: Avoid unnecessarily frequent updates
  • Batch Operations: Group related actions when possible

[Suggested Image: Performance monitoring interface showing object resource usage]


Integration Examples

Common Use Cases

Retail Display

  • Product Showcases: Multiple objects showing different products
  • Color Variants: Switch between different color options
  • Material Samples: Show different texture and material options

Interactive Art

  • Dynamic Sculptures: Objects that change based on interaction
  • Responsive Environments: Spaces that adapt to user presence
  • Collaborative Installations: Multiple users controlling different aspects

Architectural Elements

  • Building Controls: Lighting, doors, windows, decorations
  • Mood Setting: Environmental controls for atmosphere
  • Functional Elements: Interactive building components

[Suggested Image: Examples of different object types being controlled by HUD systems]

Configuration Patterns

Master-Slave Setup

  • Master HUD: Controls multiple receptor objects
  • Coordinated Actions: Actions affect multiple objects simultaneously
  • Scene Control: Complete environment management

Distributed Control

  • Multiple HUDs: Different HUDs control different object groups
  • User-Specific: Each user controls their own set of objects
  • Permission-Based: Different control levels for different users

Security and Permissions

Access Control

Object Security

  • Ownership Verification: Only object owners can add receptor scripts
  • License Validation: Valid CaveTech license required
  • Permission Checks: System verifies user permissions

Action Limitations

  • Owner Actions: Some actions require object ownership
  • Group Access: Group members may have limited access
  • Public Restrictions: Public access may be limited

Privacy Considerations

Data Handling

  • Object Information: Basic object data is stored for functionality
  • Action Logs: Button actions may be logged for debugging
  • Personal Data: No personal information is collected from objects

Network Security

  • Encrypted Communication: All data transmission is encrypted
  • Secure Authentication: License validation uses secure methods
  • Privacy Protection: User privacy is protected throughout

Next Steps

Continue setting up your HUD system:

  1. Advanced Techniques - Complex configurations and setups
  2. Button Configuration - Return to button setup
  3. Action Types - Explore all available actions
  4. Dashboard Overview - Return to dashboard overview

Need help with object setup? Visit our Contact Support page for assistance.