VORTECH SNW PADD System

Version 1.0

Your handheld PADD and its on-screen HUD work together. Use the HUD buttons to control the PADD.

1. Getting started

1. Find the **PADD HUD** and **handheld PADD** in your inventory.
2. Right-click each one and choose **Add** to wear both. The handheld must be attached to your **Left Hand** or **Right Hand**.
3. If Second Life asks permission to animate your avatar, choose **Yes**.
4. Allow a few seconds for the two objects to connect.
5. Click **POWER** on the HUD.

Wear both objects when using the PADD. For messaging, wait for **PADD Mail: Mail ready.** before sending.

2. POWER — switching on and off

Click **POWER** to switch the PADD on. Click it again to switch off.

• **Green POWER button:** on.
• **Red POWER button:** off.

The handheld screen and power sounds follow the power setting. Other feature buttons work while the PADD is on.

Unread mail can still arrive while the worn HUD is powered off. Switch on to read it.

3. Holding and typing effects

The handheld uses the holding animation for whichever hand it is attached to. To change hands, detach it and attach it to your **Left Hand** or **Right Hand**.

Accepted HUD button presses also trigger a short typing effect and the configured sounds. The typing animation follows the male or female setting of your avatar shape.

You do not need to start the typing effect yourself. Give each action a moment to finish before pressing again.

4. LOG — playing log sounds

1. Switch **POWER** on.
2. Click **LOG** once.
3. The typing effect starts first. The log sound follows after about **2.5 seconds**.
4. Wait for your LOG timer, then click again for the next sound.

Each accepted press plays one log. After the last sound, the list starts again at the first.

The PADD includes **12 built-in log sounds**. These play when you have no valid custom sounds in the LOG notecard.

5. Adding your own LOG sounds

You can add **up to 10 sound UUIDs**. A UUID is the asset ID of a sound; use a sound UUID, rather than an avatar or texture UUID.

1. Rez a spare copy of the **handheld PADD** on land where you can build.
2. Right-click it, choose **Edit**, and open **Contents** in its main/root prim.
3. Open the notecard named exactly **PADD LOG Sounds**. If it is missing, create a notecard with that name and add it to these contents.
4. Put each sound UUID after the equals sign on a `LOG_1=` to `LOG_10=` row. Use one UUID per row, without quotation marks.
5. Leave unused rows blank. Save the notecard, take the edited PADD back into inventory, and wear it with the HUD.

Use this layout, replacing the example words with your real sound UUIDs:

```text LOG_COOLDOWN_SECONDS=30.0 LOG_1=PASTE-FIRST-SOUND-UUID-HERE LOG_2=PASTE-SECOND-SOUND-UUID-HERE LOG_3= LOG_4= LOG_5= LOG_6= LOG_7= LOG_8= LOG_9= LOG_10= ```

With any valid custom sounds, LOG uses your custom list instead of the built-in list. Filled rows play in numbered order; blank rows are skipped.

• **One sound:** the same sound repeats on each accepted press.
• **Two sounds:** sound 1, sound 2, sound 1, sound 2.
• **Five sounds:** sounds 1 through 5, then back to sound 1.

To return to the built-in sounds, clear everything after `LOG_1=` through `LOG_10=` and save. Keep the rows themselves.

6. Choosing your LOG timer

In **PADD LOG Sounds**, change this line:

```text LOG_COOLDOWN_SECONDS=30.0 ```

`30.0` means **30 seconds between accepted LOG presses**. Choose a number from **3 to 3600 seconds**.

The normal default is **18 seconds**. A missing, blank or invalid timer also uses 18 seconds. The timer works with both custom and built-in sounds.

Save the notecard after editing. Choose a wait long enough for your clips to finish. Pressing LOG during the wait does not start another log. The timer starts when your press is accepted, before the sound begins.

7. Setting up messaging contacts

Messaging uses a separate notecard named exactly **PADD Contacts**, in the **HUD's main/root prim contents**.

1. Rez a spare copy of the HUD and open **Edit → Contents**.
2. Open **PADD Contacts**.
3. Add one person per line, using a label, a vertical bar `|`, and their avatar UUID or account username.
4. Save, take the edited HUD back into inventory, and wear it with your PADD.
5. Wait for **Mail ready**.

Example using account usernames:

```text Captain | first.last Engineer | another.resident ```

Replace the examples with real account usernames. Use their account name, rather than their changeable display name. An avatar UUID is also accepted after the bar.

**Both people must add each other** to their contacts and wear their mail HUD at least once to finish setup. No activation code is needed for the current PADD.

You can keep up to **50 contacts**. Wear one PADD mail HUD at a time.

8. SEND — sending to one person

1. Switch **POWER** on and click **Send**.
2. Choose the numbered contact in the menu. Use **Next** or **Prev** to change pages.
3. Type your message and choose **Submit**.
4. Check the preview, then choose **Send** to confirm. Choose **Cancel** to discard it.

Keep messages short: the limit is about **240 plain English characters**. Some symbols and non-English characters use more of that allowance.

**Stored for 1** means the message was saved for that person. It does not mean they have read it. If it says **stored for 0**, check the rest of the receipt before trying again.

9. ALL — sending to your contacts

1. Click **All**.
2. Type your message and choose **Submit**.
3. Check the preview and choose **Send All**.

This sends to the people in your contacts list who also have you in theirs. It does not broadcast to the whole region.

Check the receipt for how many messages were stored and whether any recipients were unavailable or had full inboxes.

10. RECEIVE — reading messages

The **INCOMING** indicators and green **Receive** button show unread mail. A received-message sound plays from the handheld PADD.

1. Switch **POWER** on and click **Receive**.
2. Choose the numbered message from the menu.
3. Read it in your private owner chat.
4. Repeat for your other unread messages.

Reading removes a message from the unread inbox. The indicators clear when no unread messages remain.

The worn HUD normally checks for mail about every **30 seconds**. Messages can be saved while you are offline, once your mailbox and contacts have been set up. Your inbox holds **20 unread messages**; read some to make room when it is full.

11. REGION SCAN — finding avatars

1. Switch **POWER** on.
2. Click **REGION SCAN** once.
3. Wait about **2.5 seconds** for the scan sound and results.

The scan lists avatars in your current region, nearest first, with their name, approximate distance and region position. It includes your own avatar.

Results normally appear in local chat, so nearby people may see them. The scan is a snapshot, rather than continuous tracking. It scans avatars, and can report at most 100 in a crowded region.

12. MANIFEST — displaying your ship or crew list

Click **MANIFEST** while powered on to read the **PADD Manifest** notecard from the handheld into chat.

To customise it, open that notecard in the **handheld's main/root prim contents**. Keep one of these settings as the very first line:

```text CHAT=OWNER ```

This shows the text only to you. For nearby public chat, use:

```text CHAT=LOCAL ```

Below that line, enter your ship details, crew list or other roleplay text. Use one entry per line and save.

Each press reads the saved card from the beginning. Let it finish before pressing again. Switching POWER off stops the reading.

13. OPEN, CLOSE and LOCK — compatible sliding doors

These buttons require a doorway already set up with the supplied **SNW sliding-door system**. Ordinary Second Life doors need their own compatible setup.

Wear the PADD, switch on, and stand close to a door **you are allowed to use**, in the same region. The default response distance is **2 metres**.

| Button | What it does | |---|---| | **OPEN** | Opens the nearest compatible door within its set range, if unlocked. | | **CLOSE** | Closes that door. | | **LOCK** | Locks and closes an unlocked door. | | **LOCK again** | Unlocks the selected door. Click OPEN to open it. |

Door owners choose access in the door's **Sliding Door Config** notecard:

• **PRIVATE:** only the owner.
• **GROUP:** owner plus visitors who activate the group assigned to the door.
• **PUBLIC:** anyone.

These settings apply to PADD OPEN/CLOSE and collision opening. LOCK and unlock remain owner-only. For door installation, follow the setup guide included with the door kit.

Wait for each response before pressing again. With several doors nearby, step closer to the one you want.

For this sliding-door system, **red LOCK** means the last selected door reported locked; **white** follows an unlocked reply. White is also the neutral colour after a reset or cancelled command, so it alone does not prove a door is unlocked.

If collision opening is enabled on the doorway, permitted users can bump an unlocked panel to open it. Locking prevents this. Automatic closing depends on the doorway's settings.

14. Changing the screen readout

With POWER on, touch the handheld PADD screen to cycle its readout materials. Screen changes are disabled while powered off.

15. Sliding the HUD away

Click the HUD's main background once to slide it away. Click it again to bring it back.

While the HUD is stowed, the PADD holding animation stops. When the HUD is fully back, the holding animation returns for the hand wearing the PADD. Stowing does not switch POWER off.

16. Quick help

| Problem | Try this | |---|---| | Buttons do nothing | Wear both objects, attach the handheld to Left Hand or Right Hand, allow animation permission, and check that POWER is green. | | LOG will not play again | Wait for the full timer, then press once. Check that your UUID belongs to a sound. | | Custom logs are not loading | Check the exact card name **PADD LOG Sounds**, save it in the handheld root, and check your UUID rows. | | Cannot send to someone | Both people must list each other. Wait for Mail ready and check the send receipt. | | Incoming message has not appeared yet | Allow up to 30 seconds, then click Receive while powered on. | | Inbox is full | Read unread messages, then ask the sender to send again. | | MANIFEST does not read | Check **PADD Manifest** is in the handheld root and its first line is CHAT=OWNER or CHAT=LOCAL. | | A door does not respond | Check door access, your active group, compatible setup, power and range. Step closer and wait for the current command to finish. |

For a connection problem, take off both objects and add them again. Switch POWER back on when they have connected.

If you need support, copy the exact error from chat and say which button you pressed. For LOG problems, include your timer setting and how long you waited.